Forum Discussion
Report requirements:
- the user should have a navigation part (left side) and an editor part (right side) DONE
- the user should be able to use the navigation to select a test suite/ test case/ test step and see the corresponding details on the editor part DONE
- upon clicking a test suite/ test case the user should see the list of contained test cases/ test steps and their status exactly like you would see it in ReadyAPI GUI DONE
- upon clicking on a http/ rest/ soap test step the user should be able to see the raw request/ raw response in the editor part DONE
- upon clicking on a http/ rest/ soap test step the user should be able to see the assertions and their statuses DONE
- the user should be able to see exactly why some assertion failed (eg. expected vs actual result etc) DONE
- the user should be able to see what test are failed and what not directly from the navigator side DONE
- <ideally> there should be a filter to only see the failed test cases in the report DONE
- <nice to have> a number like "Failed test cases per total test cases" DONE
- more work has to be put into how we report other test steps types - for instance how do we report a jdbc request? how do we report a groovy script? DONE
Generating the report:
There are 2 options that I took into account so far for the actual generation:
1. Create a ReadyApi plugin - no idea how to do it yet or if it adds value.
2. Create a groovy Tear-Down script - probably the simplest and yet most efficient solution.
No work has been put in either of those methods of generating the report.
I will keep everyone posted with the progress on this. I am a little busy in this period so it might take a while :)
What a great set, Lucian!
Community, any ideas on how to deal with the items currently unimplemented?
Lucian wrote:
- upon clicking on a http/ rest/ soap test step the user should be able to see the raw request/ raw response in the editor part
- upon clicking on a http/ rest/ soap test step the user should be able to see the assertions and their statuses
- the user should be able to see exactly why some assertion failed (eg. expected vs actual result etc)
- more work has to be put into how we report other test steps types - for instance how do we report a jdbc request? how do we report a groovy script?
Related Content
- 5 years ago
- 12 years ago