Quality Control.

Different solutions require different testing strategies

We have an in-house team who lead our testing activities, but when appropriate we also use third party testing services. Our testing protocol follows ISTQB guidelines.

Explore solutions for your industry

Ideate

The earlier the better.

One thing never changes: the earlier the testing activity starts, the better the results. In an agile development environment, early testing which feeds into subsequent sprints saves time and money overall.

Why test? The overall objective is to reduce the risk of malfunction as far as possible, thus increasing our confidence in the software. We can think of this in two ways. Firstly, does the application do what it needs to do? And second, how does it hold up in the face of unexpected events such as a bad connection or an unforeseen user input? While it’s impossible to prove the absence of defects, a well-designed and implemented testing strategy can minimise them, increasing the overall quality of the software.

Evaluate

Collaborate, integrate.

In the testing phase, collaboration goes as far as you want it to. We are always happy to share details of tests carried out; if you prefer we can share our testing logs so that you can add test requests and monitor the results as they evolve. We’ll also support you in designing and carrying out tests involving interaction with your existing systems.