Test-Driven Development. As it should be.

Transkriptio

1 Test-Driven Development. As it should be. Jarno Keskikangas Project Manager Digia Plc SYSOPENDIGIA Plc

2 Outline Me, You and the Company Agile software development in general and TDD in particular Test-Driven Development in a nutshell Lessons learnt & summary Q & A SYSOPENDIGIA Plc

3 Me, You and the Company SYSOPENDIGIA Plc

4 Me Agile advocate practitioner rather than researcher focus on the bottom line Introducing and implementing TDD practices to own organization and other entities Currently working as a scrum master and project manager...with software developer background SYSOPENDIGIA Plc

5 You Familiar with agile principles Comfortable with xunit frameworks Have heard or tried TDD Will have the time of your life during the presentation In a way or other =) SYSOPENDIGIA Plc

6 ...and the Company, Outline Digia Plc Modern and agile software house Complete solution offering Business critical ICT solutions Forerunner in mobile and wireless solutions Focused market segments Telecommunications Industry and Trade Finance and Services Listed on the Nordic Exchange Headquarters in Helsinki, offices in Estonia, Sweden and other locations in Finland Pro forma turnover in 2006 EUR 98.9 million Employs over 1100 professionals SYSOPENDIGIA Plc

7 Telecommunications Division Agile partner creating mobile software development services and solutions Trusted player providing business process improvement, integration and systems development Innovative forerunner building ICT solutions utilising mobile opportunities Employing over 550 professionals Handset Industry Integrating Innovations Operators & Media Corporations SYSOPENDIGIA Plc

8 Agile software development in general and TDD in particular SYSOPENDIGIA Plc

9 Agile Software Development Iterative and incremental development Close collaboration between business people and programmers Empowered and selforganized teams Working software as the primary measure of progress Risk Cost of change Agile project Waterfall project Time Time SYSOPENDIGIA Plc

10 Test-Driven Development. As it should be.

11 Test Driven Development Add a test Specification [Pass] Run the tests [Fail] Design Make a little change Development [Fail] Run the tests [Pass, Development continues] Testing [Pass, Development stops] SYSOPENDIGIA Plc

12 How to write good TDD specifications? What s the next most important thing the system doesn t do? Template for TDD scenarios Given some initial context (the givens) When an event occurs Then ensure some outcomes SYSOPENDIGIA Plc

13 Emerging design and mock objects Test class Domain object Test class Mock object Domain object Mock object SYSOPENDIGIA Plc

14 To see is to believe

15 EUnit Test Creation Wizards /* This file has been generated with EUnit Pro */ #ifndef CMYTRIANGLE_TESTI_H #define CMYTRIANGLE_TESTI_H // INCLUDES #include <CEUnitTestSuiteClass.h< CEUnitTestSuiteClass.h> #include <EUnitDecorators.h< EUnitDecorators.h> #include "CMyTriangle.h" CMyTriangle.h" // FORWARD DECLARATIONS // CLASS DEFINITION /** * Generated EUnit test suite class. */ NONSHARABLE_CLASS( CMyTriangle_Testi ) : public CEUnitTestSuiteClass { public: // Constructors and destructor static CMyTriangle_Testi* NewL(); static CMyTriangle_Testi* NewLC(); ~CMyTriangle_Testi(); private: // Constructors CMyTriangle_Testi(); void ConstructL(); private: // New methods void SetupL(); void Teardown(); void T_Global_AreaL(); void T_Global_CMyTriangleL(); void T_Global_CenterL(); void T_Global_CrossProductL(); void T_Global_FirstCornerL();

16 EUnit Test Execution EUnit S60 Gui EUnitExeRunner Connectivity Carbide.C++ EUnit View Device Test Manager RPM server and device pool

17 Lessons learnt

18 Developer questionnaire 1. Facilitates better requirements 2. Reduces debugging effort 3. Reduces development time 4. Yields higher code quality 5. Promotes simpler design 6. Is noticeably effective 7. Getting into TDD mindset 8. Lack of upfront design is a hindrance Question Mean Standard Deviation SYSOPENDIGIA Plc

19 Testimonials 3. Jos voit valita vapaasti, käytätkö mieluummin TDD-tekniikkaa vai jotain muuta lähestymistapaa? Miksi? Ehdottomasti TDD. Mikäli unit testejä tehdään jollain muulla keinolla ne eivät yleensä osu ongelman ytimeen vaan harrastetaan koodikattavuuden generointia esim. Tarkistelemalla raja-arvoja. Mielellään TDD:tä, koska silloin automaattisesti päädytään testattavaan ja yleensä toimivaan designiin. Koodin laatu pysyy koko kehitystyön ajan hyvänä. 2. Kuvaile kohtaamiasi ongelmia TDD-tekniikan soveltamisessa. Miten ongelmia voisi mielestäsi vähentää? Suurimmat ongelmat syntyvät vanhojen partojen pinttyneistä tavoista suunnitella kaikki etukäteen eli ei anneta TDD:n tehdä sitä mihin se on tarkoitettu. Huono design: konkreettiset riippuvuudet, sykliset riippuvuudet, luokilla monta vastuuta. Luokat pitäisi suunnitella niin, että ne voidaan yksikkötestata SYSOPENDIGIA Plc

20 Summary

21 TDD is not about testing. It s about specification, design and testing.

22 TDD is essential element of agile software engineering.

23 Agile software engineering is harder to adopt than agile project management.

24 Pay now or pay later. The later you pay, the higher the K.

25 Testimonials Thank You! SYSOPENDIGIA Plc

26 References Scott Ambler: Introduction to Test Driven Design Dan North: Introducing BDD Boby Georgea, Laurie Williams: A structured experiment of test-driven development Dozens of research papers, see ACM and IEEE electronic libraries SYSOPENDIGIA Plc