25
Test Automation for Manual Testing SQuAD March 2009 S. M. Allman [email protected] [email protected]
Test Automation for Manual Testing
SQuADMarch 2009S. M. Allman
[email protected]@softwarephilosophy.net
Overview
• Quick introductions• What is TestLink and why do you care?• Some simple examples• Lets take TestLink for a spin• More information about this tool• Questions from the audience
Introductions
• Me• You
– Open source automation tools?
– Ant, Java, php?– Microsoft tools:
MSWord and Excel?– Experience with
TestLink?
What is TestLink?
• Benefits– Clerical aspects of testing and reporting
• You write the test cases, and TestLink– Organizes them for a run– Acts as your lab notebook as you run tests– Publishes reports at any time, for all to see
Most Popular Testing Tool
• TestLink is the winning tool in the April 2008 survey.
• http://www.opensourcetesting.org/survey.php
TestLink Architecture
TestLink Home Page
Our Simple “Use Case” Questions
• Is it user friendly?• Are the benefits worth the costs?• Was performance good enough?• It is what the customer wanted?
Requirements (from the Use Cases)
• The System MUST be user friendly.• The System benefits SHALL BE worth the
costs.• The System performance MUST be good
enough.• The System MUST be what the customer
wanted.
Roles in TestLink
TestLink Usual Workflow (1)
• Administrator - creates a Test Project• Requirements (Optional)
– Leader import requirements– Tester updates the generated test cases
• Lead improves Test Cases– organizes Test Cases into Suites– Assigns keywords to Test Cases– Fills in procedures
• Lead authors a Test Plan
TestLink Usual Workflow (2)
• Lead - Starts a test round– Designates Test Cases to be run in a build– Assigns tests for each Test Case
• Tester – runs and records– Assigns an outcome– Adds any observations
• As you go along, at any time, generate reports
Optional Requirements
Test Suites and Cases
Fill in Test Procedures
Create Testers
Assign to Testers
Execute the Tests
Reports – TestLink’s Strength
• Available at any stage, to anyone• Browser, HTML or MSWord format• Many different reports
– Overall– By test round (they call them builds)– By failed, blocked, not run
• Charts
Reports
Complaints
• Awkward terminology – why not standardize?
• Confusing user interface and poor documentation can be frustrating
• Missing features for test procedures
Installation
• Overview of the process• How long does it take?
– Download and install XAMPP– Download and unzip TestLink
• A php script checks your computer• Startup of web server and database
Configuration
• Changing help text• Changing logos• Changing language• Peeking in the database• Customizing reports
Summary
• Cost effective• Image appropriate• Hassle free
