Scribd
Upload
9 views8 pages

Unit 3

The document outlines the objectives and factors involved in test design for software testing, including analyzing project requirements, identifying stakeholders, and defining test scope. It emphasizes the importance of testable requirements, which must be precise and verifiable, and describes how they can be articulated in terms of system state, conditions, and expected results. Additionally, it lists various factors that influence test design such as regulatory standards, customer requirements, and tester expertise.

Uploaded by

gowsalyaam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
9 views8 pages

Unit 3

The document outlines the objectives and factors involved in test design for software testing, including analyzing project requirements, identifying stakeholders, and defining test scope. It emphasizes the importance of testable requirements, which must be precise and verifiable, and describes how they can be articulated in terms of system state, conditions, and expected results. Additionally, it lists various factors that influence test design such as regulatory standards, customer requirements, and tester expertise.

Uploaded by

gowsalyaam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

UNIT 3

Test design objective


Test objectives are the specific goals and outcomes
that you want to achieve and measure in your
software testing process.
1. Analyze project requirements
Analyze the project requirements and understand what the
software is supposed to do, how it will be used, and what are the
functional and non-functional requirements.
2. Identify stakeholders and quality standards
Stakeholders are the people or groups who have an interest or
influence in the software. Quality standards are the guidelines
and criteria that define the expected level of quality and
performance of the software
3. Define test scope and focus
• The test scope determines what features, functions, and
components of the software will be tested, and what will
be excluded
4. Formulate test criteria and metrics
• The test criteria define the conditions and rules that
determine whether the software meets the requirements
and quality standards
5. Specify test outcomes and benefits
• The test outcomes describe the observable and verifiable
changes and improvements that the software testing
process will produce
Test design factors
1. Type of system or software application
2. Regulatory standards
3. Customer’s requirements
4. Level and type of risk
5. Test objectives
6. Tester’s skill and knowledge
7. Time and budget
8. Application development life cycle
9. Previous experience in types of defects tracked
Testable Requirements

• A testable requirement is a requirement that has


been broken down to a level where it is precise,
unambiguous, and not divisible into lower level
requirements.
• These criteria are only met if it is possible to
write a test case that would validate whether the
requirement has or has not been implemented
correctly.
A testable requirement could be described in terms of:

1.The state of the system and the data elements that


are inputs (e.g., customer number, product number)

2.The condition or action associated with the


requirement (e.g., the user enters data, the order is
validated, the check amount is deducted)

3.The expected or specified result described in


terms of data elements (e.g., customer number must be 8
digit numeric, product quantity must be greater than zero).
MODELING A TEST DESIGN PROCESS

You might also like