Scribd
Upload
57 views18 pages

Software Quality Assurance: Testing Throughout The Software Life Cycle

Testing should occur throughout the software development lifecycle, no matter which model is used. For each development activity, a corresponding test activity is needed. Testers should be involved early to help define requirements and design. There are different levels of testing - component, integration, system, and acceptance. Each level has specific objectives like reducing risk, finding defects, and validating functionality. Early and frequent testing helps prevent defects from impacting later stages of development.

Uploaded by

avishma kriyanji
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
57 views18 pages

Software Quality Assurance: Testing Throughout The Software Life Cycle

Testing should occur throughout the software development lifecycle, no matter which model is used. For each development activity, a corresponding test activity is needed. Testers should be involved early to help define requirements and design. There are different levels of testing - component, integration, system, and acceptance. Each level has specific objectives like reducing risk, finding defects, and validating functionality. Early and frequent testing helps prevent defects from impacting later stages of development.

Uploaded by

avishma kriyanji
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/ 18

Software Quality Assurance

Testing throughout the


software life cycle

Pavithra Subashini
Senior lecturer
Faculty of Computing
Testing throughout the software life cycle

• A software development lifecycle model describes


the types of activity performed at each stage in a
software development project, and how the
activities relate to one another.
• There are a number of different software
development lifecycle models, each of which
requires different approaches to testing.
Testing throughout the software life cycle

Any software development lifecycle model, there are several


characteristics of good testing:

• For every development activity, there is a corresponding test activity.


• Each test level has test objectives specific to that level.
• Test analysis and design for a given test level begin during the
corresponding development activity.
• Testers participate in discussions to define and refine requirements
and design, and are involved in reviewing work products (e.g.,
requirements, design, user stories, etc.) as soon as drafts are
available.
No matter which software development lifecycle
model is chosen, test activities should start in
the early stages of the lifecycle, adhering to the
testing principle of early testing.
Software Development
methodology –

Cover in Tutorial session


Test level

Acceptane testing • Focuses on the behavior and capabilities of a whole


system or product

• Often considering the end-to-end tasks the system


System testing can perform and the non-functional behaviors it
exhibits while performing those tasks

Integration testing • Focuses on interactions between components or


systems

Component testing • Focuses on components


Component testing
1. Objectives of component testing

• Reducing risk

• Verifying whether the functional and non-functional behaviors of the component


are as designed and specified

• Building confidence in the component’s quality

• Finding defects in the component

• Preventing defects from escaping to higher test levels


Component testing
1. Typical defects and failures

Incorrect functionality (e.g., not as described in design


specifications)

Data flow problems

Incorrect code and logic


Integration testing
1. Objectives of component testing

• Reducing risk

• Verifying whether the functional and non-functional behaviors of the interfaces


are as designed and specified

• Building confidence in the interfaces’ quality

• Finding defects (which may be in the interfaces themselves or within the


components or systems)

• Preventing defects from escaping to higher test levels


System testing
1. Objectives of component testing

• Reducing risk

• Verifying whether the functional and non-functional behaviors of the system


are as designed and specified
• Validating that the system is complete and will work as expected

• Building confidence in the quality of the system as a whole

• Finding defects

• Preventing defects from escaping to higher test levels or production


Acceptance Testing
1. Objectives of testing (UAT, OAT)

• Establishing confidence in the quality of the system as a


whole

• Validating that the system is complete and will work as expected

• Verifying that functional and non-functional behaviors of the system are as


specified
Acceptance
1. Typical defects and failures
testing
System workflows do not meet business or user requirements

Business rules are not implemented


correctly

System does not satisfy contractual or regulatory requirements

Non-functional failures such as security vulnerabilities, inadequate


performance efficiency under high loads, or improper operation on a
supported platform
Testing Types
Tutorial

Develop PowerPoint( with voice) explaining below SDLC:

• Waterfall
• V model
• RAD
• Agile

Upload to nLearn assignment folder.

You might also like