Feeling lucky for using TestersDesk

After spending aroung 8 years hands on experience on software product testing for small as well as large enterprise applications I've observed that even after rigorous testing by QA the field guys and the customers find many critical issues. And this happens even if testers have a good knowledge about the requirements. There had been a sign off too between QA and Develpoment on test plan. Every test case was covered that were there in the test plan. So where is the problem? Here are few of the root causes for product functionality failure at the customer site.

1. Scenarios not covered by QA
2. Data Specific
3. Combinations of inputs/components/configurations not covered by QA
4. Missing permutations of test steps (orders) not covered by QA

To counter issue #1 the only way out is to have a better understanding of the application requirements and usage from a real customer's point of view. But for issues #2, #3 and #4 it is all about creating all possible data and test all possible combinations and permutations scenarios. And definitely to do it manually is a Himalayan task. Even your boss won't ask for it! But he'll not leave you once an issues surfaces at the customer site.

I have always faced problem for issues #2, #3 and #4 in my project work. To my luck I came across TestersDesk.com from a professioanl friend and really it made my and my team's work much simpler. Definitely there are few improvements TestersDesk.com should do, espeacially supporting linux based application testing, generate all types of files. But definitely I assume TestersDesk is already considering all these aspects. Neverthless TestersDesk.com is the only online platform that every tester strive for.

I encourage testers to exploit the tools provided at http://www.testersdesk.com/. Naturally like any great successful product by constant using the platform will be able to incorporate many more feedbacks and features.

Cheers!
--Susil