What are the Pros and cons of requirements-based software testing? - 1 views

• 
  #2 QA ThoughtLeaders on 22 Nov 12

   

  "Pros:
  It is an organized and focussed way of testing.
  It makes sure that everything is as per what has been documented in the requirement documents ie the Product confirms to what it is expected to perform.
  It makes sure that all the basic flows of the application are covered. Cons:
  Requirements are many a times not properly defined which leads to unclear tests.
  In cases of requirements changes it wastes a lot of time and efforts to keep changing the tests.
  It only confimrs that the system has been designed correctly.
  It does not confirm in a concrete way that the output is also correct."

   

  <div class="cArrow"> </div><div class="cContentInner">"Pros: <br /> It is an organized and focussed way of testing. <br /> It makes sure that everything is as per what has been documented in the requirement documents ie the Product confirms to what it is expected to perform. <br /> It makes sure that all the basic flows of the application are covered. Cons: <br /> Requirements are many a times not properly defined which leads to unclear tests. <br /> In cases of requirements changes it wastes a lot of time and efforts to keep changing the tests. <br /> It only confimrs that the system has been designed correctly. <br /> It does not confirm in a concrete way that the output is also correct."</div>

  ...

  Cancel
• 
  #3 QA ThoughtLeaders on 22 Nov 12

   

  All software's are developed on the basis of some requirements and thus they are important while testing as well. Without requirements, what exactly do developers develop and testers would test? They would be working on assumptions, especially the testers. Without complete requirements, simply exercising on the code may reveal problems. Thus requirement based testing helps the tester to verify and validate the application. As without requirements a tester would be able to distinguish between feature and bug. There are few disadvantages of requirement based testing as well. If the requirements are not clearly defined or are misunderstood while testing, then this may result into missing some major issues.

   

  <div class="cArrow"> </div><div class="cContentInner">All software's are developed on the basis of some requirements and thus they are important while testing as well. Without requirements, what exactly do developers develop and testers would test? They would be working on assumptions, especially the testers. Without complete requirements, simply exercising on the code may reveal problems. Thus requirement based testing helps the tester to verify and validate the application. As without requirements a tester would be able to distinguish between feature and bug. There are few disadvantages of requirement based testing as well. If the requirements are not clearly defined or are misunderstood while testing, then this may result into missing some major issues.</div>

  ...

  Cancel
• 
  #4 QA ThoughtLeaders on 22 Nov 12

   

  "Pros:- Tester are aware with the requirements which helps them to identify and plan the areas which they can target. Testers can cover more type of testing as they are aware with the requirements.
  
  Cons:- When testers are focused on requirements the chances of exploring all areas decreases which might cause problems. Poor requirement-based documents can create bigger problems and the probability of risk increases. "

   

  <div class="cArrow"> </div><div class="cContentInner">"Pros:- Tester are aware with the requirements which helps them to identify and plan the areas which they can target. Testers can cover more type of testing as they are aware with the requirements. <br /> <br /> Cons:- When testers are focused on requirements the chances of exploring all areas decreases which might cause problems. Poor requirement-based documents can create bigger problems and the probability of risk increases. "</div>

  ...

  Cancel

To Top