Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

TDD for Testers

381 Aufrufe

Veröffentlicht am

A presentation given to Quality Assurance Testers, about Test Driven Development/Design. What it is, where the tests fit in the pipeline and what it means to developers and testers.

Veröffentlicht in: Software
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

TDD for Testers

  1. 1. For Testers Sarah & Dewald Usher Viljoen
  2. 2. ’ ? Input Process Actual Output Expected Output 2
  3. 3. 2 3 Write Test Refactor Write code 3
  4. 4. 2 3 Write Test Refactor Write code 4
  5. 5. Write Test Refactor See test fail See test pass 2 3 Write code 5
  6. 6. 6
  7. 7. 7
  8. 8. 58 API External API External APIPrivate int CreditRatingAlgorithm ( double AmountOwned, double PaymentHistoryScore, double CreditHistoryScore){ return (AmountOwed + PaymentHistoryScore + CreditHistoryScore) / 3 * 100 } 8
  9. 9. 58 API External API External APIPrivate int CreditRatingAlgorithm ( double AmountOwned, double PaymentHistoryScore, double CreditHistoryScore){ return (AmountOwed + PaymentHistoryScore + CreditHistoryScore) / 3 * 100 } U I I I I 9
  10. 10. 58 API External API External API Private int CreditRatingAlgorithm … U I I I I Acceptance Test - Scenario 10
  11. 11. Source Control Production Build Unit Tests Integration Tests Acceptance Tests Check out and Build Run Tests 11
  12. 12. SC PB U I A Passes Tests - 12
  13. 13. Test-Driven- / Design Interface designs are 13
  14. 14. ’ ? - Write the test code with a specific intent - Write the production code 14
  15. 15. 15
  16. 16. ’ - Help decide on the intent - Think edge cases which could affect the design - Pairing with the developer - Understand what the program is trying to do - Spot any cases missed by the developer - Understand how a design change may affect tests 16
  17. 17. - Test, Code, Refactor - Testing is the QA and Dev collaboration point. - QAs can help design better intentions, spot flaws and edge cases that have been missed. - QAs can better understand how design changes can affect tests down the (pipe)line. TDD is a DESIGN tool. Is does not replace the testing work that is required in a project. 17
  18. 18. 18
  19. 19. *http://programmers.stackexchange.com/quest ions/258311/if-we-have-tdd-and-bdd-why-do- we-need-qa-for http://agiledata.org/essays/tdd.html http://www.ministryoftesting.com/2014/08/tdd- testers/ http://blog.drorhelper.com/2010/05/why-tdd-is- good-for-testers.html 19
  20. 20. Code sample. 20

×