Continuous integration and deployment on Android

Droidcon Bucharest 2016 slides

Transcript

1. Continuous integration and deployment on Android DINO KOVAČ ANDROID TEAM LEAD @ INFINUM
2. ABOUT INFINUM • independent design and development agency • 90 employees • 15 Android Engineers • hundreds of projects
3. 01 EARLY PROBLEMS
6. TITLE Nunc commodo mi dictum nisi iaculis ullamcorper donec bibendum.
7. 02 CODE QUALITY
8. REGRESSIONS • the worst kind of bugs • some of them are easily detectable!
9. STATIC ANALYSIS TOOLS • lint • checkstyle • findbugs • pmd
10. ANDROID LINT • common android specific issues and best practices • LinearLayout orientation • using method introduced in SDK level > minSdk • missing super calls
11. CHECKSTYLE • helps to keep a consistent code style • highly configurable using config file • works well in combination with AS code style if(url.equals(otherUrl)){
 System.out.print("it's equal!");
 }
 
 if(url.equals(otherUrl))
 System.out.print("it's equal!");
 
 if (url.equals(otherUrl)) {
 System.out.print("it's equal!");
 }
12. PMD, FINDBUGS • warn you about common Java pitfalls • findbugs works on class files • pmd works on source files
13. JAVA.NET.URL
14. JAVA.NET.URL @Test
 public void urlEquals() throws Exception {
 URL url = new URL("https://infinum.co");
 URL otherUrl = new URL("https://www.infinum.co");
 
 Assert.assertEquals(url, otherUrl);
 }
16. JAVA.NET.URL - JAVADOCS • Two hosts are considered equivalent if both host names can be resolved into the same IP addresses; else if either host name can't be resolved, the host names must be equal without regard to case; or both host names equal to null. • Since hosts comparison requires name resolution, this operation is a blocking operation.
17. MATH.ABS • does not always return positive numbers! • integer values range from -2147483648 to 2147483647 Assert.assertTrue(Math.abs(Integer.MIN_VALUE) >= 0);
18. 03 TESTING
19. TESTING APPROACHES • instrumentation tests - robotium / espresso • unit tests - plain JUnit • functional tests - robolectric
20. TESTS • we use a combination of unit tests and functional tests • centered around the clients needs and the specification
21. GREAT LIBRARIES • JUnit 4 • Mockito • OkHttp MockWebServer • Dagger 2 • assertj-android
22. @Test
 public void correctLoginRequest() throws Exception {
 String user = "testUserName";
 String pass = "testPass0&";
 
 enqueueResponse("sdk-login-response.json");
 Sdk.login(user, pass, mock(SdkCallback.class));
 
 RecordedRequest request = takeLastRequest();
 
 assertThat(request.getMethod()).isEqualTo("POST");
 assertThat(request.getPath()).isEqualTo("/login");
 assertThat(request.getHeader(“Accept")) .isEqualTo("application/json");
 assertThat(request.getHeader(“Content-Type")) .isEqualTo("application/x-www-form-urlencoded");
 assertThat(request.getBody().readUtf8()) .isEqualTo("login=" + user + "&password=" + "testPass0%26");
 }
23. @Test
 public void successfulLogoutDeletesTokens() throws Exception {
 stub(mockPlatform().preferenceStore().getAccessToken()) .toReturn("abcdefghijklmnopqrstuvwyxz0123456789");
 
 enqueueEmptyResponse(HttpURLConnection.HTTP_OK);
 Sdk.logout();
 
 verify(mockPlatform().preferenceStore()).clearAccessToken();
 verify(mockPlatform().preferenceStore()).clearRefreshToken();
 }
24. NO DETAILED SPECS? • when you have a detailed spec, tests like these are easy • when you don’t have it → the tests ARE the spec!
25. CONTINUOUS INTEGRATION • each push to the git repo triggers a build on the CI service • CI service checks out the code, runs static analysis and tests • if the build fails, you get notified • if you break the build you fix it!
26. CIRCLE CI • hosted CI service • nice android support • configurable via .yml file • support for saving and displaying build artifacts
27. CIRCLE CI - DOWNSIDES • integrates only with github • no support for x86 emulators • your code is ‘in the cloud’
29. BROKEN BUILDS • clients want their features done yesterday • project managers / product owners don’t care about broken builds • ‘we’ll fix the build after the release’
34. 04 DEPLOYMENT
35. TITLE Nunc commodo mi dictum nisi iaculis ullamcorper donec bibendum.
36. AUTOMATIC DEPLOY FOR CLIENTS • for each push to the labs branch the release build is built • the CI build number is added to versionName: ‘1.0.0-b45’ • the .apk is uploaded to Infinum Labs • the last commit message is used as changelog
38. Thank you! Questions please :) DINO@INFINUM.CO @DINO_BLACKSMITH Visit infinum.co or find us on social networks: infinum.co infinumco infinumco infinum