Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Types of testing  Types of testing   Acceptance testing   Acceptance testing

Lifecycle   »   Agile Testing   »   Unit testing

Your developers will perform unit tests. These are probably the lowest level of tests your project will perform. Your developers may choose to run the tests before they fully write the code. The subject of test driven development is already worthy of a handful of books so we bow to their superior knowledge. Nevertheless, your developers may choose to create test harness programs which validate your system features in a non-visual output manner. They will be testing at the lowest level whether certain manual or automated inputs create or trigger certain anticipated outputs. Often times, all that has changed or created is a single digit in a row in a database.

In the Toolkit, unlike many other agile methodologies, we recognise that often certain key system fundamentals will be in place before we can usefully create assessment deliverables and before we can test it. These fundamentals include low-level database access and other data access components, security and login systems, presentational or front-end interfaces as well as other mandated application architecture components. It might be that our governance procedures dictate it or our development environment mandates it. Either way, in this instance, we need something in place before our project can get underway.

We strongly suggest that, in these instances, you identify what components you need and place them into a subproject that is estimated and time boxed to deliver when you need it. In our experience, it is often much more efficient to separate out these activities. These are often quite technical and detailed processes that do not lend themselves well to business involvement or to the straightforward business validation of their outputs.

So, you have identified the various components that you need such as login screens and database access components. These are going to be delivered in a sub-project prior to the main project and developed using test driven development. Your developers will unit test the various components using test harness programs. If there is still debate about the design of various components and these components will not be ready in time for your project, consider when you need the component precisely. If a shipment can progress without the component, plan it without the component. If a key component is required for your shipment, consider re-planning your shipments. There is no rocket science to this, at all.


 Types of testing     Types of testing   Acceptance testing    Acceptance testing

Glossary:     a  »   b  »   c  »   d  »   e  »   f  »   g  »   h  »   i  »   j  »   k  »   l  »   m  »   n  »   o  »   p  »   q  »   r  »   s  »   t  »   u  »   v  »   w  »   x  »   y  »   z

#personas  »   #artefacts  »   #archetypes  »   #patterns  »   #change  »   #personas  »   #increasingoutput  »   #reducingvariation  »   #improveefficiency  »   #abstraction  »   #predictionandcontrol  »   #management  »   #organisations  »   #socialnetworktheory  »   #failfast  »   #quality  »   #waste  »   #complexity  »   #learning  »   #adapt  »   #inspect  »   #improvement  »   #models  »   #complexadaptivesystems  »   #informationflow  »   #sytemsthinking  »   #butterflyeffect  »   #unpredictability  »   #chaos  »   #emergence  »   #emergentbehaviour  »   #distributedcontrol  »   #continuousimprovement  »   #complexityscience  »   #gametheory  »  
 Agile In 6 Steps    |    Projectivity    |    Instant Agile    |    Risks    |    Auditing Agile Projects 
Big Agile Toolkit Book (Amazon Japan)   |   Big Agile Toolkit Book (Barnes and Noble)
Buy the Big Agile Toolkit Book   |   Buy the Big Agile Toolkit Kindle eBook
Unit testing


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
Topic: 328  Page: 280/444  Progress: 63.1%
 About    |    Author 
Follow @BigAgileToolkit

This content can be copied to third parties for personal use if you acknowledge the source of the material with website URL ( and Twitter hashtag (#BigAgileToolkit).
In all other cases, no part of bigagiletoolkit or associated text or website may be copied reproduced or redistributed in any form or by any means without prior permission in writing from the author.
Agile Project Governance for Cost Conscious Companies™

All rights reserved.