Requirement based testing - Testing Techniques - Software Testing and Quality Assurance

TL;DR

Requirement based testing is a technique that involves validating explicit and implicit requirements specified in the software requirements specification (SRS) document.

Transcript

hello friends second chapter testing techniques we have already seen what is black box testing now we look at the testing technique the first thing is requirement based testing now requirement based testing deals with validating the requirements that means in the srs the requirements are specified so legal or the important requirements are being pr... Read More

Key Insights

• ⚾ Requirement based testing focuses on validating explicit and implicit requirements specified in the software requirements specification (SRS) document.
• 📜 Explicit requirements are stated and documented in the SRS, while implicit requirements are assumed and not explicitly mentioned.
• 🏆 Test requirement specification is created by collecting explicit requirements from the SRS and additional requirements from the test team.
• 🏆 Requirement traceability matrix helps in mapping test cases to specific requirements.
• 🏆 Test condition lists different ways of testing a requirement.
• 🏆 Requirement flexibility matrix includes test condition, test case ID, and type of testing to be used.
• 🏆 Multiple test cases can be created for one requirement, or multiple requirements can be covered by one test case.

Questions & Answers

Q: What is the purpose of requirement based testing?

The purpose of requirement based testing is to validate the explicit and implicit requirements stated in the SRS document. It ensures that the software meets all the specified requirements.

Q: What is the difference between explicit and implicit requirements?

Explicit requirements are clearly stated and documented in the SRS, while implicit requirements are assumed and not explicitly mentioned. They are often derived based on industry standards or common practices.

Q: How are explicit requirements used in requirement based testing?

Explicit requirements from the SRS are collected and documented in the test requirement specification. They serve as the basis for creating test cases and evaluating whether the software fulfills the specified requirements.

Q: How are implicit requirements handled in requirement based testing?

Implicit requirements are also considered during requirement based testing. Although not explicitly stated, they are assumed to be necessary for the software to meet the needs of the customer. These implicit requirements can be derived through industry knowledge or discussions with stakeholders.

Summary & Key Takeaways

• Requirement based testing involves validating the requirements stated in the SRS document, which includes explicit and implicit requirements.

• Explicit requirements are stated and documented in the SRS, while implicit requirements are assumed without any formal communication.

• Test requirement specification is created by collecting explicit requirements from the SRS and additional requirements from the test team.