Software Testing

Most IT projects acknowledge that testing is part of the development lifecycle. In practice, testing is often squeezed into whatever time can be negotiated on a project that is already late. There is pressure on the Test Manager to do as good a job as possible, but not to rock the boat too much either!

Our process gives the Test Manager everything they need to prove that the system works correctly:

  • a clear description of how the business expect to use the system
  • a clear specification of how the system is intended to work
  • a clear specification of the data in the system
  • a clear specification of the system interfaces
  • a clear picture of which areas of the system contain the most critical functionality
  • a clear picture of which areas of the system present the greatest technical challenge (performance, volume, etc.)

All of these are available before coding begins in earnest, allowing testing to be planned in advance. Test scripting can take place alongside coding. An important characteristic of good software design is that defects can be traced and fixed quickly. Our approach provides an opportunity to review the design before the code is written so that its suitability for testing can be established. Good coding practices and architecture encourage the use of automated testing tools.

Good quality assurance at each step in the process ensures that defect rates are low enough to be manageable and testing cycles do not get mired down in the demands of re-testing.

You can find out more here:

Our Approach - About Us

Contact Us

If you are interested in talking to us about application development, and how your organisation could do it better, please your details and we will do our best to help