Difference between revisions of "QA/Testlink"
Terry Yang (Talk | contribs) (Created page with "== Introduction == '''TestLink''' is a web-based software that facilitates software quality assurance. It is developed and maintained by Teamst. The platform offers support for …") |
Terry Yang (Talk | contribs) (→WorkFlow) |
||
| Line 19: | Line 19: | ||
== WorkFlow == | == WorkFlow == | ||
| − | 1.Administrator creates a Test Project | + | #1.Administrator creates a Test Project |
| − | 2.User imports or create Software Requirements and for part of these requirements generates empty Test Cases. | + | #2.User imports or create Software Requirements and for part of these requirements generates empty Test Cases. |
| − | 3.Describes a test scenario (create a content of empty Test Cases) using these Test Specification that is organized into Test Suites. | + | #3.Describes a test scenario (create a content of empty Test Cases) using these Test Specification that is organized into Test Suites. |
| − | 4.Creates keyword “Regression testing” and assigns this keyword to ten of these Test Cases. | + | #4.Creates keyword “Regression testing” and assigns this keyword to ten of these Test Cases. |
| − | 5.Creates a Test Plan , Build and links all Test Cases in Test Suite to this Test Plan. | + | #5.Creates a Test Plan , Build and links all Test Cases in Test Suite to this Test Plan. |
| − | 6.Now developers produce a first build. Tester execute and record the testing with the result. | + | #6.Now developers produce a first build. Tester execute and record the testing with the result. |
| − | 7.Developers make a new Build and tester tests the failed and blocked Test Cases only. This time these all blocked and failed Test Cases passed. They retest also all Test Cases with keywords “Regression testing” in addition. | + | #7.Developers make a new Build and tester tests the failed and blocked Test Cases only. This time these all blocked and failed Test Cases passed. They retest also all Test Cases with keywords “Regression testing” in addition. |
| − | 8.After test done, We can generat test report | + | #8.After test done, We can generat test report |
Revision as of 06:59, 14 August 2012
Introduction
TestLink is a web-based software that facilitates software quality assurance. It is developed and maintained by Teamst. The platform offers support for test cases, test suits, test plans, test projects and user management, as well as various reports and statistics. For more detail info mathine about this tool you can get it form Test Link wikipedia and Test Link.
Usage
The basic units used by TestLink are: Test Case, Test Suit, Test Plan, Test Project and User.
Test Case describes a testing task via steps (actions, scenario) and expected results. Test Cases are the fundamental piece of TestLink.
Test Suite (Test Case Suite) organizes Test Cases to units. It structures Test Specification into logical parts.
Test Plan is created when you'd like to execute Test Cases. Test Plans can be made up of the Test Cases from the current Test Project. Test Plan includes Builds, Milestones, user assignment and Test Results.
Test Project is something that will exist forever in TestLink. Test Project will undergo many different versions throughout its lifetime. Test Project includes Test Specification with Test Cases, Requirements and Keywords. Users within the project have defined roles.
User: each TestLink user has a Role that defines available TestLink features. See more in chapter “User Administration”. Illustration 2 shows common activities according to user roles.
WorkFlow
- 1.Administrator creates a Test Project
- 2.User imports or create Software Requirements and for part of these requirements generates empty Test Cases.
- 3.Describes a test scenario (create a content of empty Test Cases) using these Test Specification that is organized into Test Suites.
- 4.Creates keyword “Regression testing” and assigns this keyword to ten of these Test Cases.
- 5.Creates a Test Plan , Build and links all Test Cases in Test Suite to this Test Plan.
- 6.Now developers produce a first build. Tester execute and record the testing with the result.
- 7.Developers make a new Build and tester tests the failed and blocked Test Cases only. This time these all blocked and failed Test Cases passed. They retest also all Test Cases with keywords “Regression testing” in addition.
- 8.After test done, We can generat test report
