search

fiuba08 / robotframework

Automatically exported from code.google.com/p/robotframework
Apache License 2.0
0 stars 0 forks source link

Include original error message in suite setup/teardown failed messages #1307

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently when test suite setup or teardown fails, affected tests will be 
failed with message like `Setup of the parent suite failed`. Because message 
doesn't contain the original error message, knowing why that setup/teardown 
failed by just looking at this message isn't possible. To ease debugging, the 
original message should be included.

Original issue reported on code.google.com by pekka.klarck on 14 Dec 2012 at 2:16

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 20b42c46b119.

Initial implementation adding suite setup message.
TODO:
- fix tests
- handle errors in initialization of test suites
- handle errors in teardowns (if possible)
- refactor

Original comment by kontu...@gmail.com on 3 Jan 2013 at 1:00

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 511afd7bc1c4.

Fix broken test cases

Original comment by kontu...@gmail.com on 3 Jan 2013 at 1:28

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 8e5e10e55554.

Fixed fatal exception related tests.

Original comment by robotframework@gmail.com on 3 Jan 2013 at 1:30

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision d4a9456ee2e9.

Add suite initialization errors to test errors.

Original comment by kontu...@gmail.com on 3 Jan 2013 at 2:35

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 665a4710beee.

Refactor earlier work
TODO:
- better tests for initialization
- handling of teardown errors

Original comment by kontu...@gmail.com on 3 Jan 2013 at 2:35

GoogleCodeExporter commented 9 years ago 
Partial implementation of handling of teardown errors as attachment.

Original comment by kontu...@gmail.com on 3 Jan 2013 at 4:05

Attachments:

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 78f28393c523.

Now also suite teardowns are handled. This needed a bit more work
because when suite teardowns fail, all test related information has
already been written to output.xml. The message that suite teardown has
failed is added only when output is processed. There was no easy way to
get the correct errros at this point, so we needed to add it to
output.xml.

Now when a teardown fails, the error message is written into <status>
element similarly as with tests and suites. Other keywords don't need
this information so it was not added to them. Test teardowns don't
really need it either, but there was no simple/fast way to check is a
keyword suite or test teardown.

Original comment by pekka.klarck on 5 Jan 2013 at 5:14

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 8dff29b54387.

Suite's don't actually need information about their parents' possible failures. 
Enough to show their own errors.

Original comment by pekka.klarck on 5 Jan 2013 at 5:14

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 38743eedb3df.

Also tested that long error messages are cut correctly.

Original comment by pekka.klarck on 5 Jan 2013 at 6:15

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 28f960dd354a.

Explicitly testing that teardown errors are written to XML.

I consider this issue done.

Original comment by pekka.klarck on 5 Jan 2013 at 6:15

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 0b7f266dea6e.

Ooops, forgot that changing suite teardown error message breaks quite many 
unrelated tests. Hopefully all fixed now.

Original comment by pekka.klarck on 5 Jan 2013 at 7:36

GoogleCodeExporter commented 9 years ago

Original comment by robotframework@gmail.com on 7 Jan 2013 at 10:47

GoogleCodeExporter commented 9 years ago

Original comment by robotframework@gmail.com on 7 Jan 2013 at 1:01