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:20, 13 December 2012
, 13 December 2012→How to find a good bug to write a crashtest for?
| Line 285: | Line 285: | ||
These are only guidelines and there is no easy rule to obey here. | These are only guidelines and there is no easy rule to obey here. | ||
*Find a bug that crashes straight away. If you have to do reloads or anything like this to re-create the crash, then it is probably not good for a start. | *Find a bug that crashes straight away. If you have to do reloads or anything like this to re-create the crash, then it is probably not good for a start. | ||
*If the bug has the keywords | *If the bug has the keywords <tt>crash</tt> or <tt>in-testsuite</tt>, that is a good sign (<tt>in-testsuite</tt> may also mean <tt>mochitest</tt>, so be careful there). | ||
*If you are unsure, you can always ask ;) | *If you are unsure, you can always ask ;) | ||