gecko-dev/devtools/docs/tests
Julian Descottes 91c02a6412 Bug 1638290 - Update try syntax for DAMP in the devtools documentation r=rcaliman
Differential Revision: https://phabricator.services.mozilla.com/D75530
2020-05-15 15:03:04 +00:00
..
README.md
debugging-intermittents.md
mochitest-chrome.md
mochitest-devtools.md Bug 1558755 - Add docs on how to run mochitests in headless mode, r=pbro,nchevobbe 2019-06-21 07:55:28 +00:00
node-tests.md Bug 1589597 - Mention compatibility node test suite in the docs r=ladybenko 2019-10-18 14:10:29 +00:00
perfherder-compare-link.png
perfherder-compare.png
perfherder-create-gecko-profile.png Bug 1556652 - Document how to create perf profiles on try for DAMP r=nchevobbe 2019-06-04 12:44:57 +00:00
perfherder-damp.png
perfherder-filter-subtests.png
perfherder-subtests.png
performance-tests.md Bug 1638290 - Update try syntax for DAMP in the devtools documentation r=rcaliman 2020-05-15 15:03:04 +00:00
regression-graph.png
regression-popup.png
writing-perf-tests-example.md Bug 1596686 - Use absolute paths for require calls r=gl 2019-12-27 12:23:47 +00:00
writing-perf-tests-tips.md Bug 1576835 - Update DAMP test writing documentation r=ochameau 2019-08-29 06:22:18 +00:00
writing-perf-tests.md Bug 1596686 - Use absolute paths for require calls r=gl 2019-12-27 12:23:47 +00:00
writing-tests.md Bug 1631358 - remove traces of CPOWs from devtools, r=jdescottes,loganfsmyth 2020-04-21 14:04:58 +00: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.