Topic starter
17/09/2020 8:30 am
Hi everybody,
I would like to know how you adapt your reporting to the various people in your organisation.
Here, we have 2 distinct process loops.
1 : The continuous integration loop.
2 : The continuous delivery loop.
From the same test base, both group will want different reports.
Developpers want to know if the features they introduce breaks anything that was working or breaks differently.
Stakeholders want to know about each an every failure in order to evalute the suitability of this specific version for a public release.
Both require extra steps and manipulation of the reports that can be generated with ascential test.
For developpers, a report suitable for difference analysis is the current prefered option.
A custom text base report is generated, then a diff/merge tool is used to see the difference with the previous release.
Any quirk is verbally reported to the developper, after discussion an Issue can be created at their demand.
For Product owner/stakeholders:
A full report with details is prefered over a summary report, it has to be editable.
Manually edit the report as to include all known Jira issues and possibly comment them.
All failures or anomalies have to be commented if not associated to a known Jira issue.
So, how do you adapt your reporting to the people in your organisation ❓
A failure summary is present in the result/report of AscentialTest for the developer. If this is not sufficient then a custom report with the details of the Testname, expected and Actual output can be provided only for the failure message along with a snapshot in XML format which looks clear to the developer.
For the Stakeholders, the detailed report should be fine or else the custom report can be created for every info, warning and failure.
In our organization we have both the reports defined one with failure summary and one with detailed report. Please let me know if you need further detail.
Thanks.
Dileep
Contact Our Team
