Skip to content

Home

Jump to bottom
Francisco Mancardi edited this page Sep 23, 2018 · 22 revisions

Welcome to the Test Link - Open source Test and Requirements Management System

20180901 - Important Changes on next release (1.9.18)

TestLink 1.9.18 will be released with important changes regarding how different Test Specification and Requirement Specification will related among then, and with following artifacts:

  • test case attachments => test case version attachments
  • test case relations => test case versions relations
  • test case keywords => test case versions keywords
  • requirement attachments => requimente versions attachments
  • requirement coverage => requirement versions <-> test case versions links

When the test case version and requirement version concept were introduced, the simple past was to maintain the same old behavior were the main artifacts were the test case and the requirements.

This kind of behavior imposed some limits that were detailed by different users. One company decided to be the sponsor of a new development, that will be the new behavior since TestLink 1.9.18

TCA - Test Case Version Attachments

This concept will be transformed in Test Case Version Attachments Each Test Case Version will have its own attachments.

TCA.AM - Attachment Management when a new Test Case Version is created

When creating a new version of a test case, the attachments from the previous version should be copied.
This means that several instance/copies of the same files will exist on the file repository.

TCA.AU - Attachment Upgrade

If an upgrade to the attachments is needed in a version that can be edited, the outdated attachments will be removed manually and replaced by the updated attachments.

TCA.AMAE - Attachment Management After Test Case Version execution

it must not be possible:
a) to delete an attachment from that version of the test case.
b) to add an attachment from that version of the test case.

RQA - Requirements Version Attachments

This concept will be transformed in Requirement Version Attachments Each Requirement Version will have its own attachments.

RQA.AM - Attachment Management when a new Requirement Version is created

When creating a new version of a requirement, the attachments from the previous version should be copied.
This means that several instance/copies of the same files will exist on the file repository.

RQA.AU - Attachment Upgrade

If an upgrade to the attachments is needed in a version that can be edited, the outdated attachments will be removed manually and replaced by the updated attachments.

TCK - Test Case Version Keywords

This concept will be transformed in Test Case Version Keywords Each Test Case Version will have its own keywords.

TCK.LTCV Link to Test Case Version

Keywords will be related to the version of a Test Case, and not to the whole Test Case

TCK.NTCV - Keyword Management when a new Test Case Version is created

When creating a new version of a Test Case, the Keywords from the previous version should be copied. Because older versions will be setted frozen, no action on keywords will be possible.

TCK.BLK Block Keyword Management After Test Case Execution

After a test case version is executed, it must not be possible:
a) to delete a keyword from that version of the test case.
b) to add a keyword from that version of the test case.

TCR - Test Case Versions Relations

This concept will be transformed in Test Case Version Relations Each Test Case Version will have its own relations.

TCR.NTCV - Relation Management when a new Test Case Version is created.

When creating a new version of a Test Case, the Relations from the previous version should be copied.

TCR.NFRZ - The Relation must be frozen, this means that cannot be deleted, when one of the following events will happen:

a). a new version of any of the test case version part of the relation.
b). at the execution of any test case version part of the relation.

RQCOV - Requirement coverage => Req Version <-> Test Case Version link

Req - Test Case links, will become Req Version - Test Case Versions Links.

RQCOV.TCVEXEC - The link must be frozen at the execution of the test case

  1. Link cannot be deleted
  2. TC Version FROZEN
  3. REQ Version FROZEN

RQCOV - Use Case 01 - Create Req, Create Test Case, Create coverage link

  1. Create a requirement version 1
  2. Create a test case version 1
  3. Link the requirement (version 1) to the test case (version 1)

The user can not choose what TC Version or REQ Version to link, TestLink will use for both entities latest available versions. Then the link will be TC Version 1-REQ Version 1

RQCOV - Use Case 02 - Create Req, Create Several TC Versions, then Create coverage link

  1. Create a requirement version 1
  2. Create a test case version 1, then version 2, then version 3
  3. Link the requirement (version 1) to the test case (version 3)

The User can not choose what TC Version or REQ Version to link, TestLink will use for both entities latest available versions. Then the link will be TC Version 3-REQ Version 1 It will be impossible to create a coverage link from any REQ to TC Version 1 or TC Version 2

RQCOV - Use Case 03 - Create Req, Create Test Case, Then Create Several REQ Versions, then Create coverage link

  1. Create a requirement version 1
  2. Create a test case version 1
  3. Create a requirement version 2
  4. Create a requirement version 3
  5. Link the requirement (version 3) to the test case (version 1)

The user can not choose what TC Version or REQ Version to link, TestLink will use for both entities latest available versions. Then the link will be TC Version 1-REQ Version 3 It will be impossible to create a coverage link from any TC to REQ Version 1 or REQ Version 2

RQCOV - Use Case 04 - Create Req, Create Test Case, Create coverage link, Create TC Version = Automatic Coverage Link + Coverage Link and entities Frozen

  1. Create a requirement version 1
  2. Create a test case version 1
  3. Link the requirement (version 1) to the test case (version 1)

User can not choose what TC Version or REQ Version to link, TestLink will use for both entities latest available versions. Then the link will be TC Version1 - REQ Version 1

  1. Create a version 2 of the test case a. TestLink will automatically create a new link between REQ Version 1 and TC Version 2.
    b. Link 01 - TC Version 1 - REQ Version 1 will be FROZEN
    b.1 Link cannot be deleted
    b.2 TC Version 1 FROZEN
    b.3 REQ Version 1 FROZEN

c. Link 02 - TC Version 2 - REQ Version 1 -> is the ACTIVE Link

RQCOV - Use Case 05 - Create Req, Create Test Case, Create coverage link,Create REQ Version = Coverage Link Frozen

  1. Create a requirement version 1
  2. Create a test case version 1
  3. Link the requirement (version 1) to the test case (version 1)

The User cannot choose what TC Version or REQ Version to link, TestLink will use for both entities latest available versions. Then the link will be TC Version 1-REQ Version 1

  1. Create a version 2 for the requirement
  2. Link TC Version 1 - REQ Version 1 will be FROZEN. b.1 Link cannot be deleted
    b.2 TC Version 1 FROZEN
    b.3 REQ Version 1 FROZEN

c. Link 02 - TC Version 1 - REQ Version 2 -> is the ACTIVE Link

NCO - New Configuration Options related to Test Case Version Execution Effects

What can be done on attachments related to Test Case Version Specification

$tlCfg->testcase_cfg->downloadOnlyAfterExec = TRUE;

What will happen with related/linked Requirements Versions

$tlCfg->testcase_cfg->reqLinkingDisabledAfterExec = TRUE;

Effects on related Requirement Version (Freeze)

$tlCfg->testcase_cfg->freezeReqVersionAfterExec = TRUE;

Very Important Notice

This is a raw presentation of future changes, just to allow TestLink users to be alert regarding changes that will get, when upgrading to 1.9.18.

More detailed information is going to be available during the next weeks.

This new behavior will the only available, no options to continue with old behavior will be available. We think this will be a good improvement for TestLink, providing users fine grain control of entities and its relationships.

Clone this wiki locally