Validate the requirements

Farhan Sabir's picture
Farhan Sabir asked on November 18, 2016 - 1:38am | Replies (3).

When  a client sends requirements, should a QA person be involved to validate them? If yes then what should be the process?

3 Answers

Justin Rohrman's picture

That question is hard to answer without understanding your working environment -- process and people. In general though, I think it is a very good idea to have testers involved in reviewing requirements. We are often able to ask questions other people don't think of which changes how the product migth be developed.

Arvind Yadav's picture

Yes, QA must be involved in the validating the requirement document becuase that would help the QA team in creating the test plan document. Its always good to involve the QA person from the start of the project. If you talk about the process then you can create a process document for document review that would help the QA team in reviewing the requirement document. Like - A QA person review the requirement document and he/she come across any query or doobts then he/she can discuss the same with client by sending the query register or calls or chat or any other medium of communication. One this process is over then we can feeze that document and start creating the test plan. Also, I would suggest that both development and QA should be involved in all the discussions.

Arvind Yadav's picture

Yes, QA must be involved in validating the requirement document becuase that would help the QA team in creating the test plan document. Its always good to involve the QA person from the start of the project. If you talk about the process then you can create a process document for document review that would help the QA team in reviewing the requirement document. Like - A QA person review the requirement document and he/she come across any query or doobts then he/she can discuss the same with client by sending the query register or calls or chat or any other medium of communication. One this process is over then we can feeze that document and start creating the test plan. Also, I would suggest that both development and QA should be involved in all the discussions.

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.