1 / 14

How to understand when a project needs automation

http://qatestlab.com/ Purposes of test automation: to improve the effectiveness of testing, to accelerate testing, to make testing transparent, to reduce expenses on testing

qatestlab
Download Presentation

How to understand when a project needs automation

An Image/Link below is provided (as is) to download presentation 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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ivanna Kyryk Program Manager at QATestLab How to understand when a project needs automation James Briers Co-Founder and Delivery Director at Intelligent DS

  2. 2 Agenda Purposes of test automation Prerequisites for automation Start of automation Test Automation Pyramide Reasons of automation fail © QATestLab. All rights reserved.

  3. 3 Purposes of test automation • To improve the effectiveness of testing • To accelerate testing • To make testing transparent • To reduce expenses on testing © QATestLab. All rights reserved.

  4. 4 Manual Testing Initial Investment Cumulative Cost Saving Cumulated Costs ($) Automated Testing Time © QATestLab. All rights reserved.

  5. 5 Aspects to consider Project size Team size Generation of test data Release frequency Support of old versions © QATestLab. All rights reserved.

  6. 6 How to start automation? • Define what to automate • Determine ways of automation • Select means for automation © QATestLab. All rights reserved.

  7. 7 What to automate? • Frequently used functionality • Repetitive actions • Tests with multiple data sets • Tests for different software and hardware configurations • Time-consuming tests • Calculating algorithms, etc. © QATestLab. All rights reserved.

  8. 8 What NOT to automate? • Newly created tests • Ad Hoc tests • Projects with fast-changing requirements • Unstable functionality © QATestLab. All rights reserved.

  9. 9 Test Automation Pyramid Automated GUI Tests Automated API Tests Automated Integration Tests Automated Component Tests Automated Unit Tests © QATestLab. All rights reserved.

  10. 10 How to select automation tool? • Do not use beta versions and unstable tools • Tools should correspond to the specifics of your software • Use feature-rich tools with trial period • Verify tool integrability • Choose a tool with wide support and documentation © QATestLab. All rights reserved.

  11. 11 Why automation may fail • Incompetent team of automation engineers • Implementation without proper planning • Too late start of test automation • Prejudice that manual testing is cheaper • Unstable environment and frequent changes © QATestLab. All rights reserved.

  12. 12 Test automation will ensure high ROI, accelerate software delivery and improve software quality only if it is applied to the proper project. © QATestLab. All rights reserved.

  13. 13 Contacts E-mail: contact@qa-testlab.com Twitter:QATestLab Phone: +380 (44) 501-55-48 Web-site: qatestlab.com Address: 154a, Borschagivska str., 03056, Kiev, Ukraine SkypeID: sales.qatestlab © QATestLab. All rights reserved.

  14. 14 Thanks © QATestLab. All rights reserved.

More Related