"Do Not's" of using (Jira) XRay

Hey there.

I have been contemplating expanding our test reporting/case mgmt from Confluence pages to get Jira in for assistive purposes.
I’ve got a few new joiners who are somewhat super enthusiastic about the usage of Jira. However, I am a bit wary of it. I do get its benefits but I also believe that it can be easily misused.

e.g. I wouldn’t like people to record their exploratory tests runs - for this, I prefer something more of a report that describes some scenarios and basic stuff like test setup and overall progress of the testing. My nightmare would be to see tonnes of new test scenarios there that wouldn’t be considered for regressions and were purely exploratory.

What is your experience with the tool? And what do you think of the above?

2 Likes

We ran a few projects where exploratory testing was done separate but key scenarios were formally created in test management to keep growing knowledge that can be reused after. I think it should be a balanced approach where you have flexibility of exploratory testing and formality of test management. The one suggestion that can be done here is to make a process that will be followed by everyone. If it’s test cases rather than exploratory testing then go for it.

As one example that we used (not with XRay), creating test cases, linking it back to user stories and map confluence pages to test coverage from user stories.

1 Like

Thanks for the reply. I’ve also been thinking of some way to x-use various tooling and make sense of them all when it comes to reporting. I defo don’t want to make it too formal but formal enough