MantisBT - TestLink
View Issue Details
0008982TestLinkTest Execute - Filterspublic2020-08-19 06:352020-08-20 07:31
pamuditha 
fman 
highmajoralways
resolvedno change required 
dcker containerUbuntu16.04.3
1.9.19 (2019 Q1) 
 
mariadb
Google Chrome
PHP 7.3.13
TBD
0008982: Issues with executing test cases in multiple builds
When we have multiple Builds for a single Test Plan, all the test cases assigned for all the Builds are visible at test execution even the filters set as for specific build.
1-Create a Test Plan (Test 001)
2-Crete 2 Builds for that test plan (Build 1 and Build 2)
3-Goto Add Remove Test Cases
4-Add 5 test cases for Build 1
5-Add another 5 Test Cases for Build 2
6-Goto Test Execution and select the Test Plan
7-Check the default settings and filters
"Settings">>"Build to execute" set as Build 1
"Filters">>"on" set as "Build Chosen for execution"
8-Check only the 5 test cases assigned for Build 1 are available

Issue: Test Cases assigned for Build 1 and Build 2 are listed
Expected results: Only the test cases assigned for Build 1 should available

9-Change the "Filters">>"on" as "Specific Build"
10-Chose the Build 1 from the dropdown
11-Apply filter

Issue: Test Cases assigned for Build 1 and Build 2 all are listed
Expected results: Only the test cases assigned for Build 1 should available
No tags attached.
jpg Build issue.jpg (111,946) 2020-08-19 06:35
http://mantis.testlink.org/file_download.php?file_id=5384&type=bug
jpg
Issue History
2020-08-19 06:35pamudithaNew Issue
2020-08-19 06:35pamudithaFile Added: Build issue.jpg
2020-08-20 07:30fmanNote Added: 0029894
2020-08-20 07:31fmanQA Team - Task Workflow Status => TBD
2020-08-20 07:31fmanStatusnew => resolved
2020-08-20 07:31fmanResolutionopen => no change required
2020-08-20 07:31fmanAssigned To => fman

Notes
(0029894)
fman   
2020-08-20 07:30   
>> 3-Goto Add Remove Test Cases
>> 4-Add 5 test cases for Build 1
>> 5-Add another 5 Test Cases for Build 2
test case version are ADDED to the test plan NOT to the build, that's the way test link works

You can assign Tester Execution Task to different builds in order to do some kind of segregation, using additional filters