Confirmed users
35
edits
QA/Automation/Projects/WebRTC/Crashtest Guide: Difference between revisions
Jump to navigation
Jump to search
QA/Automation/Projects/WebRTC/Crashtest Guide (view source)
Revision as of 17:38, 13 December 2012
, 13 December 2012→Long-term setup
| Line 48: | Line 48: | ||
*https://developer.mozilla.org/en-US/docs/Developer_Guide/Mozilla_build_FAQ#Making_builds_faster | *https://developer.mozilla.org/en-US/docs/Developer_Guide/Mozilla_build_FAQ#Making_builds_faster | ||
*https://developer.mozilla.org/en-US/docs/Developer_Guide/mach | *https://developer.mozilla.org/en-US/docs/Developer_Guide/mach | ||
===Running existing tests=== | |||
Another thing to note for later is how to run existing tests. Depending on how you got your Firefox build there are two ways in running the tests for WebRTC. For now we will only focus on crashtests because mochitests aren't ready yet. | |||
With packaged tests ([https://wiki.mozilla.org/Auto-tools/Automation_Development/Projects/Crashtest_Guide#Short-term_setup Short-term setup]): | |||
python reftest/runreftest.py reftest/tests/dom/media/tests/crashtests/crashtests.list --appname=%path_to_binary% | |||
With a self-build Firefox ([https://wiki.mozilla.org/Auto-tools/Automation_Development/Projects/Crashtest_Guide#Long-term_setup Long-term setup]): | |||
TEST_PATH=dom/media/tests/crashtests/ make -C obj/ crashtest | |||
==Choose a bug (best one that is already verified) and reproduce the test case using an earlier version of firefox== | ==Choose a bug (best one that is already verified) and reproduce the test case using an earlier version of firefox== | ||