The Way to Effective Automated Testing

Views:
 
     
 

Presentation Description

The Way to Effective Automated Testing

Comments

Presentation Transcript

The way to Effective Automated Testing :

The way to Effective Automated Testing Vladimir Primakov , Kuadriga 2012

Vladimir Primakov:

Vladimir Primakov QA Manager 9+ years in Software Testing Test Management Performance Testing Server-side and GUI Automated Testing v.v.primakov@gmail.com Skype: vladimir.primakov 2

AGENDA:

AGENDA 3 in an existing TA team of 2-3 TA engineers Tool: Language: VBScript Setup test-automation process

Problems:

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) …

What to automate?:

What to automate? Regression and acceptance tests (high-priority test-items only) ( T ested, stable , almost unalterable items ) Data - oriented tests 5 New Cycle Data 1 item Test run

Consistency to manual testing:

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

Consistency to manual testing:

Consistency to manual testing Same content and structure for manual and automated tests 7

Readable format of test results :

Readable format of test results 8 Same style for the a utomated and manual test results

Fast Test-Script Creation:

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.

Clear code:

Clear code Follow coding style guideline Define, document, and follow the standard AT approach & infrastructure 3) Use Name Mapping 10

Flexibility of TA scripts :

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

Stability of TA scripts:

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

Easy and Fast Run tests:

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.

Predictability in planning:

Predictability in planning 14 (TA Time / Manual Testing TIME) average = Factor average e.g.: 300 min/ 20 min = 15

What I would do now::

What I would do now: Continuous integration Version Control Systems Keyword-driven approach Distributed test runs 15

Vladimir Primakov:

Vladimir Primakov v.v.primakov@gmail.com Skype: vladimir.primakov 16

authorStream Live Help