Showing posts with label software testing tutorial. Show all posts
Showing posts with label software testing tutorial. Show all posts

Thursday, 18 July 2013

Requirements Traceability And Test Cases

What is Requirements Traceability ?
Functional or software requirement specification  is the document which describes stakeholder's requirements which should be traced with deliverables produced during the software development life cycle.

What are the objectives of Requirements Traceeability ?
The objectives of requirement traceability, in general, are to
  • Ensure that the deliverables meet the requirement specification.
  • Ensure that no requirements are missed and therefore  that all are delivered.
  • Identify which deliverables implement which requirements.
  • Identify any deliverables that cannot be tracked back to a requirement. This may be either due to undocumented requirements or to the unnecessary introduction of features that are not actually required by the stakeholders.
Requirements Traceability and Test cases:
Every requirement should be traced to the individual test cases. This is required to ensure that all the requirements have been covered in the test cases and also to identify what tests are necessary to verify a particular requirement has been implemented successfully.

How to write a test case from use case

Use Case to Test Case Conversion:
Let us see the process for generating test cases from a fully detailed use case. The first step is to for each use case, generate a full set of high level test scenarios. For each high level scenario, identify at least one positive or negative test case and the conditions that will make it "execute". Then for each test case, identify the data values with which to test. At last document the test case as a combination of stepps and expected results including the above identified data values.

Tester should consider following concepts under preparation of test case:
  • Ensure each section in use case has one or many test cases.
  • Ensure integrity between modules are maintained throughout the test cases.
  • Need to ensure inter dependencies external to the system are taken care in test cases.

What is Test Case? Why Do We Need

What is a Test case?
IEEE Standard 610 (1990) defines a test case as follows:
A set of inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement."

A test is not only designed to reveal a defect but also to learn something from the defect.

Why Do We a Test Case?
  • Test cases identify and communicate the conditions that will be implement in test.
  • Necessary to very successful and acceptable implementation of the product requirements.
  • Help finding the problems in the requirements or design of an application.
  • To determine whether we meet the client expectations.
  • Help managers make ship / no-ship decisions.
What would happen if there is no Test Case?
If there is no test case then we cannot test effectively and so poor quality  of the deliverables to the client. Other thing is no requirements coverage tracking and take more time for execution.