Talking myself into the value of acceptance testing

I've spent some time working on acceptance testing recently, but I'm not always sure if there is actually value in this practice. In this talk we'll explore the tradeoffs of acceptance testing, and see how to get started writing acceptance tests for iOS.

Transcript

1. Talking myself into the value of acceptance testing
2. @mokagio (click to see these slides in the browser)
3. Before we begin...
4. Acceptance Test != Unit Test
5. DO. WRITE. UNIT. TESTS.
6. Acceptance Test != Automated Test
7. Having the intern make sure that when logging in with Facebook the profile picture is the set correctly is a test for an acceptance criteria
8. ⌘U, Xcode Bots, Travis CI, Jenkins, etc, can be used to run unit tests automatically
9. Automated Acceptance Tests = Acceptance tests run automatically
10. This talk is about (automated) acceptance tests
11. Content Problems When they are valuable Who they are valuable for How to get started
12. Problems
13. Long to write
14. Slow to run
15. Expensive to maintain
16. Still need QA
17. Apple doesn't care
18. When they are valuable
19. "State-intense" & "many-branches" apps
20. Refactoring legacy spaghetti code
21. The client with the JIRA board and the acceptance criterias
22. Who they are valuable for
23. big-medium teams with clear requirements and relaxed deadlines
24. small/one man teams with green product and need for fast pace
25. Just try it out and see how it goes
26. How to get started
27. UIAutomation
28. Apple UI Testing
29. Apple UI Testing / * * * W h e n I t a p t h e " s a y h e l l o " b u t t o n , I s e e a g r e e t i n g s a l e r t . * / t e s t S a y H e l l o ( ) { l e t a p p = X C U I A p p l i c a t i o n ( ) a p p . b u t t o n s [ " s a y h e l l o " ] . t a p ( ) a p p . a l e r t s [ " H e l l o " ] . c o l l e c t i o n V i e w s . b u t t o n s [ " D i s m i s s " ] . t a p ( ) }
30. Apple UI Testing / * * * W h e n I t a p t h e " s h o w e l e m e n t e s " b u t t o n , I s e e t h e l i s t w i t h * t h e e l e m e n t s o f t h e p e r i o d i c t a b l e . * / t e s t S h o w E l e m e n t s ( ) { l e t a p p = X C U I A p p l i c a t i o n ( ) a p p . b u t t o n s [ " s h o w e l e m e n t s " ] . t a p ( ) X C T A s s e r t E q u a l ( a p p . t a b l e s . c o u n t , 1 ) l e t t a b l e = a p p . t a b l e s . e l e m e n t A t I n d e x ( 0 ) l e t p e r i o d i c T a b l e E l e m e n t s C o u n t : U I n t = 1 1 8 X C T A s s e r t E q u a l ( t a b l e . c e l l s . c o u n t , p e r i o d i c T a b l e E l e m e n t s C o u n t ) }
31. KIF
32. KIF d e s c r i b e ( @ " M a i n s c r e e n " , ^ { c o n t e x t ( @ " w h e n I t a p t h e ' s a y h e l l o ' b u t t o n " , ^ { b e f o r e ( ^ { [ t e s t e r t a p V i e w W i t h A c c e s s i b i l i t y L a b e l : k S a y H e l l o ] ; } ) ; i t ( @ " I s e e a g r e e t i n g s a l e r t " , ^ { [ t e s t e r w a i t F o r V i e w W i t h A c c e s s i b i l i t y L a b e l : k H e l l o A l e r t T i t l e ] ; [ t e s t e r w a i t F o r V i e w W i t h A c c e s s i b i l i t y L a b e l : k H e l l o A l e r t M e s s a g e ] ; [ t e s t e r w a i t F o r V i e w W i t h A c c e s s i b i l i t y L a b e l : k H e l l o A l e r t B u t t o n ] ; } ) ; } ) ; } ) ;
33. Calabash and Appium
34. Were do I begin?
35. Add an acceptance test for the most important feature
36. Add an acceptance test for every new bug fix
37. "A bug is only a test that hasn't been written yet" - I don't know who said this
38. Where to go from here Xcode 7 UI testing - WWDC KIF on GitHub mokacoding.com > Acceptance Testing Generative Testing
39. And remember...
40. DO. WRITE. UNIT. TESTS.
41. Thanks
42. ❓ Questions?