testing

Delivering quality software is at the heart of Practiv’s vision.  We take testing seriously, and our testing process and results are entirely transparent to our clients.  This ensures that our clients know the status and quality of the service being provided by Practiv at any given time.

We work to ensure quality is built in to the entire development cycle this can not only save time and money, but helps ensure that clients are satisfied with what is delivered to them.  Practiv have followed this approach for many years, and our testing methodologies have matured as a result.

This enables Practiv to make informed decisions as to the type and detail of testing required in a given situation, and what best suits the services being delivered.  Testing comes in many forms ranging from static testing to automated functional testing, and stress & performance testing.  While it is possible to use all of these forms for each project, this is not the best approach in every situation.  It is here, in the application of different forms of testing to specific projects, where Practiv's maturity adds real value to our customers’ projects.

Test Driven Development (TDD) and continuous build integration allows the quality assurance team to have confidence in what is being developed.  This comes from the fact that every checked-in piece of code and functionality is passed through code quality checks (unit tests) before the test analyst is given the build to start testing.  This not only saves time testing unstable builds, but eliminates a lot of the minor issues found and allows the test analyst to focus on the higher profile areas of the Application Under Test (AUT).

If you would like to talk to us further about our testing services, please feel free to contact us directly.