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

TESTS
HOW TO ensure
THAT
SOFTWARE WORKS ?
TESTING!
Quality ( )
Assurance
Quality ( )
Assurance
CheckQuality ( )
prevent bugs
Assurance
CheckQuality ( )
Costs of neglecting
Costs of neglecting
ruin
customers trust
Costs of neglecting
costly
context switches
ruin
customers trust
Types of tests
WHITE BOX
Types of tests
BLACK BOXWHITE BOX
Types of tests
unit testing
integration testing
BLACK BOXWHITE BOX
Types of tests
unit testing
integration testing
regression testing
acceptance testing
load testing
smoke testing
functional testing
syste...
unit testing
integration testing
regression testing
acceptance testing
load testing
smoke testing
functional testing
syste...
BLACK BOXWHITE BOX
developers
BLACK BOXWHITE BOX
developers
qa
product
clients
BLACK BOXWHITE BOX
There’s no worse or better, right or wrong.
Each one has a different purpose
NUNES, Ciro
MANUAL
VS
AUTOMATED
What Who When Automation
Unit tests Developer Coding Always
Integration tests Developer Coding Always
System tests QA Test...
What Who When Automation
Unit tests Developer Coding Always
Integration tests Developer Coding Always
System tests QA Test...
UNITtests
EVERY
COMPONENT
EXERCISE & DOCUMENT
ISOLATION
single
IN
activity-list
#showDetails
activity-filter
#filterByCampaign
activity-list
#showDetails
INTEGRATIONtests
ENSURES
UNITS
different
THAT
TOGETHER
WORK
activity-filter
#filteredItems
activity-list
#filtered
Activity log
#onFilter
activity-filter
#filteredItems
activity-list
#filtered
What Who When Automation
Unit tests Developer Coding Always
Integration tests Developer Coding Always
System tests QA Test...
E2Etests
TEST
APP
entire
THE
Activity log
activity-filteractivity-list
App
Login
Dashboard Campaigns…
Testing pyramid
http://googletesting.blogspot.de/2015/04/just-say-no-to-more-end-to-end-tests.html
Unit
Integration
E2E
Testing pyramid
http://googletesting.blogspot.de/2015/04/just-say-no-to-more-end-to-end-tests.html
Unit
Integration
E2E
70%
Testing pyramid
http://googletesting.blogspot.de/2015/04/just-say-no-to-more-end-to-end-tests.html
Unit
Integration
E2E
70...
Testing pyramid
http://googletesting.blogspot.de/2015/04/just-say-no-to-more-end-to-end-tests.html
Unit
Integration
E2E
70...
Testing pyramid
http://googletesting.blogspot.de/2015/04/just-say-no-to-more-end-to-end-tests.html
Unit
Integration
E2E
70...
Testing pyramid
http://googletesting.blogspot.de/2015/04/just-say-no-to-more-end-to-end-tests.html
Unit
Integration
E2E
70...
Tools
ACCEPTANCEtests
STORIESUSER
REFLECTS
Story: Returns go to stock
In order to keep track of stock
As a store owner
I want to add items back to stock when they're...
Acceptance tests
acceptance criteria expected result result
Acceptance tests
acceptance criteria expected result result
HAVE WHEELS
BREAK
RUN
transport multiple people
Acceptance tests
acceptance criteria expected result result
HAVE WHEELS
BREAK
RUN
transport multiple people
Acceptance tests
acceptance criteria expected result result
HAVE WHEELS
BREAK
RUN
transport multiple people
Better acceptance criteria for stories
Valuable documentation for the developers
Better acceptance criteria for stories
Valuable documentation for the developers
Better acceptance criteria for stories
Asynchronous QA
Tools
What Who When Automation
Unit tests Developer Coding Always
Integration tests Developer Coding Always
System tests QA Test...
FREQUENCY OF USE
RISK OF HAVING BUGS
high
high
low
low
normal
cold warm
hot
Test case prioritization
Agile flow
Day 1, 2 Day 3, 4 Day 5-8 Day 9 Day 10
Refine scope
Identify UI
elements
Write test scripts Final tests & fixes De...
crossengage/acceptance-tests
Takeaways
Focus on the user
Takeaways
Focus on the user
Choose the right type of test for each situation
Takeaways
Automate whenever possible (and worth it)
Focus on the user
Choose the right type of test for each situation
Takeaways
DANKE

SCHÖN
Automated tests
Automated tests
Automated tests
Upcoming SlideShare
Loading in …5
×

Automated tests

This is a talk about automated tests and quality in the agile software development process.

Talk by Ciro Nunes: twitter.com/cironunesdev
Audio file: http://bit.ly/2c0CteR
Learn more about CrossEngage: www.crossengage.io

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all
  • Be the first to comment

Automated tests

  1. 1. AUTOMATED
 TESTS
  2. 2. HOW TO ensure THAT SOFTWARE WORKS ?
  3. 3. TESTING!
  4. 4. Quality ( )
  5. 5. Assurance Quality ( )
  6. 6. Assurance CheckQuality ( )
  7. 7. prevent bugs Assurance CheckQuality ( )
  8. 8. Costs of neglecting
  9. 9. Costs of neglecting ruin customers trust
  10. 10. Costs of neglecting costly context switches ruin customers trust
  11. 11. Types of tests
  12. 12. WHITE BOX Types of tests
  13. 13. BLACK BOXWHITE BOX Types of tests
  14. 14. unit testing integration testing BLACK BOXWHITE BOX Types of tests
  15. 15. unit testing integration testing regression testing acceptance testing load testing smoke testing functional testing system testing BLACK BOXWHITE BOX Types of tests
  16. 16. unit testing integration testing regression testing acceptance testing load testing smoke testing functional testing system testing BLACK BOXWHITE BOX Types of tests etc.
  17. 17. BLACK BOXWHITE BOX
  18. 18. developers BLACK BOXWHITE BOX
  19. 19. developers qa product clients BLACK BOXWHITE BOX
  20. 20. There’s no worse or better, right or wrong. Each one has a different purpose NUNES, Ciro
  21. 21. MANUAL VS AUTOMATED
  22. 22. What Who When Automation Unit tests Developer Coding Always Integration tests Developer Coding Always System tests QA Test Possible Regression tests Developer/QA Test Possible Acceptance tests QA/Clients Development/ Delivery Possible Smoke tests Product/QA Release Possible Functional (E2E) Developer/QA Anytime Possible
  23. 23. What Who When Automation Unit tests Developer Coding Always Integration tests Developer Coding Always System tests QA Test Possible Regression tests Developer/QA Test Possible Acceptance tests QA/Clients Development/ Delivery Possible Smoke tests Product/QA Release Possible Functional (E2E) Developer/QA Anytime Possible
  24. 24. UNITtests EVERY COMPONENT EXERCISE & DOCUMENT ISOLATION single IN
  25. 25. activity-list #showDetails
  26. 26. activity-filter #filterByCampaign activity-list #showDetails
  27. 27. INTEGRATIONtests ENSURES UNITS different THAT TOGETHER WORK
  28. 28. activity-filter #filteredItems activity-list #filtered
  29. 29. Activity log #onFilter activity-filter #filteredItems activity-list #filtered
  30. 30. What Who When Automation Unit tests Developer Coding Always Integration tests Developer Coding Always System tests QA Test Possible Regression tests Developer/QA Test Possible Acceptance tests Tester/Clients Development/ Delivery Possible Smoke tests Product/QA Release Possible Functional (E2E) Developer/QA Anytime Possible
  31. 31. E2Etests TEST APP entire THE
  32. 32. Activity log activity-filteractivity-list App Login Dashboard Campaigns…
  33. 33. Testing pyramid http://googletesting.blogspot.de/2015/04/just-say-no-to-more-end-to-end-tests.html Unit Integration E2E
  34. 34. Testing pyramid http://googletesting.blogspot.de/2015/04/just-say-no-to-more-end-to-end-tests.html Unit Integration E2E 70%
  35. 35. Testing pyramid http://googletesting.blogspot.de/2015/04/just-say-no-to-more-end-to-end-tests.html Unit Integration E2E 70% 20%
  36. 36. Testing pyramid http://googletesting.blogspot.de/2015/04/just-say-no-to-more-end-to-end-tests.html Unit Integration E2E 70% 20% 10%
  37. 37. Testing pyramid http://googletesting.blogspot.de/2015/04/just-say-no-to-more-end-to-end-tests.html Unit Integration E2E 70% 20% 10% FAST & CHEAP
  38. 38. Testing pyramid http://googletesting.blogspot.de/2015/04/just-say-no-to-more-end-to-end-tests.html Unit Integration E2E 70% 20% 10% FAST & CHEAP SLOW & PRICEY
  39. 39. Tools
  40. 40. ACCEPTANCEtests STORIESUSER REFLECTS
  41. 41. Story: Returns go to stock In order to keep track of stock As a store owner I want to add items back to stock when they're returned. Scenario 1: Refunded items should be returned to stock Given that a customer previously bought a black sweater from me And I have three black sweaters in stock. When he returns the black sweater for a refund Then I should have four black sweaters in stock. Scenario 2: Replaced items should be returned to stock Given that a customer previously bought a blue garment from me And I have two blue garments in stock And three black garments in stock. When he returns the blue garment for a replacement in black Then I should have three blue garments in stock And two black garments in stock.
  42. 42. Acceptance tests acceptance criteria expected result result
  43. 43. Acceptance tests acceptance criteria expected result result HAVE WHEELS BREAK RUN transport multiple people
  44. 44. Acceptance tests acceptance criteria expected result result HAVE WHEELS BREAK RUN transport multiple people
  45. 45. Acceptance tests acceptance criteria expected result result HAVE WHEELS BREAK RUN transport multiple people
  46. 46. Better acceptance criteria for stories
  47. 47. Valuable documentation for the developers Better acceptance criteria for stories
  48. 48. Valuable documentation for the developers Better acceptance criteria for stories Asynchronous QA
  49. 49. Tools
  50. 50. What Who When Automation Unit tests Developer Coding Always Integration tests Developer Coding Always System tests QA Test Possible Regression tests Developer/QA Test Possible Acceptance tests Tester/Clients Development/ Delivery Possible Smoke tests Product/QA Release Possible Functional (E2E) Developer/QA Anytime Possible
  51. 51. FREQUENCY OF USE RISK OF HAVING BUGS high high low low normal cold warm hot Test case prioritization
  52. 52. Agile flow Day 1, 2 Day 3, 4 Day 5-8 Day 9 Day 10 Refine scope Identify UI elements Write test scripts Final tests & fixes Demo Write acceptance tests Test data QA schedule Test data Acceptance tests https://www.scrumalliance.org/system/resource_files/0000/0459/AgileQA.pdf
  53. 53. crossengage/acceptance-tests
  54. 54. Takeaways
  55. 55. Focus on the user Takeaways
  56. 56. Focus on the user Choose the right type of test for each situation Takeaways
  57. 57. Automate whenever possible (and worth it) Focus on the user Choose the right type of test for each situation Takeaways
  58. 58. DANKE
 SCHÖN

×