QA/Automation/Projects/WebRTC/Crashtest Guide: Difference between revisions

Line 40: Line 40:
The following is best explained with an example:
The following is best explained with an example:


We take a bug, e.g Bug https://bugzilla.mozilla.org/show_bug.cgi?id=803535 critical, VERIFIED FIXED, WebRTC crash [@mozilla::MediaEngineDefault::EnumerateAudioDevices]
We take a bug, e.g Bug https://bugzilla.mozilla.org/show_bug.cgi?id=803535 <tt>critical, VERIFIED FIXED, WebRTC crash [@mozilla::MediaEngineDefault::EnumerateAudioDevices]</tt>


Take the submitted testcase and create a suitable file (usually HTML file) on your harddrive.
Take the submitted testcase and create a suitable file (usually HTML file) on your harddrive.


Now obtain a build from the day this bug was submitted using mozdownload. In this case it was: 2012-10-19 07:31 PDT (top right of the bug report)
Now obtain a build from the day this bug was submitted using <tt>mozdownload</tt>. In this case it was: <tt>2012-10-19 07:31 PDT</tt> (top right of the bug report)


Now call
Now call
Line 50: Line 50:
     mozdownload --type=daily –date=2012-10-19
     mozdownload --type=daily –date=2012-10-19


from the command line. This should download a file called ''2012-10-19-03-05-51-mozilla-central-firefox-19.0a1.en-US.linux-x86_64.tar.bz2''.
from the command line. This should download a file called <tt>2012-10-19-03-05-51-mozilla-central-firefox-19.0a1.en-US.linux-x86_64.tar.bz2</tt>.


Unpack this version of firefox and start it from command line with
Unpack this version of firefox and start it from command line with
Line 62: Line 62:
{| border="1" cellpadding="5"
{| border="1" cellpadding="5"
|'''SIDE NOTE:'''<br>
|'''SIDE NOTE:'''<br>
If it crashes straight away, it is possible to check the stacktrace by starting the nightly build and going on the page about:crashes
If it crashes straight away, it is possible to check the stacktrace by starting the nightly build and going on the page <tt>about:crashes</tt>
Also, please make sure that ''media.navigator.enabled'' and ''media.peerconnection.enabled'' in ''about:config'' is set to '''true''' before testing for the crash. If these are not enabled, nothing will happen.
Also, please make sure that <tt>media.navigator.enabled</tt> and <tt>media.peerconnection.enabled</tt> in <tt>about:config</tt> is set to '''<tt>true</tt>''' before testing for the crash. If these are not enabled, nothing will happen.
|}
|}


Confirmed users
35

edits