Auto-tools/Goals/Proposed 2010 Q2: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with '{| class="standard-table" |- |class="header" Project |class="header" Purpose |class="header" WAG time |- |Test Harnesses into Own Repo | * Enables us to run tests on all versions…')
 
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
{| class="standard-table"
{| class="standard-table"
|-
|-
|class="header" Project
|class="header"|Project
|class="header" Purpose
|class="header"|Purpose
|class="header" WAG time
|class="header"|WAG time
|-
|-
|Test Harnesses into Own Repo
| Maemo Qt Agent & test Harenesses
|
* Expand our sutagent system to maemo qt
|
|
* Enables us to run tests on all versions without backporting harness infrastrucutre
??
* Makes developers able to write tests for any branch in any test type
* Easier to maintain
* Easier to catch breakage
| 1.5 - 2 Quarters
|-
|-
| Universal Manifest
| Android Agent & test harnesses
|
|
* Makes all tests use the same manifest structure
* Aid RelEng in rolling out the Android harness and test system
* Gives us ability to manifest for mochi* tests
* Finish Android agent
* Gives us the ability to handle different behaviors per product, per platform
* Gives us the ability to create a better manifest than what we have now
* Gives us flexibility to selectively enable/disable tests (could create an "orange" only run for debugging)
|
|
* 1 Quarter design and experiment with manifest, selling the idea to dev, refactoring mochitest/xpcshell to use a manifest at all.
* 1 month dev time
* 1 month implementation reftest style harnesses
* 2 months support releng
* 1 month porting and testing
* TODO: Would we want to keep old behavior going forward or just new behavior going forward?  How does that change if we do the "test harness in own repo"?
|-
|-
| Profile Manager Replacement
|
* Replace the profile manager with a good xulrunner based tool
|
??
|-
| Mozmill + Buildbot
|
* Get Mozmill unitests running in a buildbot framework
| ??
|-
| Crash Automation UI 2.0
|
* Make it easier to view the correlations between crashes, assertions, valgrind messages
|
* 1 month design
* 1 month implementation
|-
| Mozmill.next
|
??
| ??
|-
| Launch HAL Reftest
|
* Get testing on driver/version/os configurations in the wild
| ??
|-
| Get Purify turned on for testing
|
* So that we get purify messages on windows where we have no valgrind coverage
| 3 weeks?
|-
| The next big dream (see email)
| ??
| ??
|}
|}

Latest revision as of 00:27, 23 March 2010

Project Purpose WAG time
Maemo Qt Agent & test Harenesses
  • Expand our sutagent system to maemo qt

??

Android Agent & test harnesses
  • Aid RelEng in rolling out the Android harness and test system
  • Finish Android agent
  • 1 month dev time
  • 2 months support releng
Profile Manager Replacement
  • Replace the profile manager with a good xulrunner based tool

??

Mozmill + Buildbot
  • Get Mozmill unitests running in a buildbot framework
 ??
Crash Automation UI 2.0
  • Make it easier to view the correlations between crashes, assertions, valgrind messages
  • 1 month design
  • 1 month implementation
Mozmill.next

??

??
Launch HAL Reftest
  • Get testing on driver/version/os configurations in the wild
 ??
Get Purify turned on for testing
  • So that we get purify messages on windows where we have no valgrind coverage
 3 weeks?
The next big dream (see email) ?? ??
Retrieved from "https://wiki.mozilla.org/index.php?title=Auto-tools/Goals/Proposed_2010_Q2&oldid=210272"