Learn Software Testing with TechPartnerz 1.ppt

7/28/2019 Learn Software Testing with TechPartnerz 1.ppt

1/20

Learn Software Testing

With TechPartnerz

Session 1

http://www.techpartnerz.com


2/20

Your Partner for Professional Successhttp://www.techpartnerz.com 2013 TechPartnerz

In this presentation..

What is Verification & Validation? Session 1

Verification Strategies.

Validation Strategies.

Establishing a Software Testing Methodology.

Test Phases. Session 2

Metrics.

Configuration Management. Session 3

Test Development.

Defect Tracking Process.

Deliverables.


3/20


What is Verification & Validation?

Verification and Validation are the basic ingredients of

Software Quality Assurance (SQA) activities.

Verification checks whether we are building the rightsystem, and

Validation checks whether we are building the

system right.


4/20


Verification Strategies comprise of the following:

1. Requirements Review.

2. Design Review.3. Code Walkthrough.

4. Code Inspections.

Verification Strategies


5/20


Validation Strategies comprise of the following:

1. Unit Testing.

2. Integration Testing.

3. System Testing.

4. Performance Testing.

5. Alpha Testing.

6. User Acceptance Testing (UAT).

7. Installation Testing.

8. Beta Testing.

Validation Strategies


6/20


Verification Strategiesin detail

VerificationStrategy

Explanation Deliverable

Requirements

Review

The study and discussions of the

computer system requirements to

ensure they meet stated user needs

and are feasible.

Reviewed statement

of requirements.

Design

Review

The study and discussion of the

computer system design to ensure it

will support the system requirements.

System Design

Document, Hardware

Design Document.

Code

Walkthrough

Informal analysis of the program

source code to find defects and verify

coding techniques.

Software ready for

initial testing by the

developer.

Code

Inspection

Formal analysis of the program source

code to find defects as defined by

meeting system design specification.

Software ready for

testing by the testing

team.


7/20Your Partner for Professional Successhttp://www.techpartnerz.com 2013 TechPartnerz

Validation Strategiesin detail

ValidationStrategy


Unit Testing Testing of single program, modules, or

unit of code.

Software unit ready

for testing with other

system component.

Integration

Testing

Testing of related programs, modules, or

units of code.

Portions of the system

ready for testing with

other portions of the

system.

System

Testing

Testing of entire computer system. This

kind of testing can include functional and

structural testing.

Tested computer

system, based on

what was specified to

be developed.

Performance

Testing

Testing of the application for the

performance at stipulated times and

stipulated number of users.

Stable application

performance.



Validation Strategiesin detail

Validation

Strategy


Alpha Testing Testing of the whole computer system

before rolling out to the UAT.

Stable application.

User

Acceptance

Testing (UAT)

Testing of computer system to make

sure it will work in the system regardless

of what the system requirements

indicate.

Tested and accepted

system based on the

user needs.

Installation

Testing

Testing of the Computer System during

the Installation at the user place.

Successfully installed

application.

Beta Testing Testing of the application after the

installation at the client place.

Successfully installed

and running

application.



In order to establish software testing methodology and

developing the framework for developing the testing tactics,

the following eight considerations should be described:

Acquire and study the Test Strategy.

Determine the Type of Development project. Determine the Type of Software System.

Determine the project scope.

Identify the tactical risks.

Determine when testing should occur.

Build the system test plan. Build the unit test plan.

Establishing a Software Testing Methodology.



Type of Development Project

Type Characteristics Test Tactic

Traditional System

Development

Uses a system development

methodology.

User knows requirements.

Development determines

structure.

Test at end of each

task/step/phase.

Verify that specs match need.

Test function and structure.

Iterative

development /Prototyping / CASE

Requirements unknown.

Structure pre-defined.

Verify that CASE tools are used

properly.

Test functionality.

System

Maintenance

Modify structure. Test structure.

Works best with release

methods.

Requires regression testing.

Purchased /

Contracted

Software

Structure unknown.

May contain defects.

Functionality defined in user

documentation.

Documentation may vary from

software.

Verify that functionality matches

need.

Test functionality.

Test fit into environment.



Testing can and should occur throughout the phases of a project.

Requirements Phase

Determine the test strategy.

Determine adequacy of requirements.

Generate functional test conditions.

Design Phase

Determine consistency of design with requirements.

Determine adequacy of design.

Generate structural and functional test conditions.

Program (Build) Phase

Determine consistency with design.

Determine adequacy of implementation.

Generate structural and functional test conditions for

programs/units.

When Testing should occur..?



Test Phase Determine adequacy of the test plan.

Test application system.

Installation Phase

Place tested system into production.

Maintenance Phase

Modify and retest.

When Testing should occur..?



Two types of testing can be taken into consideration.

Functional or Black Box Testing.

Structural or White Box Testing.

Functional testing ensures that the requirements areproperly satisfied by the application system. The

functions are those tasks that the system is designed to

accomplish.

Structural testing ensures sufficient testing of theimplementation of a function.

Types of Testing.



Structural Testing.

Technique Explanation Example

Stress Determine system performance

with expected volumes.

Sufficient disk

space allocated.

Execution System achieves desired level of

proficiency.

Transaction

turnaround time

adequate.

Recovery System can be returned to anoperational status after a failure.

Evaluate adequacyof backup data.



Structural Testing.


Operations System can be executed in a

normal operational status.

Determine systems

can run using

document.

Compliance System is developed in

accordance with standards and

procedures.

Standards follow.

Security System is protected inaccordance with importance to

organization.

Access denied.



Functional Testing.


Requirements System performs as specified. Prove system

requirements.

Regression Verifies that anything

unchanged still performs

correctly.

Unchanged system

segments function.

ErrorHandling Errors can be prevented ordetected and then corrected.Error introducedinto the test.



Functional Testing.


Manual

Support

The people-computer interaction

works.

Manual procedures

developed.

Inter Systems Data is correctly passed from system

to system.

Intersystem parameters

changed.

Control Controls reduce system risk to anacceptable level. File reconciliationprocedures work.

Parallel Old systems and new system are run

and the results compared to detect

unplanned differences.

Old and new system can

reconcile.



End of session 1



About TechPartnerz

TechPartnerz is an IIT NIT alumni company providing end

to end IT training solutions to Corporates, working

professionals and Freshers

TechPartnerz provides certification training programs for

ITIL-Foundation, ITIL-Intermediate, PRINCE2-Foundation,

PRINCE2-Practitioner, COBIT 5, Cloud Computing etc

Our Software Training Portfolio includes training on QTP,

Selenium, Loadrunner, Jmeter, SoapUI etc.


20/20 2013 T hP t

Thank YouFor any queries feel free to contact [email protected]

Follow TechPartnerz on facebook, Linkedin, twitter
mailto:[email protected]://www.facebook.com/techpartnerzhttp://www.linkedin.com/company/techpartnerzhttp://www.twitter.com/techpartnerzhttp://www.twitter.com/techpartnerzhttp://www.linkedin.com/company/techpartnerzhttp://www.facebook.com/techpartnerzmailto:[email protected]

Learn Software Testing with TechPartnerz 1.ppt

Documents