Bug 856799 - [rfe] Ability to delegate tester/multiple tester(s) after creating a test run
Summary: [rfe] Ability to delegate tester/multiple tester(s) after creating a test run
Keywords:
Status: NEW
Alias: None
Product: TCMS
Classification: Other
Component: Web UI
Version: Devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.0
Assignee: Yang Ren
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-12 20:00 UTC by Corey Welton
Modified: 2022-03-14 03:26 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Nitrate 3.8.0
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Corey Welton 2012-09-12 20:00:24 UTC
Description of problem:

We have a product with well over 200 testcases that need to be executed amongst multiple members on a team. 

When creating a test run, the run manager/creator has the ability to initially assign a default tester for all cases or leave that field blank.  However, after creation, there is no way to subsequently modify the Tester (or Assignee) fields to adequately delegate assignment execution.  

In short, you're left with a slew of testcases in a run that cannot in any easily measurable way be assigned out to multiple members on a team.

I'm not sure it's valid to assume that...

a) one user will execute all testcases in a run, or 
b) all cases are by default unassigned, leaving them basically in a "free-for-all" mode

...covers all valid use cases for creating test run.

Secondly, I'm not sure why these can't be changed after the fact, i.e., after creating a test run.

Comment 1 Corey Welton 2012-09-12 20:04:40 UTC
Edit: It does look like I can change Assignee using the Cases dropdown, but I'm not sure that's 100% adequate. A similar dropdown for "Tester" would be better.


Note You need to log in before you can comment on or make changes to this bug.