„Testing can only ever prove the presence of faults, never their absence.“
(Edsger Wybe Dijkstra)

Why does hsp have a testing department?

Developing software is a demanding and complex task. Developers often have to implement difficult functions, coordinate their work perfectly, and frequently have to extend programme code written by someone else.

Our developers work intensively on their code. Sometimes, therefore, we need someone who can take a step back and look at the bigger picture. This is where our testing department comes in. The testers have nothing to do with the programming itself and can therefore offer a neutral, critical perspective.

What is assessed in the HSP test?

No software or update is released by hsp without first being tested. The focus of testing always aligns with the focus of development work – currently Opti.Tax.

How is HSP tested?

However, the testing department is not solely responsible for quality assurance. At hsp, every department pays close attention to quality at every stage of development.

Developers check their work, for example, using unit tests and a code review, during which at least one other developer examines the programme code.

The testing department distinguishes between manual and automated testing. New functions are initially tested manually. On the one hand, as many variants of the function as possible are tested. On the other hand, the functionality is also examined in the broader context of the rest of the programme.

One tried-and-tested method of manual testing is known as exploratory testing. This involves not only considering the intended user flow, but also examining what happens when users deviate from it.

Once a function has been developed to the point where virtually no further changes are made, testing can also be automated. The reason is quite simple: it can always happen that a change made in one place has unexpected consequences in a completely different part of the code. To rule out such cases, we use what are known as regression tests, which are run every night on two machines.

Who carries out the testing at hsp?

The testing department currently has two full-time staff members. They are either certified to the recognised ISTQB standard or have received appropriate training.

Our work-study student assists the department with the tests. During the busy run-up to a release, colleagues from the support department also help with the manual tests.

Why do we enjoy testing?

An anonymous tester once said: ‘Software testers always go to heaven; they’ve already had their fair share of hell.’.

And yet, testing software is simply a hell of a lot of fun. At hsp in particular, the combination of manual and automated testing makes the tester’s job very varied. When one of our testers tracks down a bug, it immediately creates a sort of thrill of the hunt.

But perhaps it’s also because a good test can help several groups at once: the developers, because it gives them the assurance that their application works; the users, because they get a product that works well; and the management, because they can sell the product with a clear conscience.

And last but not least: it’s simply a pleasure to work with colleagues from other departments. Everyone sees themselves as part of a team that works together to ensure our customers have access to the best software solutions.

And what if an error does occur at the customer’s end after all?

Even in the case of hsp, Lubarsky’s law of cybernetic entomology applies: „There’s always one more bug.“