Scribd
Upload
7 views21 pages

Software Development Testing Lifecycle Guide

This document provides an overview of software testing processes and types. It discusses the software development life cycle and various testing types like white box, black box, and grey box testing. It also describes different testing techniques like unit testing, integration testing, functional testing, non-functional testing, and others. The document then outlines the typical testing process including test initiation, test planning, test design, test implementation, test execution, and result analysis and reporting. Formats for use cases and test cases are also presented along with test case writing techniques.

Uploaded by

PrateekMandi
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
7 views21 pages

Software Development Testing Lifecycle Guide

This document provides an overview of software testing processes and types. It discusses the software development life cycle and various testing types like white box, black box, and grey box testing. It also describes different testing techniques like unit testing, integration testing, functional testing, non-functional testing, and others. The document then outlines the typical testing process including test initiation, test planning, test design, test implementation, test execution, and result analysis and reporting. Formats for use cases and test cases are also presented along with test case writing techniques.

Uploaded by

PrateekMandi
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

PROJECT & PRODUCT

Software Development Life


Cycle
Requirement Gathering

Project Planning
Project Design
Coding
Testing
Release and Maintenance

Types of Testing
1. White Box Testing
2. Grey Box Testing
3. Black box Testing

White Box Testing (Unit


Testing)

Code Coverage
Path Coverage
Condition Coverage
Loop Coverage
Mutation Coverage

Grey Box Testing (Integration


Testing)

Top down approach


Bottom up approach
Big bang approach
Sand witch Approach

Black box Testing

Functional Testing
Non Functional Testing

Functional Testing

GUI Testing
Usability Testing
Functionality Testing

Non Functional testing

Load Testing
Stress Testing
Crash Testing
Soak Testing
Recovery Testing
Volume Testing

Other types of Testing

Performance Testing
Smoke Testing
End to End Testing
Retesting
Regression Testing
Ad hoc Testing

Other types of Testing

Compatibility Testing
Cross browser testing
Exhaustive testing
Parallel Testing
Security Testing

Testing process

Test Initiation
Test Plan
Test Design
Test Implementation
Test Execution
Analysis of Result & Reporting

Testing Initiation

The first phase of the testing process


is test initiation. In this phase, the
tester will be getting training in the
domain, project, testing tools tools,
software configuration management
tools etc., This phase is also called
as knowledge transferring phase.

Test Plan

Introduction to testing and the project


Objective
Scope of testing
Strategies
Approach
Entry and exit criteria
Suspension and resumption criteria
Deliverable documents
Scheduling
Budget
Matrix
Features to be tested and features not be tested

Test Design
Use Case
Use case scenario is a stepwise procedure on
how a user intends to use a system, with
different
user
roles
and
associated
parameters.
Test case
Test case is a collection of set of input data
to validate any software or application. It is
a document to compare the requirement and
the execution result.

Use Case Format


Use Case Name
Use Case ID
Actor
Objective
Precondition
Post condition
Step

Alternate Course
Exceptions

User Action

System Response

Relevant Data

Test case Format


Document Reference No: Functionality 001
Project Name

: Asset Management System

Module Name

: Surplus

Released by
Date of release

: AMS Batch
: 01/04/2007

Remarks
Sl No

Test
Case ID

Scenario Descripti
on

Test
Data

Expecte
d Result

Status
Pass/
Fail

Remarks

Test case writing techniques

BVA (Boundary Value Analysis)


ECP (Equivalence Class Partition)
EG (Error Guessing)

Test Implementation

Setting up of an environment to
execute tests

Test Execution

Executing the test cases after getting


the exe file or the build and
comparing with the requirement is
known as test execution. If we find
any deviation from the requirement,
we will send it to the developer for
rectification.

Analysis of results and reporting

After executing the test cases, we


will analyze the result and report to
the assigned person. The developer
will pre look to it. If he feels that he
has done a mistake, he will rectify
and send back to testing engineer or
he will reject the bug.

Thank You

You might also like