The Sanctity of Testing and why we need it as developers

The Sanctity of Testing and why we need it as developers – by Kevin Bolam

The Sanctity of Testing and why we need it as developers – by Kevin Bolam

Recently I have realised something disturbing. On projects, time for testing is seemingly the first to be compromised should development over run. It seems all too easy for developers and managers a like to cut time in test during a delayed project or in more extreme cases fore going a test team all together, which is very worrying, and that is coming from a developer. There is a common misconception it seems that dev teams and test teams don’t like each other. When in fact it is more likely that this relationship is more symbiotic, dev needs test to point out mistakes, weather it is missed functionality or just broken functionality and test ultimately need dev without us developers test would have no work.

I know you, dear reader and you the boss looking over the shoulder, possibly think I am waffling on a bit but I think it is important to remind people that the relationship is symbiotic.

When it comes to basic functionality, yes, we as developers can test this ourselves, and I’d assume most of us do regularly during the development process. We may even have a JENKINS server set up which will pull from the repository and run a set of scripts. Most of these scripts will push a few values through a function and test the output to make sure that it is what we would expect. We may even, have scripts that test the limits of the functions to make sure that the expected errors are returned. This is Unit Testing 101. We may even while developing or before a commit run through the new piece of functionality from the front end, to make sure the User gets the correct responses to their input. Developers do this all the time, we do it without knowing it in some cases.

Now is this enough testing of new or modified functionality? Can you trust a developer (Even if it is not the person who wrote the code) isn’t ‘fudging it’ to get these outcomes so they can go back to development? This is something people could argue about for hours (I’ve been in that meeting), in my opinion the answer is always No! Developer testing is inherently flawed in my opinion a Developer knows the ‘paths’ of the code and they are likely to be very gentle with the system. The same can be said for developer created unit tests. While they will do as expected and test the unit, they will do this gently also. This is why developers need the aid of a Testing Team, a Testing team does not care for your carefully constructed switch statement that you forgot to add a default to, they don’t care that it is obvious to add a numerical value to a quantity. They will find the flaws in your code and will report it.

The Sanctity of Testing and why we need it as developers

Developers not only need a Test Team we should rely on it for important feedback of the system before it gets in front of a client or user. A Test Team can provide valuable feedback on the usability of the system. This is something developers do not always think about, like how many clicks it takes to navigate to an area within the system.

This is not the only time a developer needs a tester, the other important time is during support. If there is no test team this stage is needlessly a time waste for developers, who cannot rely on the support of a test team who will attempt to recreate any issue or bug raised. If a developer were to do this they would need to be taken off Development of new features or other fixes to try and replicate the reported issue. This would be time consuming and a bad use of resources, when this can be given to a team to replicate and give detailed instruction for the developer to help narrow down the issue.

Ok so Yes! This has been a bit ‘waffling’ but it needs to be said. Weather it is just to make developers appreciate the valuable assistance that test teams give to our daily lives. It needs to be said as much as you can design the perfect system and build it with the best developers.  but out dedicated tests being ran on the system by a human removed from the process. There is potential for errors that your client will see and an even greater potential for errors to slip past into the wider world. Even with all the testing in the world, I am reminded of what a lecturer once said, ‘You cannot test for human stupidity’.

If you are serious about attracting new candidates, why not book in for a free 10-minute client attraction call with us today? Please click here to make an appointment.

© Ronald James Ltd. 09824756. Q16 Business Exchange, Quorum Business Park, Newcastle upon Tyne, Tyne and Wear, NE12 8BX, United Kingdom. Website by Outlines Design.