When all the operations performed in TestCollab revolve around test cases then it is important to have the knowledge about what a test case holds and what as a user you can do with it?

Test Case View Pane

Click on a test case listed on grid to open its view panel. All the information pertaining to test case right from its title, suite, steps and expected results to comments it has received, execution history, log of changes it had been through, are all available on this panel.

Title on top bar is accompanied by actions menu.

After Title, you can see information like Priority, Suite, Test Case created date, updated date, its author and description.

Next Section is for the data related to the custom fields and tags associated with this test case.

Then comes the most important part of information the steps followed by their expected results are shown sequentially.

The bottom section of the panel is divided in 3 parts: Comments, Run history and Change log

Comments

Communication becomes the basis of the real collaboration between team members, that is why with the version 2 of TestCollab we have introduced the comments feature allowing users to share their views, feedback and instructions related to the test case.

Comments can be simple text messages to share your views about the test case with team, but there are certain other features worth exploring:

@mentions

Now, you can directly address your teammates by mentioning them in comments to share your views or instructions. For this the '@' is to be used to get the list of project members. There would be in-app and email notifications for the users who have been mentioned.

#testcase references

You can also refer other test cases in your comment, you start by typing '#' to get list of test cases in the project, select one of the test cases to add a reference with link to the test case's view page.

Run History

When test cases are added to test plans and have been executed a run history gets created, and to have details of the executions a test case has been through there is a separate section on view panel.

Key metrics:

  • Total number of runs a test case has been through

  • When the test case was last ran

  • What was status during the last run

  • What is the average time required to execute this test case: calculated by dividing total execution time (under different test plans, configurations and RUNs) by the total number of runs

Followed by the metrics are the logs of every execution the test case has been through.

Change Log

During the lifetime of a test case it goes through many a changes by its users, all these changes can be viewed on Change log panel in chronologically descending order i.e. latest change is shown first.

Every row in the change log denotes a version (revision) of test case, where you see:

  • Version number (again latest being on top)

  • When the version was introduced

  • Who made this change

  • A brief summary of change - it can be adding a new case, modifying it or reverting to a previous version

  • Fields for which the values have changed during this revision

  • Actions

Revert to a previous version

If you are convinced that a previous version of test case is to be used and all the changes done after that revision should be omitted then revert action can be used for the test case. This would revert all the changes that a test case had been through after the selected revision, this would again create yet another revision with logs of whatever differences test case has been through due to this revert action.

Full Screen View

In action menu "View" opens a full screen view of test case. This full screen view is also used when a link for referred test case is used either within app or received through an email.

Did this answer your question?