Continuous integration and good testing practices while coding

Transcription

1 Continuous integration and good testing practices while coding Presentation for TTY course Ohjelmistojen testaus Tuomas Lunti 1 12/10/2016 Nokia 2016

2 Nokia Networks business in Finland 2 12/10/2016 Nokia 2016

3 Networks business in Finland Head office in Espoo; other offices in Oulu and in Tampere One of the main R&D locations for Networks Full range of operations including manufacturing of base station products in Oulu Key customers: Nationwide operators Elisa and TeliaSonera; Finnish Railway Administration (GSM-R) 3 12/10/2016 Nokia 2016

4 Employees 6000 employees Over 10% of total Nokia employees 3700 R&D employees Approximately 400 manufacturing employees Employees by location: Espoo Oulu Tampere /10/2016 Nokia 2016

5 Locations Espoo Head office functions End-to-end Mobile Solution Center Oulu Radio Research & Design Center Base Station manufacturing Tampere End-to-end Network Operability Center 5 12/10/2016 Nokia 2016

6 Tampere SoC Development, Operations Support Systems and Customer Experience Center Highlights End to end Operability, User Experience and Process Automation Operations Support Systems GSM Base Station Controller and WCDMA Radio Network Controller SW maintenance services Real-time data processing for CEM via Traffica Shared Reference Network lab and Global OSS Lab Technology Expertise System integration competences for OSS and end-to-end operability Customer experience management, Traffica, Service assurance GSM / WCDMA Controller Specification, SW and I&V System Modules, System on Chip development Ecosystem Local universities providing access to latest technologies which utilized via coop projects and thesis workers for our R&D projects Lots of user experience and process automation expertise in local companies. Coop projects with TUT, UTA, TAKK and TAMK Close, regular and trustful relationship with Tampere City officials and mayor to discuss the future plans mutually. Visible e.g. via Tampere spirit Training where public funding available 6 12/10/2016 Nokia 2016

7 Continuous integration 7 12/10/2016 Nokia 2016

8 General Architecture in NetAct 3 RD party tool Global products (e.g. Advanced Configurator, ison Manager) 3 RD party tool NetANctetAct Alarms Configurations Measurements GSM (regional) LTE Other vendors NEs MVI WCDMA CORE 8 9/11/2016 Nokia 2016

9 Continuous integration Continuous integration (CI) is a practise where all developers merge their working branches to main branch at the end of the day. This ensures integration problems are found faster and no large integration problems can arise. 9 9/11/2016 Nokia 2016

10 Code creation and testing before commit Create/refactor code Development team + architect(s) iterative process Create unit testing Test code by locally building or debugging in IDE Review code with team member 10 9/11/2016 Nokia 2016

11 Front end Build server Unit testing Junits first level of regression testing Building the software Running static analysis tools to check code quality. Review code in review tools. Gerrit: Free build server tools Build server: Static analysis tool: /11/2016 Nokia 2016

12 About unit testing and static analysis Unit testing Unit tests are most important test cases Unit tests gives fast feedback to developers normally in seconds Unit tests can be executed already in local environment Unit tests are stable if done in correct way Unit tests should test unit ie classes. Static analysis Keeps the code in good shape Sometimes finds potential problems like null pointer issues 12 9/11/2016 Nokia 2016

13 Automated Integration testing Integration testing pipe is constructed on many blocks to help locating problems easier and faster. Examples of test automation frameworks: /11/2016 Nokia 2016

14 Testing practices while coding 14 12/10/2016 Nokia 2016

15 About bugs Every programmer creates bugs when coding. But testing can catch the bugs before those go to customer. Some reasons for bugs: The code has some software bug The code is not working as specified Customer environment is different than thought The code is used in different context than tough The code is used with different input than tough Someone else has modified the code and broken some implementation The installation of the software has not worked 16 9/11/2016 Nokia 2016

16 Before and after commit Make the units. Read requirements one time more. Go trough them with team mate if needed. Make units to cover those. Review the code with team mate if needed. Review the code with static analysis tool. Test the code by deploying it to target environment. Test manually the use cases that those work. Ready to commit Follow the continuous integration pipes that those work Implement black box testes if needed 16 12/10/2015 Nokia 2014

17 Test driven development 16 9/11/2016 Nokia 2016

18 Make code which easy to understand Don t make spaghetti code. Write code so its easily to understand. Use good names for functions and classes. Break the code into small-enough classes and functions that everyone can easily understand what they do. Remember to use single responsibility principle. Don t use two fancy things which are hard to understand for team members. 15 9/11/2016 Nokia 2016

19 Summary and Q&A Summary and Q&A 18 9/11/2016 Nokia 2016

20 19 12/10/2016 Nokia 2016