Auto-tools/Goals/Proposed 2010 Q2

From MozillaWiki
< Auto-tools‎ | Goals
Revision as of 20:45, 22 March 2010 by Ctalbert (talk | contribs) (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…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
class="header" Project class="header" Purpose class="header" WAG time
Test Harnesses into Own Repo
  • 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
  • Makes all tests use the same manifest structure
  • Gives us ability to manifest for mochi* tests
  • 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 implementation reftest style harnesses
  • 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"?