Easier Assignment of Test Cases

[danielm-p]

Hi there,

We chop and change our testers across projects/products quite frequently and I can foresee an operational concern with Zephyr if this occurs.

Currently to assign test cases to another user you need to navigate down to each individual folder you wish to assign, click the 'Assign' button and repeat for every other folder you want to change over. This will be quite time consuming each time we put a new resource on a project, or change the leadership (I have also noticed that changing the test lead on a project also does not assign the test cases over to them).

Would it be possible to allow the facility to cascade test case assignments down the tree if a higher-level folder is used? For example, I can select a Test Phase folder, click 'Assign' and select the tester(s) I want to assign the test cases to. Once I click 'Save', the assignments are applied to all test cases in all subfolders.

Many thanks,

Daniel

[danielm-p]

In addition, when you schedule an execution of a test phase, you are asked if you want to assign test cases to their respective creators. What will happen if a team member has been disabled (i.e. left) or has been de-assigned from the project?

In our case, we may assign a single tester to a project for a time and then may swap them over with another tester as necessary. We've found that if a project has a large number of folders containing test cases then there is no easy way to assign all test cases to an individual user, short of going to each individual folder, selecting all cases and then the user.

An option to assign all test cases in the test phase to a user or group of users (to allow work sharing) would also be highly desirable

(unless I have missed something?)

[danielm-p]

Having talked about this further with a number of testers in our team, our thoughts are as follows:

It would be great if any users assigned to those projects are able to view/edit existing test cases without then having to be assigned (this is quite cumbersome for bigger projects with large component trees).

The same goes for execution of test cases - being able to assign is nice, but if all testers working on a project are able to see test cases scheduled for execution then that is easier for the way we work. We may need to bring testers on board very quickly to pick up slack and this may be helpful.

Also, one further observation in that if we do want to assign test cases, it can be quite cumbersome to do them by one folder at a time. One way of facilitating faster bulk assignment is that if there is the ability to list all test cases for a phase in one big list? This could possibly sit as an option above the phase name in the component tree.



This screenshot should hopefully illustrate things a bit more. This is an example of one of our product sanity tests and these test cases have been worked on by a variety of testers. We typically only have one tester on the project at a time and it can be time consuming having to choose and assign test cases one folder at a time.

[ao5431]

Daniel,

We understand your frustration, such frequent changes are cumbersome and tedious. This is a feature that we are hoping to incorporate in an upcoming release.

Regards,

John

[malexs]

This is also something we are eagerly awaiting

We have thousands of test cases and folders and its not feasible to have to go into each and every folder to assign a test case. We want the ability to be able to select a folder and all its sub folders to assign. Similar to what the mapping requirements to test case screen where each element in the directory tree has a little checkbox in front of it.

Also, while working in an agile environment, its nice to be able to assign test cases to users. However things change often to the point where I may want to run some test cases previously assigned to someone else. In such a situation it would be ideal to be able to select an option on the Testcase Execution screen to show test cases for all users. Then I could run a test case assigned to someone else without having to go back to EAS and re-assign and then come back again and execute. Upon execution, the result would be that the test case is then assigned to me so that the metrics show that I executed the test case.

The nicest way to implement this may be to either assign this option to a manager or to create a new permission that sets weather a users role can see the select option on the Testcase Execution screen. That way it will not affect users that wish to have such strict security.

Optional: The select option could be simply an checkbox to show all test cases or to a listbox of all users in the project (as well as an "all" option). Selecting an item from the selectbox will change what test cases are shown.

[cometgrrl]

I would love something like this too. Often, I want to assign a bunch or all of the test cases, but it is tedious to have to go select each one and assign the tester. I want everyone on my team to be assigned to execute them, as we do a lot of project sharing, and if one person doesn't have time on a given day, someone else might, and it is a royal pain to go change the assignments just to execute a handful of tests.

[chris.miller]

Thank you all for your feedback on Test Case Assignment. We certainly use this input in our development plans. If you have any other constructive ideas, do include them in this area of community.

Kind Regards,
Chris

[malexs]

From the upcoming 3.0 release, this sounds like it could be implemented.... hope so

In Testcase Repository, assignments can be applied to at a particular node or cascaded to all sub-nodes or completely turned off

[ao5431]

That is correct, in 3.0 you have the functionality that you have been asking for to assign test cases in mass or you can disable this feature from the back end.

Regards,

John