Comments on: 10 golden rules for Requirements Based Testing

By: Jaideepkhanduja

Jaideepkhanduja — Fri, 07 Jan 2011 10:34:47 +0000

Thanks Moses

By: MosesRozario

MosesRozario — Fri, 07 Jan 2011 10:25:52 +0000

Very informative article. Thanks a ton!!!

By: Jaideep

Jaideep — Tue, 03 Mar 2009 11:50:52 +0000

Thanks Prashanti, Very true the requirements analysis is the bulkiest cause of software projects delays or failures. Just for system sake the requirements are taken or documented and project teams start working on those requirements. The whole system goes haywired if the requirements are not validated right in the start.
I found the link, “testerdesk” quite interesting. I would definitely push my testers to hook on to it for the help in testing.
And for sure the tool(s) based testing has always an edge over the manual testing but point of caution is if the tool is used wisely with full understanding of what I intend it to deliver it to me.

By: Prashanti

Prashanti — Tue, 03 Mar 2009 09:53:28 +0000

Very good analysis of how the requirements and the related testing go in tandem.Validation of the requirements is an often neglected aspect and the companies pay the price later on.
The methodical way in which the requirements and testing are related in this post makes me bring to your notice the test design and test data tools available at [A href="http://www.testersdesk.com"]
The design tool box has the pairwise, n way,t way, subset combinations and boundary interactions generator which can be of great help in testing the requirements. For test data there is a different tool kit altogether.
These tools as a whole can be used in testing to ensure high quality requirements

Prashanti
Product Consultant

ValueMinds – Makers of [A href="http://www.testersdesk.com"]www.TestersDesk.com [/A]– The Online Tool Platform for Software Test Design and Test Data Generation.