Why does testing take so long?

Why does testing take so long? It is a re-occuring question of managment and other people of many projects.

The development team has in many cases too litle time, they have 23 new features to build and there is only room for 6 in the SCRUM sprint... so... what can you do?
Business wants things done 'yesterday', so everything is fast, fast, rush, rush.

Next to that, the team desires a way of pragmatic working which is not exactly in line with what is best to do for an optimal test process. It's like the development team likes to drive a car without seatbelts, and the testers advice to drive with a seatbelt because it's safer. "But we like driving without a seatbelt more, because we are used to doing that and it is much faster".

Not only that, because we have only room for 6 features, why should we listen to what the testers would like?

Well what the developers sometimes don't seem to see, is that what the testers would like (as a feature, or as a change) is exactly that, that helps the testers with the progression of the testing. (immensly) That is the reason why they want the change. But because developers have the tools to look at the things differently, they don't seem the see it the same way. There's much misunderstanding.

What causes that the test process takes even longer....

So, what is the solution here?
Try to understand that, even you do have only room for 6 features to build in a certain time. At least some of the time should be allocated to meet the desires and wishes of the software testing team.
Book/allocate some time for helping the test team progress faster. Even if it means building some features that where not on the list of 23 new things to build.....

---