Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Test Strategies

No description
by

Olha Tester

on 3 March 2016

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Test Strategies

Test Strategies
What is Test Strategy?
Types of Test Strategies
Test Strategies Developing
Test strategy
is a high-level description
of the test levels to be performed
and the testing within those levels for an organization or program
(one or more projects)
(by ISTQB Glossary)
Test Approach
Test Strategy defines:
objectives
methods
resources
timing
environment
Object (requirements)
based approach:
Smart regression:
Analyze changes to define regression scope;
Use traceability matrices, analyze technical risks to make a decision;
Use quality risk analysis to determine what areas have high business risk.
Quality-Based Strategy:
Use a quality standards like ISO 9126 to identify the important “-ilities” for your system and test them.
How to choose?
Format
MS Word or Adobe Document
Other realizations
is an implementation of the test strategy for a specific project


by Vitaliy Kupchynskyy
& Olha Chopyk


August 2014
Agenda
What is Test Strategy?
Test Strategy types
How to choose?
Real Examples
Again, it depends on:
objectives
methods
resources
timing
environment
How to choose?
Risks based approach:
Fully informed approach:

Use various available sources of information to identify quality risks;
Analyze quality risk to prioritize them;
Adjust the tests according to the risk priority levels.
Analytical:
Use requirements, design, and implementation objects to determine testing focus;
Objects include requirements specifications, design specifications, UML diagrams, use cases, etc;
Relies on extensive documentation and does not work well when documentation is not available or incomplete.

Start with the object-guided or risk-based strategy but take the analysis further;
Study the system, use-cases, configurations, and all available data;
Design and execute tests based on the knowledge gained in analysis.

Assumes that everything can and will have bugs;
Tries to reach exhaustive coverage.
Philosophical
test strategies:
Exhaustive strategy
Shotgun strategy
Assumes that everything is buggy;
Accepts that exhaustive testing is impossible;
Randomly distributes the test effort within the given resource and schedule.
Externally Guided Test Strategy
Accepts that you cannot test everything, and that you can’t know where the bugs are;
Trusts to others guidance;
Common guides include programmers, users, technical or customer support, help desk staff, business analyst...
E.g. User-directed testing Strategy
Regressions:
Learning-based approach:
Use checklists that are developing over time to guide your testing
Brute-force
regression approach:
You repeat all of your tests
Methodical:
Function-Based approach:
Identify each and every function of the system;
Test each at least once

Identify every state and every state transition that can occur;
Test them.

State-Based approach:
Process-Oriented:
Automated Functional:
Standards-Oriented:
Idea is to follow official or recognized standards (like IEEE 829 standard for test documentation).
It makes the test process transparent and comprehensible to programmers, managers, business analysts, and other non-testers.
Testing follows lightweight processes, mostly focused on technical risk
Follow selected agile SDLC and use its best practices
Agile-based:
Means testing system functionality using repeatable scripts
Relies on the ability to effectively automate most of the needed testing
Dynamic:
Test Plan
VS
Test Strategy
Test plan
is a document describing the scope, approach, resources and schedule of intended test activities.
Developed once per release.


Test strategy
is developed for particular project (or group of them)
Test Strategy
is an outline that describes the testing approach of the software development cycle.
( by Wikipedia)
Test Levels
is a group of test activities that are organized and managed together
(by ISTQB Glossary)

Exploratory:
Bug Hunting:
Uses bug classifications, statistic to assume where the bugs are and to focus testing on buggy areas.

Intuitive:
Relies on simultaneously learning of the system’s behavior and design while test run.
Test approach is continuously reviewed and improved according to test results.

Testing process is built according to the collective experience, wisdom and gut instincts
of the test team
Domain-Based:
Model-Based Strategies:

Define domains of inputs, processing, or outputs;
Analyze analysis of different domains;
Picks 'the best' test cases in each domain.
Scenario-Based:
You test according to real-world scenarios.

Use-cases-Based:
Relies on object-oriented design documents known as use cases.


Thank you!
?
Combine them!
:)
Reactive Test Approach
VS
Proactive Test Approach
Reactive Testing is the philosophy of waiting to to design and implement tests until the software is received, reacting to the actual system under test. In other words, testing process
reacts
on what was developed
Proactive Testing approach looks for ways to prevent defects, that is why it also called 'Preventive approach'.
This approach allows reduce time and cost of development ("Early testing" law)
Test strategies
for Real Projects
(demo & discussion)

Full transcript