vladimir primakov - test automation by example
DESCRIPTION
how Vladimir Primakov did test automation project. by http://automated-testing.infoTRANSCRIPT
A U T O M AT E D -T E S T I N G . I N F O
The way to EffectiveAutomated Testing
Vladimir Primakov, Kuadriga2012
A U T O M AT E D -T E S T I N G . I N F O
Vladimir Primakov
QA Manager• 9+ years in Software Testing• Test Management• Performance Testing• Server-side and GUI Automated Testing
[email protected] Skype: vladimir.primakov
2
A U T O M AT E D -T E S T I N G . I N F O
AGENDA
3
in an existing TA team of 2-3 TA engineers Tool:Language: VBScript
Setup test-automation process
A U T O M AT E D -T E S T I N G . I N F O
Problems
4
• What to automate?• Bad consistency with manual testing• Unreadable format of test results• Lack of clear code• No stability of TA scripts• No Flexibility of TA scripts (Data dependency)• A lot of time to create TA scripts• Difficult and long time to start automated tests• Absence of predictability (in planning)• …
A U T O M AT E D -T E S T I N G . I N F O
What to automate?
• Regression and acceptance tests (high-priority test-items only)
(Tested, stable, almost unalterable items)
• Data-oriented tests
5
New Cycle
Data1 item Test run
A U T O M AT E D -T E S T I N G . I N F O
Consistency to manual testing
• Use same organization, grouping, names for manual test cases and test automation scripts
6
Manual Test Item Test Complete Item
Product: Kuadriga Web-site Suite: KuadrigaWebSite
Test Object: Admin Project: Admin
Test Case: Admin_Search_TC_01.xmlx
Test Script: Admin_Search_TC_01.svb
A U T O M AT E D -T E S T I N G . I N F O
Consistency to manual testing
Same content and structure for manual and automated tests
7
A U T O M AT E D -T E S T I N G . I N F O
Readable format of test results
8
Same style for the automated and manual test results
A U T O M AT E D -T E S T I N G . I N F O
Fast Test-Script Creation
9
• Functional Decomposition / Framework building approach
• Stereotyping approach: Use suite, project, script, function, procedure, step, VP, etc. templates
• Document lessons learned: Test complete issues, coding samples, tips & tricks, etc.
A U T O M AT E D -T E S T I N G . I N F O
Clear code
1)Follow coding style guideline
2)Define, document, and follow the standard AT approach & infrastructure3) Use Name Mapping
10
A U T O M AT E D -T E S T I N G . I N F O
Flexibility of TA scripts
Take all changing data out of scripts Example: Keep test run settings in an external config.xml file:
– Path to the installation \ URL of a web-application,– Web-browser,– User Login, Password– Standard Delays,– Emails to sent test results (logs) to,– Any other useful information which should preferably be modified
externally.•
11
A U T O M AT E D -T E S T I N G . I N F O
Stability of TA scripts
12
Quit and Start the tested application regularly
Apply and follow standard Desktop, OS, and application settings
Make your scripts independent from other scripts
Apply error-handling Use error-avoiding code
A U T O M AT E D -T E S T I N G . I N F O
1. Fill in the config.xml file with the expected run settings.
13
Easy and Fast Run tests
2. Click the “startup” script.
3. Get easily understood test results on your email.
A U T O M AT E D -T E S T I N G . I N F O
Predictability in planning
14
(TA Time / Manual Testing TIME)average = Factoraverage
e.g.: 300 min/ 20 min = 15
A U T O M AT E D -T E S T I N G . I N F O
What I would do now:
• Continuous integration • Version Control Systems• Keyword-driven approach• Distributed test runs
15
A U T O M AT E D -T E S T I N G . I N F O
Vladimir Primakov
[email protected] Skype: vladimir.primakov
16