Hi
@prajakta,
I appreciate you state the report fields you list are "required by your organisation", but as
@nmrao said the list youve provided needs to be carefully considered.
An example of one of the reasons we're saying this is cos the list provided includes "reason test step fails" and "reason test step passes" as field attributes on the report.
The fact that youve included these attributes indicates the list has been put together by someone that is unfamiliar with soapui and in some ways testing itself.
Ignoring the fail option, youd never include a reason a step passes....it just passes so you dont worry about it. There'd be no added value in reporting the pass reason.
In regards to reason a step fails, its unlikely youd get this level of granularity in an execution report. You might include the failure itself (e.g. regex match failure, pattern [A-Z]{5}[0-9]{1}), but its unlikely youd get the full failure reason on the report saying "regex pattern facet restriction match failure due to invalid value 'Abcde99' for regex pattern [A-Z]{5}[0-9]{1}", due to the level of effort required and also this is dependent on the test tool itself. Its not impossible, but i believe its unlikely as i say due to the effort involved for little added value.
The above is just a single reason why we're saying you might want to go back to the person who suggested the report attributes and revisit what is essential and what attributes are just nice to have and go from there.
Ta
Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
