Custom HTML reports - Need Your Contribution

[Lucian]

Hi guys,

I am working on a custom HTML report for ReadyApi tests. This is how the report will look like:

If you know html, css, javascript or groovy and you want to contribute the git project can be found here.

[Nastya_Khovrina]

Lucian,

Thank you for sharing the project file!

[Lucian]

Sure, 

Still working on it. Hope it will help other people as well.

[Olga_T]

Great initiative, @Lucian!

Do you have any specific requirements for the report? What information do you expect to be displayed? For now, I think we need something like a list of items that the report should include so that anyone could contribute.

Community, we are looking forward to your suggestions!

Let’s float this topic for a couple of weeks so that our Community members could have a look and contribute.

And, thanks again for sharing, Lucian!

[Lucian]

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 🙂

[Olga_T]

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?

[Lucian]

WIP

[groovyguy]

I wish I had some of the skills you're looking for so that I could contribute, but this is awesome!

[Lucian]

haha thx. It's actually pretty simple to do. I just requires some time... 

[Lucian]