Testing and Test Driven Development Phase Test Preperation

Getting a Clearer Picture Getting to a stage where we understand the problem more clearly Event tables Use case diagrams / descriptions An early prototype of the proposed system  

Visual Studio Configuration Project bank web facing front end Project bank locally hosted back end The class library A database file linked to both presentation layers

Two More Things A class diagram Test plans

The Class Diagram

The Test Plan Test Type Test Data Expected Result Actual Result Extreme Min Min -1 Min (Boundary) Min +1 Max -1 Max (Boundary) Max +1 Mid Extreme Max Invalid data type Other tests

Test Driven Development Testing is error prone and boring “Flat Pack” Programming? In TDD Create a test that fails (test plan my not always encourage this) Run the test and see it fail Fix the error in a simplistic way See the test pass Re-factor to implement the feature correctly All about small steps Builds confidence in the system Builds confidence in the programmer Programming Pathways

The Phase Test You may bring with you to the test Your class diagram Your test plan A single A4 page of handwritten notes (This will be inspected prior to the test start) You will create on the day Test framework Class library Test cases for 2 x properties of different data type 2 x parameters of different data type

For Example Properties Parameters in Valid CountyNo Int32 DateAdded DateTime Parameters in Valid PostCode DateAdded

Some Examples We will now work through some examples to get you atarted