QA/Execution/Web Testing/mcomtests: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 26: Line 26:
*Every commit in there should be reviewed (to be sure we are not breaking other tests, only adding good new tests)
*Every commit in there should be reviewed (to be sure we are not breaking other tests, only adding good new tests)
*Public reporting system (so that we quickly know if any branch is misbehaving)
*Public reporting system (so that we quickly know if any branch is misbehaving)
**[http://qa-selenium.mv.mozilla.com:8080/ Hudson] takes care of it

Revision as of 18:36, 23 March 2011

Mozilla.com Automated Test Tracking

Dev requirements ideas

  • Easy to run locally (when refactoring)
  • Every commit in there should be reviewed (to be sure we are not breaking other tests, only adding good new tests)
  • Public reporting system (so that we quickly know if any branch is misbehaving)