Talking myself into the value of acceptance testing 

@mokagio (click to see these slides in the browser) 

Before we begin... 

Acceptance Test != Unit Test 

DO. WRITE. UNIT. TESTS. 

Acceptance Test != Automated Test 

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 

⌘U, Xcode Bots, Travis CI, Jenkins, etc, can be used to run unit tests automatically 

Automated Acceptance Tests = Acceptance tests run automatically 

This talk is about (automated) acceptance tests 

Content Problems When they are valuable Who they are valuable for How to get started 

Problems 

Long to write 

Slow to run 

Expensive to maintain 

Still need QA 

Apple doesn't care 

When they are valuable 

"State-intense" & "many-branches" apps 

Refactoring legacy spaghetti code 

The client with the JIRA board and the acceptance criterias 

Who they are valuable for 

big-medium teams with clear requirements and relaxed deadlines 

small/one man teams with green product and need for fast pace 

Just try it out and see how it goes 

How to get started 

UIAutomation 

Apple UI Testing 

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 ( ) } 

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 ) } 

KIF 

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 ] ; } ) ; } ) ; } ) ; 

Calabash and Appium 

Were do I begin? 

Add an acceptance test for the most important feature 

Add an acceptance test for every new bug fix 

"A bug is only a test that hasn't been written yet" - I don't know who said this 

Where to go from here Xcode 7 UI testing - WWDC KIF on GitHub mokacoding.com > Acceptance Testing Generative Testing 

And remember... 

DO. WRITE. UNIT. TESTS. 

Thanks 

❓ Questions?