A tweak to the unit testing methodology

Just a quick update on a change of methodology from my earlier post.

We have decided to scrap the control team. It was deemed too expensive in terms of man hours as we are only trialling the concept.

So my team is now the “unit testing” team. Any regression defects that arise from this development stage are to be tracked back to individual pieces of work. This will hopefully show how many defects can be attributed to a piece of code with a unit test as opposed to code without. As a proper unit test should catch the majority of defects before system testing we will also be counting the number of defects our team tester finds from our code.

We will meticulously record the time spent on development and on writing unit tests, hopefully giving us some idea of the time overhead that comes with writing a test.