TestLink 1.9.3 (Prague)
is it possible to assign for execution of test case(s) to only 1 build/release?
steps:
1. create a test plan = TP100
2. create a build/release = BR100
3. add test case(s) to test plan
4. create another build/release = BR200
5. go to test execution
result:
if you select build to execute = BR200 > it will show the test case(s) for execution
expected result:
BR200 will NOT show any test case(s) for execution
Assign case(s) to only 1 build/release
Moderators: Amaradana, TurboPT, TL Developers
-
- TestLink user
- Posts: 4
- Joined: Thu Dec 02, 2010 9:36 am
Re: Assign case(s) to only 1 build/release
TL works this way:
what has to be executed can be defined JUST at (TestPlan + Platform) Level.
Builds/Releases are used in some way to identify new SET of test runs to be done.
You can exclude test from a new RUN using the TEST EXECUTION assignment feature, if you DO NOT ASSIGN to ANY tester test cases you do not want to execute.
TestCases WITHOUT tester assigned are excluded on several reports.
This technique has been implemented to allow a picture of testing process evolution.
hope is clear
what has to be executed can be defined JUST at (TestPlan + Platform) Level.
Builds/Releases are used in some way to identify new SET of test runs to be done.
You can exclude test from a new RUN using the TEST EXECUTION assignment feature, if you DO NOT ASSIGN to ANY tester test cases you do not want to execute.
TestCases WITHOUT tester assigned are excluded on several reports.
This technique has been implemented to allow a picture of testing process evolution.
hope is clear
-
- TestLink user
- Posts: 4
- Joined: Thu Dec 02, 2010 9:36 am
Re: Assign case(s) to only 1 build/release
thanks for the reply fman!
i am ok to implement as you've suggested.
i just wanted to know if there was a way to customize TL behavior to fit our flow of test execution/assignments. we use build/release independent from one another and test cases that are executed on one build/release may not need to be executed for another build/release so don't want them showing up.
i am ok to implement as you've suggested.
i just wanted to know if there was a way to customize TL behavior to fit our flow of test execution/assignments. we use build/release independent from one another and test cases that are executed on one build/release may not need to be executed for another build/release so don't want them showing up.
fman wrote:TL works this way:
what has to be executed can be defined JUST at (TestPlan + Platform) Level.
Builds/Releases are used in some way to identify new SET of test runs to be done.
You can exclude test from a new RUN using the TEST EXECUTION assignment feature, if you DO NOT ASSIGN to ANY tester test cases you do not want to execute.
TestCases WITHOUT tester assigned are excluded on several reports.
This technique has been implemented to allow a picture of testing process evolution.
hope is clear