A I d i S f T A I d i S f T An Introduction to Software Test An Introduction to Software Test Automation Automation (during the Testing Process) (during the Testing Process) Automation Automation (during the Testing Process) (during the Testing Process)

Author: Eduardo Filho

Automation ConstantsAutomation ConstantsKnowledge of the App (Test Team) RequiredIt’s not easyIt s not easy.A skilled person is needed.Thinking on Architecture (modules) is crucial.Thinking on Architecture (modules) is crucial.Communication – Automator, Test Team.Test and stress the script (nonworking < nothing).p ( g g)Maintenance is crucial.Must be simple.Environment must be stable.The effort need templates.Communication with Dev/Env team is crucial.Small and reliable > Big and not reliable

2

Purpose of AutomationPurpose of AutomationPurpose of AutomationPurpose of Automation

To help test:To help test:

Broader – wider testing coverage of more features.AND/ORDeeper – more extensive variations within a feature.

AND/ORFaster test tools execute tests between 10 and Faster – test tools execute tests between 10 and 100 times faster than a human executes it.

3

Automation ProsAutomation ProsAutomation ProsAutomation Pros

ReliableFastFastDeeppBroadM d l d (R bl )Modularized (Reusable)Compact (10 Manual become 3 automated)Compact (10 Manual become 3 automated)

4

Automation ConsAutomation ConsAutomation ConsAutomation Cons

B ld d h d h Building an automated test is harder than create a manual one.Needs a SKILLED personHarder to maintainTakes longer to be builtTakes longer to be builtDepends on the App’s Interface, etc..p ppConstant change may be an issue.

5

The Automator ProfileThe Automator ProfileThe Automator ProfileThe Automator ProfileSTRONG knowledge on programming logics.STRONG knowledge on programming logics.Capacity of simplifying complex logics.C i f i lif i i ( j k h Capacity of simplifying scripts (not just make them shorter) .STRONG communication skills.Good knowledge of software testing.Patient.Creative inventive Creative, inventive Perfectionist.

6

AutomationAutomation ToolToolVendorsVendorsAutomationAutomation ToolToolVendorsVendors

7

AutomationAutomation ToolsTools marketmarketAutomationAutomation ToolsTools marketmarket

8

Automation BasicsAutomation Basics

1 Requirement To Many Scenarios1 Requirement To Many ScenariosReq 1: Google must perform searches.

1 Scenario To Many 1 Scenario To Many TestCasesTestCasesS i 1 Titl b t h th h d t i ft S kScenario1:Title bar must show the searched string after Seek.

Scenario2:String searched must be bold at the result list

Case 1:Dell, Case 2:Sony, Case 3:Asus

1 Test Script to Many 1 Test Script to Many TestCasesTestCasesTest Script 1:Title bar must show <<< Value>>> string after Seek.

Automation Basics (Design for testability)

One Step in a Manual Test Script One Step in a Manual Test Script Step N - Title bar must show <<< Value>>> string after Seek.

ValueDELL

1 Manual Test ScriptIBM

HP

1 Manual Test Script

3 Test Cases

One Step in 3 Manual Test CasesOne Step in 3 Manual Test CasesppStep N - Title bar must show “DELL” string after Seek.

Step N Title bar must show “IBM” string after SeekStep N - Title bar must show IBM string after Seek.

Step N - Title bar must show “HP” string after Seek.

Which is Easier to Automate? Which is Easier to Automate? (Design for testability)(Design for testability)StepStep NameName DescriptionDescriptionStep 1Step 1 Go to GoogleStep 2Step 2 Search the string "Dell"

OR

StepStep 33 Verify whether the browser title has change properly or not.

StepStep NameName DescriptionDescriptionStepStep 11 Open Internet Explorer 6StSt 22 N i t t "htt // l "StepStep 22 Navigate to "http://www.google.com"StepStep 33 Type <<<Value>>> into the search text boxStepStep 44 Click on the "Google Search" button

Aft th lt i l d d if h th V lStepStep 55

After the results page is loaded, verify whether <<<Value>>> appears on the browser title bar or not.

StepStep 66 Close Internet Explorer 6

ValueDELL

IBM

HP11

Test Automation & Agile MethodsTest Automation & Agile Methods

•Agile projects need a very strong automation strategyautomation strategy.•The environment must be stable.•Design for testability must be followed•Communication with dev and modularity yis crucial.

Approach: When one sprint is finished, while a tester focus on next sprint testswhile a tester focus on next sprint tests, we can automate the previous sprint, as

12

long as the requirements won’t change.

13