Question

my company is small with only one full time tester, and mostly we’re doing web apps. so i’m glad that we have tester as i think i would probably be bias or lazy when debugging my own code…

and our tester is actually located in another country, so usually we communicate via IM or email only. usually i try to do as much white box testing as possible but sometimes due to tight schedule i need to handle a few stuff at the same time and that’s where i get rather lazy on post-testing… 🙁

currently what we usually do is to provide some documents with what the features should be like and hopefully they will have enough information to break whatever that is not working properly.

and sometimes i also include information or test cases on some of testing that i’ve done, and include also some test based on the potential faulty code logic that i would want her test explicitly.

whatever she finds she will log into our bugzilla and i will proceed to check it, fix it and get her to verify it again.

so my question do you have any good tips or better way so that we can aid our tester better in finding more bugs?

thanks

Answer 1

Sounds like you are already doing two important things:

1. Do you best to find your own defects. (Although doesn’t sound like you are working with any automated unit tests, which could help in this area)
2. Valuing the feedback that you get from testing.

Two additional things I would recommend.

1. You both need to get a clear definition of what needs to be done.
2. Provide completed functionality on a regular basis.

This is a bit of a balance between:

A. Provide Release Notes with a clear description of what was done

B. Regularly release with incremental functionality introduced.