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 13:19, 13 December 2012
, 13 December 2012→Testing on the current version
| Line 274: | Line 274: | ||
Now all that is left to be done, is to test the crashtest on the current version of firefox and if everything is ok, create a patch file which can be submitted. | Now all that is left to be done, is to test the crashtest on the current version of firefox and if everything is ok, create a patch file which can be submitted. | ||
In order to revert this change call either hg revert –all (if you are using mercurial) or patch -p1 < %filename% . | In order to revert this change call either <tt>hg revert –all</tt> (if you are using mercurial) or <tt>patch -p1 < %filename%</tt>. It might also be wise to make sure at this point that the changes were truly implemented. At this juncture just run another crashtest and see if the output is expected (in our case, the crashtest should pass) | ||
TEST_PATH=dom/media/tests/crashtests/ make -C obj/ crashtest | |||
TEST_PATH=dom/media/tests/crashtests/ make -C obj/ crashtest | |||
===Create a patch=== | ===Create a patch=== | ||