Testing in absence of input documentation
Recently I worked on a project, where lack of documentation necessary to plan the testing activity was an issue. Although this is not a very common scenario, the possibility can't be ruled out completely. So how should the test team proceed when there ain't any input documentation such as design specifications, feature specification et al? It sounds like a tricky situation, isn't it? Well, it is a somewhat tricky situation to deal with, but then there are tools/methods which would come to your rescue. Let's see which are these tools and how to make best use of them... Using product simulator: Although simulators are miniature versions of the fully functional product, they certainly give us a look and feel of the end product. By using the simulator, we can define functional workflows and get some feel about the product's UI. These things then can be used to write test plans and test cases. However one thing is very important to note here, it's a simulator w