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

1. Automation in testing
How to tackle it
Presenter: Mirek Rakowski
Date: 13/11/2014

3. Goals
Automation in testing

4. Software testing
16-Apr-15 4Source: http://danspira.com/2011/06/

5. • 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

6. • 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

7. • Team work
• Transparent goals
• Well defined test strategy
Overcomming obstacles
16-Apr-15 7

9. Scope
Automation in testing

10. 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

11. What can we automate?
16-Apr-15 11
Manual
tests
GUI tests
Functional / API
tests
Unit tests

12. • 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

13. • Usability tests
• Exploratory tests
• Tests that will always pass
• Tests that are executed only once
What shouldn’t be automated
16-Apr-15 13

14. • 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

16. Test strategy
Automation in testing

17. Test strategy
16-Apr-15 17Source: http://4.bp.blogspot.com/_S3TFiuLoYtg/S_PdfSptbZI/AAAAAAAAAMk/nRrI4LB-3dc/s1600/Where%20to%20start.jpg

18. • 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

19. Automation in testing
16-Apr-15 19Source: http://sd.keepcalm-o-matic.co.uk/i/keep-calm-and-automate--20.png

20. Q / A

21. Thank you!