Best practises on test case review workflow

LATEST Official version.
Questions and discussions - NO ISSUES
FOR ISSUES => http://mantis.testlink.org

Moderators: Amaradana, TurboPT, TL Developers

Post Reply
hmaier
TestLink user
Posts: 2
Joined: Sat Feb 03, 2018 9:33 am

Best practises on test case review workflow

Post by hmaier »

I want to ask you guys how you solved the workflow for reviewing test cases. We need to set a reviewer's name for each test case in order to proof that someone checked for accuracy.

Today we solve it with custom fields
a) Enabled on Test Spec Design or
b) Test Plan Design

Unfortunately this is manual work and thereby unsafe.

We would like to force setting a user's/reviewer's name as reviewer when a new version of a test case is created and show that in the report

How do you deal with the problem?
fman
Member of TestLink Community
Posts: 3123
Joined: Tue Nov 15, 2005 7:19 am

Re: Best practises on test case review workflow

Post by fman »

At least since the version 1.9.17 you can write plugins to provide new features.
Using this approach you can add the missing feature.
You are going to need a custom development.
Adding a new field to the tcversions table is IMHO not an option if you want to have multiple reviewers.
The best approach is to create a new table testcase_reviewers ? where you can set the the user that have changed test case worflow status to reviewed.
But doing this right now you are going again to be able to save just one user, or be forced to change to a intermediate state and the again to reviewed.
This can be a FIRST working and simple implementation, that creates conditions for improvements

Please open a ticket on mantis in order to trace this feature
hmaier
TestLink user
Posts: 2
Joined: Sat Feb 03, 2018 9:33 am

Re: Best practises on test case review workflow

Post by hmaier »

Thank you fman for your fast reply, I'll look into that.
Post Reply