Commit Code With Confidence

So you wrote some awesome lines of code and you're ready to commit the changes. How do you know if it breaks code you wrote last year or that your teammate wrote yesterday? How confident are you that it will not break anything in your app or in a dependency? Testing is a great way to be confident in your own code and avoid nightmares of your code breaking production.

Testing comes up often in discussions about software engineering, but when, how, and why should it be implemented? Often, the amount of testing depends on the stage of the software application and the development team. How many active users does the app have? How large is the development team? Is the app in international markets with multiple language localizations? With each increasing stage of an app and growth of the development team, automated testing becomes ever more important to ensure a quality product.

This talk will use Lookout's iOS product as an example, but the principles and learnings can be applied to any software stack.

Transcript

1. 03.17.2016 COMMIT CODE WITH CONFIDENCE STEPHANIE SHUPE
2. OUTLINE • #define testing • Why test? • Let’s test! • Takeaways
3. #define testing
4. dictionary.com the means by which the presence, quality, or genuineness of anything is determined; a means of trial. #define testing
5. dictionary.com the means by which the presence, quality, or genuineness of anything is determined; a means of trial. #define testing
6. dictionary.com the means by which the presence, quality, or genuineness of software is determined; a means of trial. #define software testing
7. #define manual testing
8. wikipedia.org the process of manually testing software for defects. #define manual testing
9. wikipedia.org it requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behavior. #define manual testing
10. wikipedia.org it requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behavior. #define manual testing
11. wikipedia.org the tester often follows a written test plan that leads them through a set of important test cases. #define manual testing
12. wikipedia.org the tester often follows a written test plan that leads them through a set of important test cases. #define manual testing
14. #define automated testing
15. wikipedia.org the use of special software to control the execution of tests and the comparison of actual outcomes with predicted outcomes #define automated testing
16. wikipedia.org the use of special software to control the execution of tests and the comparison of actual outcomes with predicted outcomes #define automated testing
17. So... why test?
18. To commit code with confidence!
19. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code
20. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code
21. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code • Doesn’t break a localization
22. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code • Doesn’t break a localization
23. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code • Doesn’t break a localization • Doesn’t break a dependency
24. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code • Doesn’t break a localization • Doesn’t break a dependency iOS Server Android Web 
25. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code • Doesn’t break a localization • Doesn’t break a dependency • Doesn’t add a bug
26. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code • Doesn’t break a localization • Doesn’t break a dependency • Doesn’t add a bug www.slwoods.co.uk
27. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code • Doesn’t break a localization • Doesn’t break a dependency • Doesn’t add a bug • Handles error scenarios
28. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code • Doesn’t break a localization • Doesn’t break a dependency • Doesn’t add a bug • Handles error scenarios WHAT HAPPENS IF MY METHOD IS CALLED WITH THE WRONG PARAMETERS?
29. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code • Doesn’t break a localization • Doesn’t break a dependency • Doesn’t add a bug • Handles error scenarios • Actually works as expected
30. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code • Doesn’t break a localization • Doesn’t break a dependency • Doesn’t add a bug • Handles error scenarios • Actually works as expected SENDS DATA TO CORRECT SERVER 
31. BE CONFIDENT THAT YOUR CODE • Doesn’t break pre-existing code • Doesn’t break a localization • Doesn’t break a dependency • Doesn’t add a bug • Handles error scenarios • Actually works as expected • Will continue to work as expected
32. Then... why doesn’t
    everyone test?
33. There are some
    common excuses.
34.  Testing takes too long - slows down development.
35.  You can save yourself & others time now.
36.  You can save yourself & others time later.
37.  It’s too early to test this product.
38.  Testing later is a bigger tech debt.
39.  Testing as you develop ensures quality early.
40.  I don’t know how to test what I’m working on.
41.  You can learn how to test and teach others.
42.  My team doesn’t test.
43.  You can improve the development process.
44.  You can increase your team’s code stability.
45.  I’m the only developer building this app.
46.  You can break your own code from yesterday.
47. You can break your own code from 2 weeks ago. 
48. You can break your own code from 5 months ago. 
49. You can break your own code from last year. 
50. You can test to ensure your code works. 
51.  LET’S TEST!
52. Automated Testing Types Unit
53. Automated Testing Types Unit test a method
54. Unit Testing describe(@"+isExpired:", ^{ context(@"when date occurred in past", ^{ beforeEach(^{ subject = [NSDate dateWithTimeIntervalSinceNow:-10]; }); it(@"should return expired", ^{ [[theValue([NSDate isExpired:subject]) should] beYes]; }); }); context(@"when date occurs in future", ^{ beforeEach(^{ subject = [NSDate dateWithTimeIntervalSinceNow:1000000]; }); it(@"should return not expired", ^{ [[theValue([NSDate isExpired:subject]) should] beNo]; }); }); });
55. Automated Testing Types Unit Integration
56. Automated Testing Types Unit Integration test dependency integration
57. Integration Testing context(@"when a request is made with malformed data", ^{ it(@"should return an error", ^AsyncBlock { Request *request = [Request new]; ... expect(error).toNot.beNil(); expect(httpResponse.statusCode).to.equal(500); [client enqueueRequest:request]; }); });
58. Automated Testing Types Unit Integration UI Automation
59. Automated Testing Types Unit Integration UI Automation test UI and end to end validation
60. Automated User Interface Testing Run Tests Generate Screen shots Linguistic Verification Quality Assurance
61.  LET’S SEE UI AUTOMATION IN ACTION!
62. 
63. Testing @Lookout • Part of our code review process
64. Testing @Lookout • Part of our code review process • Devs write tests with code changes
65. Testing @Lookout • Part of our code review process • Devs write tests with code changes • Automation engineers write UI automation tests
66. Testing @Lookout • All automated test suites run • before code can be pushed to master • after merge to master
67. Testing iOS @Lookout
68. TAKEAWAYS • Why test • When to test • How to test
69. STAY CONNECTED @steph_shupe @Lookout @womenwhocode / @wwcsf https://www.linkedin.com/in/shupestephanie steph@lookout.com