The Path to Better Debugging on iOS

Recommendations

Info

“ ...after debugging I knew where the defect was, but after squeezing I had a minimal unit test for the defect as well. That concise test is a handy by-product of the process. — Kent Beck Regression Testing & <strong>The</strong> Saff Squeeze http://www.threeriversinstitute.org/HitEmHighHitEmLow.html ”
GHUnit • SenTestKit has, his<strong>to</strong>rically, been a path <strong>to</strong> madness! • Tests run as separate target • GUI & CLI runner • Selectively run & re-run tests • Setting a breakpoint doesn’t require a PHD • Supports asynchronous tests, runnable in parallel • UI change verification via image diffs https://github.com/gabriel/gh-unit
Page 1 and 2: The Path</
Page 3 and 4: “ Debugging is t
Page 6: Beyond Rubber Ducking NSLog(@"Made
Page 9 and 10: So, Specialised Tools! 1. Interacti
Page 18: Logging without NSLog();
Page 24: Disabling a function - (void)doSome
Page 29 and 30: Shared breakpoints are sto<
Page 31 and 32: Command Abbrev. LLDB Equivalent con
Page 33: 2. Testing
Page 37 and 38: 3. Logging
Page 41 and 42: 4. Network Condition Simulation
Page 43 and 44: 5. Network Traffic Debuggin
Page 45 and 46: Capturing Traffic Via middleware, y
Page 53: 6. Core Animation Debugging
Page 56 and 57: https://github.com/domesticcatsoftw
Page 58: Thank you! Nathan de Vries http://t

The Path to Better Debugging on iOS

Create successful ePaper yourself

Delete template?

Save as template?