Acceptance Testing - CMD+U Conf

The secret to fast, r0ck-solid, automated acceptance tests. Presented at CMD+U Conf, Barcelona, 2016. - "HOLA"!

Transcript

1. Acceptance Testing ! The secret to fast, r0ck-solid, automated acceptance tests. @paulstringer
2. Two Kinds Of Tests Verify your code is correct Validate you wrote the right code
4. “Defect Avoidance is more powerful than defect removal” – Levendal (1990)
5. iOS Acceptance Testing Appium Kif Subliminal Zuchinni Calabash Frank UIAutomation Cucumber XCUITest
6. •Doesn’t scale (slow, fragile, complex) •Very hard to exercise all business logic •Very poor defect localisation •Customer doesn’t write or read them •Abandoned, revert to manual testing
8. BDD / ATDD Executable Specifications Automated Tests Living Documentation
9. “Are you doing BDD? Or are you just using Cucumber?” – Aslak Hellesøy
10. Courtesy of Aslak Hellesøy, - cucumber.io
11. Plan, Read, Write, Execute requirements Works across platforms (Mac, iOS, Android) An alternative, first UI to your App Fully integrated standalone wiki and acceptance testing framework
12. Demo
13. FitNesse <Slim Server> Fixtures System Instructions Web Browser UIKit Views View Controllers System Touch Events Human Responses Updates CI FitNesse FitNesse YourAcceptanceTests.App Your.App
14. Clean Architecture Affords the ability to independently validate behaviour separate from annoying implementation details (e.g. Databases, Network or UI)
15. Final Thoughts ATDD/BDD is the practice of customers writing the tests Fully understanding requirements early saves effort later Non UI based testing is fast, reliable and scales Helps improve collaboration and understanding across team and most importantly with the customer. Good choice for long-term, complex software
16. TicTacToe - http:/ /bit.ly/CMDU-TTT ‘OCSlimProject’ - GitHub, CocoaPods Tutorial - http:/ /stringerstheory.net Questions - @paulstringer Discover More… Code and Resources