gecko-dev/devtools/docs/tests
Julian Descottes 109bb692c0 Bug 1457098 - Update DevTools performance documentation to mention DevTools dashboard;r=ochameau
MozReview-Commit-ID: 6MIqaha3mcn

--HG--
extra : rebase_source : 28b8f2672fb8bf340643ed06990e1507e93d5ae5
2018-04-26 12:39:42 +02:00
..
README.md
debugging-intermittents.md
mochitest-chrome.md
mochitest-devtools.md
perfherder-compare-link.png Bug 1399465 - Document DAMP. r=nchevobbe 2017-10-10 16:08:22 +02:00
perfherder-compare.png Bug 1399465 - Document DAMP. r=nchevobbe 2017-10-10 16:08:22 +02:00
perfherder-damp.png Bug 1454582 - Update docs with new job name (damp-e10s) to run DAMP tests on try. r=jdescottes 2018-04-17 01:18:14 -07:00
perfherder-filter-subtests.png Bug 1399465 - Document DAMP. r=nchevobbe 2017-10-10 16:08:22 +02:00
perfherder-subtests.png Bug 1399465 - Document DAMP. r=nchevobbe 2017-10-10 16:08:22 +02:00
performance-tests.md Bug 1457098 - Update DevTools performance documentation to mention DevTools dashboard;r=ochameau 2018-04-26 12:39:42 +02:00
regression-graph.png Bug 1399465 - Document DAMP. r=nchevobbe 2017-10-10 16:08:22 +02:00
regression-popup.png Bug 1399465 - Document DAMP. r=nchevobbe 2017-10-10 16:08:22 +02:00
writing-perf-tests.md Bug 1432416 - Add comments and documentation about adding new DAMP tests;r=ochameau 2018-02-22 10:54:28 +01:00
writing-tests.md Bug 1436187 - Move existing shared head files to devtools/client/shared. r=bgrins 2018-03-02 19:14:05 -06:00
xpcshell.md

README.md

Automated tests

When working on a patch for DevTools, there's almost never a reason not to add a new test. If you are fixing a bug, you probably should write a new test to prevent this bug from occurring again. If you're implementing a new feature, you should write new tests to cover the aspects of this new feature.

Ask yourself:

  • Are there enough tests for my patch?
  • Are they the right types of tests?

We use three suites of tests:

  • xpcshell: Unit-test style of tests. No browser window, only a JavaScript shell. Mostly testing APIs directly.
  • Chrome mochitests: Unit-test style of tests, but with a browser window. Mostly testing APIs that interact with the DOM.
  • DevTools mochitests: Integration style of tests. Fires up a whole browser window with every test and you can test clicking on buttons, etc.

More information about the different types of tests can be found on the automated testing page at MDN.

To run all DevTools tests, regardless of suite type:

./mach test devtools/*

Have a look at the child pages for more specific commands for running only a single suite or single test in a suite.