TEST LINK TRAINING. Author : Tran Ngoc Dan Phuong Date : 24/5/2011 Time : 2h. Agenda . About Test Link Benefit of Test Link Test Case Process Management with Test Link How to work with Test Link Tasks of QC Leader Tasks of QC Member Troubleshooting Q&A. About Test Link.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
TEST LINK TRAINING Author: Tran Ngoc Dan Phuong Date: 24/5/2011 Time: 2h
Agenda • About Test Link • Benefit of Test Link • Test Case Process Management with Test Link • How to work with Test Link • Tasks of QC Leader • Tasks of QC Member • Troubleshooting • Q&A
About Test Link • Test management tool based on PHP & MySQL • Create and manage test • Track test results dynamically, generate reports, trace software requirements, prioritize and assign.
Benefit of Test Link • Open source • Easy to maintenance for multiple projects • Centralized Repository for all test cases • Centralized Repository for all test results • Integrate with bug tracking tool (Mantis, Bugzilla, Jira…) • Integrate with automation tool ( Selenium…) • Multiple reports and charts can viewed
Test Case Process Management with Test Link • Actors will be interacted with Test Link • QC Manager • QC Leaders • QC Members • Guest (BA, PM, QA, Dev, Higher manager…)
Some relationship between objects • 1 Test Project -> n Test Plans/ n Custom Fields • 1 Test Plan -> n Milestones • 1 Test Plan -> n Builds • 1 Test Plan -> n Platforms • 1 Build -> n Test Suites • 1 Test Suite -> n Test Cases • 1 Test Case -> n TC Versions / n Keyword • 1 Test Case -> 1 Requirement • 1 TC Version -> n Test Results
How To Work with Test Link • Tasks of QC Leader • Preparation • Get all information from project plan (Schedule, Timeline, Milestone, Resources, Features need to be tested or not…) • Prepare all necessary information for testing • To do • Step 1:Create new Test Project/ new Test Plan • Format: TP_ProjectName_Phase • Enable requirements ( if having) • Enable Testing Priority ( if having) • Enable Test Automation ( if having) • Enable Inventory (if having)
How To Work with Test Link (cont’d) • Step 2: (optional) Create Users • Create account login for users • Assign roles, permission • Assign user to project • Step 3: Create Milestone (depend on iterations or phases of each of specific project) • Format: • Milestone = M1_yyyymmdd • Phase = P_yyymmdd • Start Date, End Date • Percentage commitment high priority test cases will be executed
How To Work with Test Link (cont’d) • Step 4: Create/ assign Custom Fields to Test Plan • Purpose: Extend the most important objects • Format: CF_Name • Common: pre-defined custom fields will be applied for all projects (Defined by Admin) • Specific: custom fields will be defined for each project • Example: • CF_ReviewingStatus (New, Reviewed, Rejected, Approved…) • CF_EstimatedExecutionTime • CF_ExecutionTime • Assign: assign and enable on Design or Execution TC Phase
How To Work with Test Link (cont’d) • Step 5: Create Keyword • Purpose: Filter or categorize • Format: KW_Name • Common: pre-defined keywords will be applied for all projects (Defined by Admin) • Specific: keyword will be defined for each project • Example: • KW_SanityTesting • Assign: to test cases/ test suites
How To Work with Test Link (cont’d) • Step 6: Create/ assign Platform to Test Plan • Purpose: describle a unit that test cases could be executed on • Format: PF_Name • Common: pre-defined platforms will be applied for all projects (Defined by Admin) • Specific: platform will be defined for each project • Example: • PF_Window7 • PF_Mac OS • Assign: to Test Plan
How To Work with Test Link (cont’d) • Step 7 : Create Inventory • Purpose: define information of server , client environment • Format: INV_Name Notes: --- Create Release/Build after Dev Lead release build notes. Use the same build number (Build = B1_DevBuildReleaseNumber) --- To specific projects, can use external or internal build --- Import Test Case to System if using template TCs
How To Work with Test Link (cont’d) • Tasks of QC Member • Step 1: Create Requirements • Purpose: manage outline test requirements • Format: • New Specs: REQ_UCName • CRs: CR_UCName(ID) (Link to Jira issues) • Step 2: Write Test Cases/ Assign Keyword , Requirements • Write TCs • Format Test Case Title: PrefixProject_ID_PrefixModule/Features_ShortSummary • Prefix: get 2 first characters of string • Example: FA_1_ETA_EditETAsuccessfully
How To Work with Test Link (cont’d) • Assign Keyword to test cases • Assign Requirements to test cases • Update test cases after reviewing • Step 3: Execute TCs, Update Test Results, Test Report • Step 4: Update Test Case and Test Requirements when having CRs