Difference between revisions of "QA/Testlink"

From Apache OpenOffice Wiki
< QA
Jump to: navigation, search
Line 18: Line 18:
 
'''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.
 
'''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.
+
'''User''': each TestLink user has a Role that defines available TestLink features. [http://aootesting.adfinis-sygroup.org/docs/testlink_user_manual.pdf user manual] See more in chapter “User Administration”. Illustration 2 shows common activities according to user roles, for our project, ther are only 2 roles, Tester and QA leader, Tester can create Test case, run test case, log result and open defect. For QA leader, it will manage whole test project, like create test plan, manage test plan, create test report and so on.
  
 
== WorkFlow ==
 
== WorkFlow ==
#Administrator creates a Test Project  
+
#QA leader creates a Test Project  
#User imports or create Software Requirements and for part of these requirements generates empty Test Cases.  
+
#Tester imports or create Software Requirements and for part of these requirements generates empty Test Cases.  
#Describes a test scenario (create a content of empty Test Cases) using these Test Specification that is organized into Test Suites.
+
#Tester Describes a test scenario (create a content of empty Test Cases) using these Test Specification that is organized into Test Suites.
#Creates keyword “Regression testing” and assigns this keyword to ten of these Test Cases.
+
#Tester Creates keyword “Regression testing” and assigns this keyword to ten of these Test Cases.
#Creates a Test Plan , Build  and links all Test Cases in Test Suite to this Test Plan.  
+
#QA leader Creates a Test Plan , Build  and links all Test Cases in Test Suite to this Test Plan,  assign test case to every tester.  
 
#Now developers produce a first build. Tester execute and record the testing with the result.
 
#Now developers produce a first build. Tester execute and record the testing with the result.
 
#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.
 
#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.
#After test done, We can generat test report
+
#After test done, QA leader can generat test report
  
 
== Step Create User==
 
== Step Create User==
Line 34: Line 34:
 
#Logon [http://aootesting.adfinis-sygroup.org http://aootesting.adfinis-sygroup.org] with the user you create in step 1.  
 
#Logon [http://aootesting.adfinis-sygroup.org http://aootesting.adfinis-sygroup.org] with the user you create in step 1.  
  
== Step To New Test Case ==
+
== Step To New Test Case for tester ==
 
Need Create Requirement first, then create Test Case and Assign Test case with Requirement.
 
Need Create Requirement first, then create Test Case and Assign Test case with Requirement.
 
#Select the Project, then Click '''Requirement Specification''' in left panel, in the Root folder, click '''Create''' button to create a Requirement Specification[[File:CreateRequirement Specifications.jpg]]
 
#Select the Project, then Click '''Requirement Specification''' in left panel, in the Root folder, click '''Create''' button to create a Requirement Specification[[File:CreateRequirement Specifications.jpg]]
Line 48: Line 48:
  
  
== Step to Assign TestCase to Test Plan ==
+
== Step to Assign TestCase to Test Plan for QA leader ==
 +
QA leader need create test plan and add test case to Test plan, also need set others for test plan, like which build used for test plan, which platform need cover in test plan.
  
 +
1.Create and active Test Plan from Test Plan Management
 +
 +
[[File:TestPlan.PNG]]
 +
 +
2.Choose Platform need test in this Test Plan, "Add/Remove Platforms" in "Test Plan contents" list.
 +
 +
[[File:AssignTester.PNG]]
 +
 +
3.Click "Test Specification "button on menu bar
 +
 +
4.Double Click Specific Case Which you want to add to Test Plan
 +
 +
5.Click "Add to Test Plans" button on available operation view, like,
 +
 +
[[File:AddToPlan.PNG]]
 +
 +
[[File:AddToPlan2.PNG]]
 +
 +
6.Check the specific Plan and Platform
 +
 +
7.Create Specific build from "Builds/Releases"
 +
 +
[[File:TestPlanBuild.PNG]] 
 +
 +
(build version bind with test plan ,and tester can't change build version in the process of test execution)
 +
 +
8.Assign Tester from "Assign Test Case Execution"
 +
 +
[[File:AssignTester.PNG]]
 +
 +
then you can assign Test Suite or Test Case to specific tester.Maybe this function need to improve to adapt community mode.
  
 
== Step to Run Test Case and input result ==
 
== Step to Run Test Case and input result ==
  
 
== Step to General Test Report ==
 
== Step to General Test Report ==

Revision as of 05:48, 16 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. You also can download the user manual to learn it in detail.

Our TestLink is http://aootesting.adfinis-sygroup.org

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. user manual See more in chapter “User Administration”. Illustration 2 shows common activities according to user roles, for our project, ther are only 2 roles, Tester and QA leader, Tester can create Test case, run test case, log result and open defect. For QA leader, it will manage whole test project, like create test plan, manage test plan, create test report and so on.

WorkFlow

  1. QA leader creates a Test Project
  2. Tester imports or create Software Requirements and for part of these requirements generates empty Test Cases.
  3. Tester Describes a test scenario (create a content of empty Test Cases) using these Test Specification that is organized into Test Suites.
  4. Tester Creates keyword “Regression testing” and assigns this keyword to ten of these Test Cases.
  5. QA leader Creates a Test Plan , Build and links all Test Cases in Test Suite to this Test Plan, assign test case to every tester.
  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, QA leader can generat test report

Step Create User

  1. Open http://aootesting.adfinis-sygroup.org, Click New User? link, input your user name/password/Email and click Add User Data. Then your account create.
  2. Logon http://aootesting.adfinis-sygroup.org with the user you create in step 1.

Step To New Test Case for tester

Need Create Requirement first, then create Test Case and Assign Test case with Requirement.

  1. Select the Project, then Click Requirement Specification in left panel, in the Root folder, click Create button to create a Requirement SpecificationCreateRequirement Specifications.jpg
  2. Input Document ID/Title/Scope Click Save button CreateRequirementSpecifications.jpg
  3. Click the Requirement Specifications you create in step 2 in left panel, click the Create button under Requirement Operations
  4. Input Document ID/Title/Scope/Case number and Click Save buttonCreateRequirement.jpg
  5. Click Test Specification link go the Test Specification page, Go to root folder in left panel, click Create button to create a Test Suite.CreateTestSuite.jpg
  6. Input Test Suite Name like Apache OpenOffice Writer, then click Create Test Suite button to create Writer test suite, do same to create a sub test suite Table under Write.
  7. Click the sub test suite, click Create button under Test Case OperationsCreate TestCase.jpg
  8. Input Test Case Title like "Insert table", Summary,Preconditions, select Execution Type, select Test importance and assign Keyword then Click create button to create a Test Case
  9. The test case create successfully, now Click Create steps to create test case steps
  10. Go to project home page, Click Assign Requirements Link, Select the Test case you create, select correct Assign Requirements, check the Available Requirements, click Assign button.


Step to Assign TestCase to Test Plan for QA leader

QA leader need create test plan and add test case to Test plan, also need set others for test plan, like which build used for test plan, which platform need cover in test plan.

1.Create and active Test Plan from Test Plan Management

TestPlan.PNG

2.Choose Platform need test in this Test Plan, "Add/Remove Platforms" in "Test Plan contents" list.

AssignTester.PNG

3.Click "Test Specification "button on menu bar

4.Double Click Specific Case Which you want to add to Test Plan

5.Click "Add to Test Plans" button on available operation view, like,

AddToPlan.PNG

AddToPlan2.PNG

6.Check the specific Plan and Platform

7.Create Specific build from "Builds/Releases"

TestPlanBuild.PNG

(build version bind with test plan ,and tester can't change build version in the process of test execution)

8.Assign Tester from "Assign Test Case Execution"

AssignTester.PNG

then you can assign Test Suite or Test Case to specific tester.Maybe this function need to improve to adapt community mode.

Step to Run Test Case and input result

Step to General Test Report

Personal tools