Download to read offline
Uploaded byAnnyce Davis
Develop Maintainable Apps - edUiConf
The document outlines best practices for developing maintainable applications, emphasizing the importance of code quality, proper library selection, and unit testing. Key methodologies such as MV* patterns, clean code principles, and tools like Checkstyle and Mockito are highlighted for improving code readability and ensuring thorough testing. Additionally, resources for further learning on effective software development are provided.
More Related Content
![The Hitchhiker's Guide to Servo Contributor [COSCUP 2020]](https://cdn.slidesharecdn.com/ss_thumbnails/thehitchhikersguidetoservocontributor-coscup2020-200801073819-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Develop Maintainable Apps - edUiConf
Develop Maintainable Apps - edUiConf
- 1.
- 2. What’s our job? A.Make apps B. Make apps that work C. Make great apps! @brwngrldev
- 3. What’s our job? Makegreat apps! @brwngrldev
- 4.
- 5.
- 6.
- 7. What to consider AmazingApp ! Documentation Project Stability Fulfills a Need @brwngrldev
- 8.
- 9. So you needimages… Volley ! Fresco ! Glide ! Picasso !
- 10.
- 13.
- 15. Documentations W Project Stability pFulfills a need Volley !
- 16.
- 17.
- 18. Review… • Documentation • RepositoryCheck-ins • Fulfills a Need Libraries 1 @brwngrldev
- 19.
- 20.
- 21.
- 22. Clean It Up! How tofix this MVP MVVM OO
- 23.
- 24.
- 25.
- 26.
- 28.
- 29.
- 30. Reference the Interface publicvoid onEvent (ErrorEvent event) { mainView.showVideoUnavailableMessage(); }
- 31. Implement the Interface @Override publicvoid showVideoUnavailableMessage () { Toast.makeText( this, getString(R.string.video_unavailable), Toast.LENGTH_LONG ) .show(); }
- 32.
- 33. Review… • Keep CodeSimple • Use MV* Pattern • Functional Tests • Use the Tools @brwngrldev Domain Design 2
- 34.
- 35.
- 36. Increase Readability? “Checkstyle isa development tool to help programmers write Java code that adheres to a coding standard.”
- 37.
- 38. apply plugin: ‘checkstyle’ taskcheckstyle(type: Checkstyle) { description 'Checks if the code passes quality standards' group 'verification' configFile file(‘checkstyle.xml') … }
- 39. <module name=“MethodLength"> <property name="max"value=“60"/> </module> <module name=“LineLength"> <property name="max" value=“120"/> </module> <module name=“CyclomaticComplexity"> <property name="max" value=“8"/> </module> … playerControlConfig.setShowClosedCaptionsButton(a.getBo
- 40. <module name=“CyclomaticComplexity"> <property name="max"value=“8"/> </module>
- 41.
- 42. public void overlyComplexMethod(Videovideo) { if (video != null && video.getStreamUrl() != null) { switch (video.getCategory()) { case "CAT1" : playVideo(video); if (video.getLargeImageUrl() == null) { video.setLargeImageUrl("http://www.largeImage.png"); } updateMetadata(video); break; case "CAT2" : if (video.getLargeImageUrl() == null) { video.setLargeImageUrl("http://www.smallImage.png");
- 43. … warning: CyclomaticComplexity is 9
- 44. public void overlyComplexMethod(Videovideo) { if (video != null && video.getStreamUrl() != null) { updateVideoBasedOnCategory(video); } } private void updateVideoBasedOnCategory(Video video) { switch (video.getCategory()) { case "CAT1" : playVideo(video); if (video.getLargeImageUrl() == null) { video.setLargeImageUrl("http://www.largeImage.png"); } updateMetadata(video); break; 7
- 45. switch (video.getCategory()) { case"CAT1" : playVideo(video); updateMetaDataAndUrl(video, "http://www.largeImage.png"); break; … 4 @brwngrldev
- 46. Review… • Readability Matters •Use Checkstyle • Refactor Gradually @brwngrldev Code Quality 3
- 47.
- 48.
- 49. “Every single lineof code that you write should be tested. Period.” — Robert Martin
- 51. 0 9,000 18,000 27,000 36,000 Lines of Code ProductionTests 90% 2,200 90s FitNesse
- 53. JUnit • Framework forwriting repeatable tests • Assertions for testing expected results • Features for sharing common test data • Test suites for organizing tests
- 54. Mockito • Enables mockcreation and verification • Mock concrete classes and interfaces • Simple annotation support
- 55.
- 56.
- 57. Test Setup @Mock MainView mainView; @Before publicvoid setUp () { } @brwngrldev
- 58. Test Setup @Mock MainView mainView; @Before publicvoid setUp () { initMocks( this ); mainPresenter = new MainPresenter(); mainPresenter.setMainView( mainView ); } @brwngrldev
- 59. Sample Test @brwngrldev @Test public voidconfigurationLoaded_shouldHideSplashScreen () { ConfigurationLoadedEvent event = new ConfigurationLoadedEvent(); mainPresenter.onEvent( event ); }
- 60. Sample Test @brwngrldev @Test public voidconfigurationLoaded_shouldHideSplashScreen () { ConfigurationLoadedEvent event = new ConfigurationLoadedEvent(); mainPresenter.onEvent( event ); verify( mainView ).hideSplashScreen(); }
- 61.
- 62.
- 63.
- 64.
- 65. Review • Listen toRobert Martin! • JUnit + Mockito • Continuous Integration • Code Coverage Testing 4 @brwngrldev
- 66. Summary Ensure code quality Choosethe right library Don’t do too much Write unit tests @brwngrldev
- 67.
- 68. Resources • Clean Code- http://amzn.to/1DJybxH • Effective Java - http://amzn.to/1Ku8Xel • Working Effectively with Legacy Code - http://amzn.to/1Jqe1PA • Unit Testing Idioms - http://goo.gl/Bx1WbL • Google Code Style - http://goo.gl/8Pf6J3 • Architecting Android - http://goo.gl/UKvmbq • Conquering Cyclomatic Complexity - http://goo.gl/lRoPXN @brwngrldev
- 69. Photo Credits • Slide5 - https://www.flickr.com/photos/tshirbert/118250140 • Slide 19 - http://uncompromisedmen.com/2015/02/17/top-10-crazy-beards- wish-youd-seen-person/ • Slide 34 - https://www.flickr.com/photos/cast_fish/2888442781 • Slide 48 - https://www.flickr.com/photos/desertbusforhope/8207412726/ • Slide 50 - https://www.flickr.com/photos/sokabs/2668975758 • Slide 64 - https://www.flickr.com/photos/pasukaru76/5268559005 @brwngrldev