Confirmed users
35
edits
QA/Automation/Projects/WebRTC/Crashtest Guide: Difference between revisions
QA/Automation/Projects/WebRTC/Crashtest Guide (view source)
Revision as of 20:44, 13 December 2012
, 13 December 2012→Testing your crashtest
| Line 261: | Line 261: | ||
Now is the time to test your crashtest in a real case scenario. In order to do this, add the following line to <tt>crastest.list</tt> in the <tt>$HOME/mozilla-central/dom/media/tests/crashtests</tt> directory. | Now is the time to test your crashtest in a real case scenario. In order to do this, add the following line to <tt>crastest.list</tt> in the <tt>$HOME/mozilla-central/dom/media/tests/crashtests</tt> directory. | ||
load %filename% | |||
{| border="1" cellpadding="5" | {| border="1" cellpadding="5" | ||
| Line 270: | Line 270: | ||
Now go to <tt>$HOME/mozilla-central/</tt> and run the crasthest | Now go to <tt>$HOME/mozilla-central/</tt> and run the crasthest | ||
./mach crashtest dom/media/tests/crashtests | |||
If you use the Short-term build, you will have to call | |||
python reftest/runreftest.py reftest/tests/dom/media/tests/crashtests/crashtests.list --appname=%path_to_binary% | |||
What we should now see, is a failed crashtest with the error message that you have seen earlier. To give you a guideline example again, I have shown the excerpt from the crashtest for this bug. | What we should now see, is a failed crashtest with the error message that you have seen earlier. To give you a guideline example again, I have shown the excerpt from the crashtest for this bug. | ||