canmove, Confirmed users
2,041
edits
B2G/QA/Automation/UI/Filing Bugs Against Automation Errors: Difference between revisions
B2G/QA/Automation/UI/Filing Bugs Against Automation Errors (view source)
Revision as of 00:37, 12 March 2015
, 12 March 2015→Names and Errors
| Line 2: | Line 2: | ||
In templates below, it is very important to be consistent about ''<test name>'' and ''<error>''. Being consistent about how these are supplied lets us easily search for whether a bug already exists for the failure. | In templates below, it is very important to be consistent about ''<test name>'' and ''<error>''. Being consistent about how these are supplied lets us easily search for whether a bug already exists for the failure. | ||
== <test name> == | |||
''<test name>'' is at least the *.py filename. However, if the test function and file have | ''<test name>'' is at least the *.py filename. However, if the test function and file have | ||
| Line 23: | Line 25: | ||
You do not need to include the class. | You do not need to include the class. | ||
== <error>> == | |||
''<error>'' is usually the last line of the stack trace. It will look like: | ''<error>'' is usually the last line of the stack trace. It will look like: | ||