testlink.org
| Anonymous | Login | Signup for a new account | 2019-04-20 05:28 UTC |  |
| Main | My View | View Issues | Change Log | My Account |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0003770 | TestLink | Requirement Management | public | 2010-09-10 23:03 | 2019-04-02 20:41 | ||||
| Reporter | apugohome | ||||||||
| Assigned To | fman | ||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 1.9 Beta 6 | ||||||||
| Fixed in Version | 1.9.18 (2018 Q3) | ||||||||
| Summary | 0003770: Existing test cases are always assigned to the latest version of a requirement | ||||||||
| Description | When a new version of a requirement is created, all linked test cases are linked to the latest version. Is there a way to implement the coverage so that test cases are linked to a specific version of a requirement? | ||||||||
| Steps To Reproduce | -Create a requirement -link to a test case -Create a new version of the requirement -Test case is now linked to the latest version of the requirement | ||||||||
| Additional Information | Sometimes a requirement changes and the corresponding set of test cases have to be updated to account for the change in the requirement. However, existing test cases should ideally not be affected and should be able to point to the previous version of the requirement. | ||||||||
| Tags | OUTDATED TEST CASES | ||||||||
| Database (MySQL,Postgres,etc) | mysql 5.1.49 | ||||||||
| Browser | |||||||||
| PHP Version | |||||||||
| TestCaseID | |||||||||
| QA Team - Task Workflow Status | TBD | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0011329) Julian (reporter) 2010-09-11 07:06 edited on: 2010-09-11 07:15 |
this is a feature to be discussed for testlink 2.0 for 1.9 there won't be a change In my eyes it will be a real pain to link a requirement to multiple tc versions. think of the effort when you want to update the linked version(s) of a tc. i would prefer some mechanism like this: - requirements are linked to "latest" test case version - if requirement is edited all linked test cases get an indicator that they are maybe outdated - via an extra page to "show outdated test cases" the user is able to mark test cases as "not outdated" -> reset indicator. test cases that are really outdated can be edited and then be marked as "not outdated" |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2010-09-10 23:03 | apugohome | New Issue | |
| 2010-09-11 07:06 | Julian | Note Added: 0011329 | |
| 2010-09-11 07:15 | Julian | Note Edited: 0011329 | View Revisions |
| 2010-09-12 12:58 | fman | Status | new => feedback |
| 2012-11-25 18:11 | fman | Tag Attached: OUTDATED TEST CASES | |
| 2019-01-19 15:10 | fman | QA Team - Task Workflow Status | => TBD |
| 2019-01-19 15:10 | fman | Status | feedback => resolved |
| 2019-01-19 15:10 | fman | Fixed in Version | => 1.9.18 (2018 Q3) |
| 2019-01-19 15:10 | fman | Resolution | open => fixed |
| 2019-01-19 15:10 | fman | Assigned To | => fman |
| 2019-04-02 20:41 | fman | Status | resolved => closed |
|
Issue History |
| Copyright © 2000 - 2019 MantisBT Team |
 |