Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Automation in testing
How to tackle it
Presenter: Mirek Rakowski
Date: 13/11/2014
Goals
Automation in testing
Software testing
16-Apr-15 4Source: http://danspira.com/2011/06/
• Manual testing takes too much time
• Manual testing is error prone
• Release of key resources
• Regression testing as a ...
• Developers’ approach
• Hump of pain
• Initial costs
• Constantly changed code
• Legacy software
• Fear
• Bad habbits
• W...
• Team work
• Transparent goals
• Well defined test strategy
Overcomming obstacles
16-Apr-15 7
Scope
Automation in testing
What can we automate?
16-Apr-15 10Source: http://coding-is-like-cooking.info/wp-content/uploads/2013/07/agile-testing-quad...
What can we automate?
16-Apr-15 11
Manual
tests
GUI tests
Functional / API
tests
Unit tests
• Code analysis
• Builds and deployment, Continous Integration
• Unit and component tests
• API / Web services tests
• Bus...
• Usability tests
• Exploratory tests
• Tests that will always pass
• Tests that are executed only once
What shouldn’t be ...
• Code that was not designed to be tested automatically
• Software that doesn’t have clear separation between layers
• Tes...
Test strategy
Automation in testing
Test strategy
16-Apr-15 17Source: http://4.bp.blogspot.com/_S3TFiuLoYtg/S_PdfSptbZI/AAAAAAAAAMk/nRrI4LB-3dc/s1600/Where%20...
• Aim where it hurt most
• Multilayer approach
• Properly designed tests structure and maintenance
• Correct tools selecti...
Automation in testing
16-Apr-15 19Source: http://sd.keepcalm-o-matic.co.uk/i/keep-calm-and-automate--20.png
Q / A
Thank you!
Mirosław Rakowski - Automation in testing – how to tackle it
Mirosław Rakowski - Automation in testing – how to tackle it
Mirosław Rakowski - Automation in testing – how to tackle it
Upcoming SlideShare
Loading in …5
×

Mirosław Rakowski - Automation in testing – how to tackle it

309 views

Published on

II meeting of Trójmiejska Grupa Testerska - testers community in tri-city area, Poland.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Mirosław Rakowski - Automation in testing – how to tackle it

  1. 1. Automation in testing How to tackle it Presenter: Mirek Rakowski Date: 13/11/2014
  2. 2. Goals Automation in testing
  3. 3. Software testing 16-Apr-15 4Source: http://danspira.com/2011/06/
  4. 4. • Manual testing takes too much time • Manual testing is error prone • Release of key resources • Regression testing as a ‘safety net’ • Test automation as a source of feedback • Test driven develpoment • Automated tests as a live documentation • Automation – good return of investment Why to automate? 16-Apr-15 5Source: http://media.gamerevolution.com/images/misc/Image/cat-nap-on-comp.jpg
  5. 5. • Developers’ approach • Hump of pain • Initial costs • Constantly changed code • Legacy software • Fear • Bad habbits • Wrong assumptions Impediments for test automation 16-Apr-15 6Source: http://librairie.immateriel.fr/baw/9780596159818/httpatomoreillycomsourceoreillyimages329397.png
  6. 6. • Team work • Transparent goals • Well defined test strategy Overcomming obstacles 16-Apr-15 7
  7. 7. Scope Automation in testing
  8. 8. What can we automate? 16-Apr-15 10Source: http://coding-is-like-cooking.info/wp-content/uploads/2013/07/agile-testing-quadrants.009.jpg Unit Tests Component Tests Functional Tests Examples Story Tests Prototypes Simulations Exploratory Testing Usability Tests UAT Alpha / Beta Performance Tests Security Testing „ility” Testing Automated Automated & Manual Manual Tools
  9. 9. What can we automate? 16-Apr-15 11 Manual tests GUI tests Functional / API tests Unit tests
  10. 10. • Code analysis • Builds and deployment, Continous Integration • Unit and component tests • API / Web services tests • Business layer tests • Presentation layer tests • Load, performance, stress tests • Results comparison • Repetable activities • Data / configuration setup What can be automated? 16-Apr-15 12Source: http://blog.typemock.com/wp-content/uploads/2012/04/crash-test-dummies.jpg
  11. 11. • Usability tests • Exploratory tests • Tests that will always pass • Tests that are executed only once What shouldn’t be automated 16-Apr-15 13
  12. 12. • Code that was not designed to be tested automatically • Software that doesn’t have clear separation between layers • Tests when requirements constantly changes What can be hard to automate? 16-Apr-15 14
  13. 13. Test strategy Automation in testing
  14. 14. Test strategy 16-Apr-15 17Source: http://4.bp.blogspot.com/_S3TFiuLoYtg/S_PdfSptbZI/AAAAAAAAAMk/nRrI4LB-3dc/s1600/Where%20to%20start.jpg
  15. 15. • Aim where it hurt most • Multilayer approach • Properly designed tests structure and maintenance • Correct tools selection • Do it agile Test strategy 16-Apr-15 18
  16. 16. Automation in testing 16-Apr-15 19Source: http://sd.keepcalm-o-matic.co.uk/i/keep-calm-and-automate--20.png
  17. 17. Q / A
  18. 18. Thank you!

×