forked from mirrors/gecko-dev
ca0d2865b4
It's not clear what the advantage of waitFor is supposed to be, but in practice the use of requestAnimationFrame makes the timing somewhat unpredictable. Just using the built-in timer based polling seems simpler for these tests without changing their behaviour. Differential Revision: https://phabricator.services.mozilla.com/D158967 |
||
|---|---|---|
| .. | ||
| awsy | ||
| condprofile | ||
| config | ||
| crashtest | ||
| docs | ||
| extensions | ||
| firefox-ui | ||
| fxrecord/perfdocs | ||
| geckodriver | ||
| gtest | ||
| jsshell | ||
| marionette | ||
| mochitest | ||
| modules | ||
| mozbase | ||
| mozharness | ||
| perfdocs | ||
| performance | ||
| profiles | ||
| raptor | ||
| runtimes | ||
| specialpowers | ||
| talos | ||
| tools | ||
| tps | ||
| web-platform | ||
| webcompat | ||
| webdriver | ||
| xpcshell | ||
| addtest.py | ||
| cppunittest.ini | ||
| mach_commands.py | ||
| moz.build | ||
| parse_build_tests_ccov.py | ||
| README.txt | ||
| remotecppunittests.py | ||
| runcppunittests.py | ||
| testinfo.py | ||
| testsuite-targets.mk | ||
Common testing tools for mozilla codebase projects, test suite definitions for automated test runs, tests that don't fit anywhere else, and other fun stuff