by James Spencer, Senior Test

Consultant with Testhouse 

& Adrian Hammon, Visual  Studio 

Consultant for Testhouse


The best place to start testing is not when the code is finished but when it's being written, and in some cases before the coding has even started.  We've put together 10 things you need to think about when planning your testing to drastically improve the quality of your code – and so the perception of the quality of work you put out.

  1. What is the purpose of the tests? Might be purely function, performance (speed, space, etc.), accuracy.
  2. What are the risks of inadequate testing?
  3. Can I bring any of my testing in earlier?  (This is probably the single most effective money saver in any software program)
  4. Have all the requirements been covered in the software and the tests?
  5. Is the software, or this piece of it, ready for testing?
  6. Can I save money on the software development effort by making the software easier to test?
  7. How do I know that any new functionality I’m introducing fits the customers’ requirements?
  8. What sort of performance do I need from this system and how do I measure it?
  9. How am I checking for technical areas that the software testers can’t touch such as memory leaks and the locking of shared resources?
  10. Have past bugs clustered around certain areas and how does testing help this?

Let us know your tips and guidance in the comments. Thanks!

Find out how Testhouse worked with Emirates NBD bank to deploy Team Foundation Server, which the bank now uses for all application life cycle tasks, including source code control, defect management, testing and reporting.