Description of test cases should be easily extractable or present somewhere in TestOps

Feedback & Reviews Feature Requests
1

As a test automater, I would like to be able to share my coverage of the functionalities tested in my automation tests. I also like to document this for my future-self or any other tester that come aboard our projects for optimal transparency/transferability.

Since there is no dedicated “coverage” field to detail what is covered by a testcase I currently use the field “Description” in the properties tab of the test case.
Example of such a description might be:

This test case covers the negative scenario of a failed login by entering an invalid credentials. We make sure the error message shows in correct language. Afterwards we cover the positive scenario when we try to do the login with correct credentials and verify the main landing page is loaded properly.

Ideally, coverage should (also) be explained by the linked requirements from JIRA, but we do not have the JIRA plugin.

I would like at any point be able to share this coverage information with stakeholders to clearly show what is covered by the automation runs and what is not.
However: I do not see any feature/functionality that would allow me to share this easily (without doing copy pasting the information from all of my tests).

Ideal solution: A dedicated “coverage” field that any user in TestOps can consult in TestOps. In the TestOps reporting I’d like to be able to see an overview (or at least export of) the test cases that run in a certain run with their coverage information, so a report that goes out to management states clearly what is tested. Note that this description might be a long descriptive text field.

Currently in TestOps there is a field “Description” in the /test-design/test-cases (above “Maintainer”) but that is never filled in with the information that I provided in the description field (bug or intended?).
There are also various export possible form the test results, but these do not include the description field.

3 Likes
3

Hi @joost.degeyndt,

Thank you for the suggestion. It sounds interesting and may be of great benefit to other users too :slight_smile:
We will give some thought on it and will definitely let you know once we decide to make it live.
Cheers!

On behalf of TestOps,
Thuyen

1 Like
4

Just a minor update from my side on this:
I have discovered that WebUI.comment() actually logs to the “Descriptions” field in the TestOps Reports-Test Runs-Result page!
So what we now try to do is construct our test cases with first a general description what the test case should do and what the expected prerequisites are through the WebUI.comment().
Followed by the actual script of the testcase with the actual execution logs, again via WebUI.comment. This allows 1° easy debug: You can see in TestOps description directly what was expected and what actually was done (and where the test run might stop). 2° documentation within the test case helps out test colleagues to know what goes on in the tests where. Below example is just a small use case, but in very big tests this can be of much help.

Example:
WebUI.comment(“PREREQUISITE: We have at least one row of data in the dashboard”)
WebUI.comment(“Enter invalid credentials and verify the error message”)
WebUI.comment(“Enter valid credentials and verify the dashboard loads”)
WebUI.comment("******EXECUTION LOG*****")
String negativePassword = “incorrectPassword”
String positivePassword = “correctPassword”
WebUI.comment(“We provide password $negativePassword , which should result in an error message”)
//code to sendKeys, click login button and assertion on error message here
…
//
WebUI.comment(“We provide password $positivePassword, which should result in a proper login and show the dashboard”)
…
…
WebUI.comment(“We find back this dossier $actualDossierFirstRow in the first row of the dashboard!”)