Testing is well understood to be a crucial factor in the overall quality of a system being built. Since it is often seen to take resources away from the implementation of new features it's generally not given the proper support until it’s too late. Little or poorly planned testing represents a risk to your project.

What process do we use for testing?

• we build detailed test plans that comprehensively cover all product scenarios
• we automate the test scenarios in the test plans to eliminate the need for manual steps to test or verify functionality
• we build and maintain infrastructure that enables us to rapidly run, analyze and report on the status of these automated tests

Test plans

Test plans are the first step, and happen as early as possible in the product cycle. A separate test plan will be written by a tester for each feature or feature area of the product. We can help you comprehensively detail all of the scenarios needed to test a given feature.

Test automation

After testers finalize their test plans, they will start writing and automating the tests defined within them. Free technologies such as NUnit/JUnit can be used to provide a testing framework. Working with your team we can implement test cases & shared test libraries. The test cases are usually straightforward and not too code heavy. The bulk of the work goes into the test libraries that are shared across test scenarios and test cases.

Running tests

So what do you do once you have your tests? The answer of course is to run them regularly on your product. We can help you carefully organise the runs to ensure they cover the various scenarios required for a release. (i.e. different operating systems, under load etc.)