I am looking for a test management tool for my work and currently evaluating TestLink. I have read User Manual for TL v1.7 and would like to confirm the recommended workflow in section 1.3 of the user manual.
1. Administrator creates a Test Project;
2. Leader imports software requirements from external file;
3. Tester updates test cases that are generated during import of requirements;
4. Leader organizes test cases into test suites;
5. Leader assigns keywords to test cases;
6. Leader creates test plans;
7. Leader creates test build;
8. Leader assign test cases into test build;
9. Tester executes test cases in test build and record test result into test cases;
10. Repeat step 7 - 9 until tests on all requirements passed;
11. Manager generates test report.
Please advise whether the above understanding is correct. Thank you.
Recommended workflow in TestLink
Moderators: Amaradana, TurboPT, TL Developers
TestLink process for test execution
I have a similar question.
We are impressed with TestLink and would like to use it. However, there is a difference in the test execution process and our test execution process.
We do not anticipate executing the same test cases through each cycle of testing before release.
For example, after the first cycle, we find a defect and determine that a test case needs to be written for it and needs to be executed in the next cycle. The test case is written and added to the test execution list.
This is where the problem comes in. TestLink automatically changes the stats in the first (closed) cycle to include the test case added for the second cycle.
In other words, the first cycle is completed with 100% execution. A test case is added to the second cycle. The first, closed cycle, is then changed to less than 100% complete.
Is there any way to change the process flow so that when cycle 1 is complete, any addition or deletion of test cases to the 2nd cycle are not reflected in the first?
I hope I was clear enough on that.
Thanks for any help,
Jena
We are impressed with TestLink and would like to use it. However, there is a difference in the test execution process and our test execution process.
We do not anticipate executing the same test cases through each cycle of testing before release.
For example, after the first cycle, we find a defect and determine that a test case needs to be written for it and needs to be executed in the next cycle. The test case is written and added to the test execution list.
This is where the problem comes in. TestLink automatically changes the stats in the first (closed) cycle to include the test case added for the second cycle.
In other words, the first cycle is completed with 100% execution. A test case is added to the second cycle. The first, closed cycle, is then changed to less than 100% complete.
Is there any way to change the process flow so that when cycle 1 is complete, any addition or deletion of test cases to the 2nd cycle are not reflected in the first?
I hope I was clear enough on that.
Thanks for any help,
Jena
Francis,
I can confirm, that this procedure is the main intended process. There are differences between particular teams how to use it. So we try to allow particular differences from this scenario. For example some users would like to share test plan between several test projects, etc.
Jena,
You are right, that there is a small inconsistence in later results. However I think that it's acceptable. Managers could look at results after the first cycle and see correct temporary result. They interesting in the final (latest) results in the time of closing Test Plan. So the first round is not important for them later.
The problem is, that technical solution of this problem. It means, that relations between data will be more difficult and maybe also slow down the system.
You can add request into our tracker of course. But you can see that we have amount of issues to solve.
I can confirm, that this procedure is the main intended process. There are differences between particular teams how to use it. So we try to allow particular differences from this scenario. For example some users would like to share test plan between several test projects, etc.
Jena,
You are right, that there is a small inconsistence in later results. However I think that it's acceptable. Managers could look at results after the first cycle and see correct temporary result. They interesting in the final (latest) results in the time of closing Test Plan. So the first round is not important for them later.
The problem is, that technical solution of this problem. It means, that relations between data will be more difficult and maybe also slow down the system.
You can add request into our tracker of course. But you can see that we have amount of issues to solve.
This should have two meanings:
1. Test Specification is structured via Test Suites. So you can choose Edit Test cases, select Test Project node in navigation and create one or more Test Suites.
2. You have created Test Suites in Test Specification. Now you can assign test cases into a Test Plan. You don't care about assign Test Suites. The test suite structure is automatically copied if you assign TC(s).
1. Test Specification is structured via Test Suites. So you can choose Edit Test cases, select Test Project node in navigation and create one or more Test Suites.
2. You have created Test Suites in Test Specification. Now you can assign test cases into a Test Plan. You don't care about assign Test Suites. The test suite structure is automatically copied if you assign TC(s).
Thank you.
Now, I realize that when a requirement is added to a requirement document, a test suite and test case will be generated automatically. The test suite bears the title of the requirement document and test case bears the title of requirement. This has confused me because I used requirement document and requirement 1 and 2 for my evaluation. It makes me think the test suite and test cases are the actual requirement document and requirements.
Now, I can move onto the next step.
Now, I realize that when a requirement is added to a requirement document, a test suite and test case will be generated automatically. The test suite bears the title of the requirement document and test case bears the title of requirement. This has confused me because I used requirement document and requirement 1 and 2 for my evaluation. It makes me think the test suite and test cases are the actual requirement document and requirements.
Now, I can move onto the next step.
Sequence of test cases within a test plan
Hi all,
First of all, congratulations to the developers team for TestLink, it is been a huge step for us to explore it.
My doubt:
When assigning test cases to a test plan, is there a way to define a specific sequence for the cases within the test plan?
In my case, sometimes it is interesting within a test plan to have a specific sequence for the cases/suites to be executed (different than the way done in the test suites).
Regards and thanks a lot
Rodrigo Aznar
First of all, congratulations to the developers team for TestLink, it is been a huge step for us to explore it.
My doubt:
When assigning test cases to a test plan, is there a way to define a specific sequence for the cases within the test plan?
In my case, sometimes it is interesting within a test plan to have a specific sequence for the cases/suites to be executed (different than the way done in the test suites).
Regards and thanks a lot
Rodrigo Aznar
The use of TestLink Build
Hi all,
I got confused on how TestLink Build works.
I am using TL 1.8.0 Beta 1 and I have noticed the following behaviour:
Suppose I´ve executed a build (TL Build) of a certain Test Plan and some test cases failed and other get blocked (most likely case).
In such case, I am assuming the next steps are:
- have a new build of the software/product to be tested
- in TL, build management, create a new Build (lets say Build 2)
- execute the Build 2, filtering just the blocked and failed test cases in the option "Navigation Filter & Settings ".
When I filter the Build 2 no test case appears. I am assuming that a new Build that follows a not passed Build would carry all the previous results. I am assuming that each product build would need a new Build in TL.
It seems like a TL Build is intended to be re-executed until all TCs pass. Then a new TL Build (same TP) would make sense only for a new version of the product to be tested (with new features), is it the point?
thanks a lot
I got confused on how TestLink Build works.
I am using TL 1.8.0 Beta 1 and I have noticed the following behaviour:
Suppose I´ve executed a build (TL Build) of a certain Test Plan and some test cases failed and other get blocked (most likely case).
In such case, I am assuming the next steps are:
- have a new build of the software/product to be tested
- in TL, build management, create a new Build (lets say Build 2)
- execute the Build 2, filtering just the blocked and failed test cases in the option "Navigation Filter & Settings ".
When I filter the Build 2 no test case appears. I am assuming that a new Build that follows a not passed Build would carry all the previous results. I am assuming that each product build would need a new Build in TL.
It seems like a TL Build is intended to be re-executed until all TCs pass. Then a new TL Build (same TP) would make sense only for a new version of the product to be tested (with new features), is it the point?
thanks a lot
Hi,
I'm on TestLink 1.7.4 and I'm encountering the same situation of Nazar.
E.g:
In my testplain I have 10 testcases. For build #1, 5 testcases pass and 5 testcases fail. In buid #2, it contains the fixes for the 5 failing testcases. I only want to filter and execute the 5 failing test against build #2 and not all 10 testcases.
Will upgrading to the latest version of 1.8 resolve my situation?
I'm on TestLink 1.7.4 and I'm encountering the same situation of Nazar.
E.g:
In my testplain I have 10 testcases. For build #1, 5 testcases pass and 5 testcases fail. In buid #2, it contains the fixes for the 5 failing testcases. I only want to filter and execute the 5 failing test against build #2 and not all 10 testcases.
Will upgrading to the latest version of 1.8 resolve my situation?
Facing the same issue
I am using Testlink 1.7.5 version and i am facing the same issues
I was under the assumption that a new Build that follows a not passed Build would carry all the previous results. But when i create a new build none of the results of the previous build are propogated.
So we have decided to update the same build and use it until all the test cases are passed?? Please let me know of any issues due to this ?
Has this been fixed in the new version 1.8 ???
Thanks
Usha
I was under the assumption that a new Build that follows a not passed Build would carry all the previous results. But when i create a new build none of the results of the previous build are propogated.
So we have decided to update the same build and use it until all the test cases are passed?? Please let me know of any issues due to this ?
Has this been fixed in the new version 1.8 ???
Thanks
Usha
