1,072
edits
QA/Execution/Web Testing/Docs/Automation/Testcases/TroubleshootingAmoTests: Difference between revisions
QA/Execution/Web Testing/Docs/Automation/Testcases/TroubleshootingAmoTests (view source)
Revision as of 01:12, 9 November 2010
, 9 November 2010no edit summary
(Created page with "= Troubleshooting failed AMO test runs = Test suite driver output log in Hudson The test suite driver appends the output from all tests’ stderr output followed by all tests...") |
No edit summary |
||
| Line 31: | Line 31: | ||
==== Saved exceptions ==== | ==== Saved exceptions ==== | ||
Test cases might capture certain errors and report them as a group at the end of the test. This is done where the same verifications are applied to multiple add-ons or pages, and it’s desirable to not end the test because of a minor discrepancy. (More on the SavedExceptions | Test cases might capture certain errors and report them as a group at the end of the test. This is done where the same verifications are applied to multiple add-ons or pages, and it’s desirable to not end the test because of a minor discrepancy. (More on the SavedExceptions object in the Conventions in AMO Tests wiki page.)<br> | ||
At then end of the test case all saved exceptions are printed to to stderr and assertion error is thrown with the message “exceptions reported by test case”. In the output log the saved exceptions and the assertion error appear in separate blocks. Since they both contain a test case name they can be tied together as being from the same test. | At then end of the test case all saved exceptions are printed to to stderr and assertion error is thrown with the message “exceptions reported by test case”. In the output log the saved exceptions and the assertion error appear in separate blocks. Since they both contain a test case name they can be tied together as being from the same test. | ||
| Line 43: | Line 43: | ||
Counts for each error summary are also printed to avoid loosing visibility of an exception because it is buried amongst others. | Counts for each error summary are also printed to avoid loosing visibility of an exception because it is buried amongst others. | ||
The saved exceptions do not contain a line#, unlike raised exceptions with tracebacks. Searching the test case source code for the error summary will often return the line# at or near where the saved exeption was created. If the error summary text is not in the test case it will be in a function library or a page class method which was called by the test case. | The saved exceptions do not contain a line#, unlike raised exceptions with tracebacks. Searching the test case source code for the error summary will often return the line# at or near where the saved exeption was created. If the error summary text is not in the test case it will be in a function library or a page class method which was called by the test case. | ||
=== Errors that indicate failure due to environmental factors === | === Errors that indicate failure due to environmental factors === | ||