×
Copy
Open
Link
Embed
Share
Beginning
This slide
Copy link URL
Copy link URL
Copy iframe embed code
Copy iframe embed code
Copy javascript embed code
Copy javascript embed code
Share
Tweet
Share
Tweet
Slide 1
Slide 1 text
Ensuring the Happy Path @kickinbahk Josiah Mory
Slide 2
Slide 2 text
This is Me
Slide 3
Slide 3 text
New Feature
Slide 4
Slide 4 text
Wait…but it worked before!?!
Slide 5
Slide 5 text
Just need to fix this one last bug…
Slide 6
Slide 6 text
No content
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
No content
Slide 9
Slide 9 text
No content
Slide 10
Slide 10 text
Why Test?
Slide 11
Slide 11 text
Rephrased: What are the benefits of testing?
Slide 12
Slide 12 text
Check for Behavior
Slide 13
Slide 13 text
Refactoring Assurance
Slide 14
Slide 14 text
Doesn’t the Compiler Test Enough for us?
Slide 15
Slide 15 text
The Compiler Checks for….
Slide 16
Slide 16 text
Compile-Time Bugs
Slide 17
Slide 17 text
Types (type of objects we place into functions)
Slide 18
Slide 18 text
An object’s adherence to protocols
Slide 19
Slide 19 text
Nil
Slide 20
Slide 20 text
The compiler does not check for….
Slide 21
Slide 21 text
Runtime errors
Slide 22
Slide 22 text
Behavior
Slide 23
Slide 23 text
Testing Takes Too Much Time
Slide 24
Slide 24 text
TDD is SUPER Intense!
Slide 25
Slide 25 text
No content
Slide 26
Slide 26 text
TDD Not Required
Slide 27
Slide 27 text
100% Coverage Not Required
Slide 28
Slide 28 text
Testing doesn’t need to be all or nothing
Slide 29
Slide 29 text
Start off just Testing Main Functionality
Slide 30
Slide 30 text
Many 3rd Party Test Frameworks • Quick/Nimble • Kiwi • Specta • XCFit
Slide 31
Slide 31 text
No content
Slide 32
Slide 32 text
No content
Slide 33
Slide 33 text
“But we don’t want to include (more) third party libraries”
Slide 34
Slide 34 text
Enter XCTest Apple’s test framework built into Xcode
Slide 35
Slide 35 text
No content
Slide 36
Slide 36 text
No content
Slide 37
Slide 37 text
TDD Doesn’t Fit our Business Model
Slide 38
Slide 38 text
Time = Money
Slide 39
Slide 39 text
Testing requires more modular code
Slide 40
Slide 40 text
Less time spent in manual QA
Slide 41
Slide 41 text
Less time Debugging and Fixing Programmer Errors
Slide 42
Slide 42 text
Our users shouldn’t be our QA team
Slide 43
Slide 43 text
Loss of confidence due to reoccurring bugs
Slide 44
Slide 44 text
No content
Slide 45
Slide 45 text
Testing…
Slide 46
Slide 46 text
covers a multitude of mistakes
Slide 47
Slide 47 text
and provides refactoring reassurance
Slide 48
Slide 48 text
Testing doesn’t need to be all or nothing
Slide 49
Slide 49 text
Start off just Testing Main Functionality
Slide 50
Slide 50 text
and continue adding tests as needed
Slide 51
Slide 51 text
Thank you! @kickinbahk Josiah Mory