Why is the test strategy necessary? - PowerPoint PPT Presentation

About This Presentation
Title:

Why is the test strategy necessary?

Description:

The testing strategy is essential keeping in mind your plans. It helps you identify the strategy, besides helps you to focus on how to use testing to manage your project and product risks, which makes the testing strategy more important. – PowerPoint PPT presentation

Number of Views:79
Slides: 13
Provided by: nexsoftsys

less

Transcript and Presenter's Notes

Title: Why is the test strategy necessary?


1
8 Things to Keep In Mind before Starting
With Test-Plan
2
Introduction
Test Case Development
Environment Setup
Test Execution
Requirements Analysis
Test Planning
Test Cycle Closure
2
3
1
4
5
6
  • In Software testing, There is much debate that
    how to achieve quality and how to plan the
    testing activities.
  • This tutorial will explain to you all
    about Software Test Plan and suggest the ways on
    how to plan test activities from scratch along
    with the test planning and test execution.
  • Most of what is expected to achieve quality in a
    software test phase with best practices are
    summarized in this topic. These practices have an
    impact in addition to improving Quality.

3
8 Things Keep In Mind
Analyze the product
Plan Test Environment
Design the Test Strategy
Schedule Estimation
Define the Test Objectives
Identify Entry and Exit Criteria
Resource Planning
Determine Test Deliverables
4
Design the Test Strategy
Analyze the product
  • Design Test Strategy is essential when keeping a
    plan in mind.
  • Test Strategy tells you how to use testing for
    managing project and product risks.
  • It contains the process which needs to be
    bifurcated into different levels of testing
    phases.
  • It also indicates which testing strategy should
    be used in which situation? Strategies can differ
    based on project requirements like regulatory
    requirements, risk levels, and different
    methodologies of software development.
  • Product analysis processes to become familiar
    with the product! What does it do? What does it
    look like? All this information you would need to
    be asked before a product can be analyzed.
  • It is also important to consider how it becomes
    user-friendly.

5
Define the Test Objectives
Resource Planning
  • The goals and objectives of software testing are
    numerous, which when achieved help developers
    build defect-less and error-free software.
  • Understand the scope of your application.
  • Based on this we must plan our resources and
    other related activities.
  • Our resource planning should be well enough
    effective that will show how we are going to use
    our resource in all testing phases.

6
Plan Test Environment
Schedule Estimation
  • Schedule and estimation are one of the important
    parts of product development.
  • It shows how things will go during the
    development.
  • The schedule is basically told that how the
    things will be delivered to the customer. It
    shows the delivery schedule of the product.
  • Test Estimation, on the other hand, is a
    management activity that serves how long a task
    would take to complete.
  • Estimating effort for the test is one of the
    major and important tasks in Test Management.
  • It is one of the most important Phases for the
    tester, which plays a key role in achieving
    success in the testing.
  • It provides all the pre-requisites that are
    required to perform the task of testing on a
    particular software product.

7
Identify Entry and Exit Criteria
Determine Test Deliverables
  • Entry and exit criteria in the testing cycle
    define when to start and when to stop testing.
  • This is a very crucial stage to identify these
    constraints in the testing cycle.
  • We must have knowledge about the areas and
    conditions in product development where to start
    with our testing when to stop.
  • Test Deliverables are the artifacts that are
    given to the customer in the form of software
    projects during the development lifecycle.
  • There are different test deliverables at every
    phase of the software development lifecycle.
  • Determine and plan the test deliverables.
  • Provide the evidence of your deliverables which
    can show your efforts to be applied in the
    project to build quality.

8
Key practices that improve overall software
quality include the following
  • Keep eye on driving requirements and have a focus
    on crucial use cases of the application early in
    the development cycle.
  • Use tracking metrics and indicators to measure
    progress and quality.
  • One of the important aspects of the testing life
    cycle is planning.
  • Hence Test-Plan document plays a very important
    role in testing.

9
  • It is a detailed extensive document that
    basically has outlines of your strategy, Test
    Estimation, test deliverables, resources
    (manpower, software, and hardware) required for
    testing, test schedule, etc. from a Selenium
    Testing Services Providers.
  • The Test Plan document is derived from the
    product Requirement Specification, or Use Case
    Documents. It is usually prepared by a testing
    team especially by a lead or manager who is
    taking care of all the testing activities in
    product development.
  • The document contains what to test, how to test
    when to test and who will do what test.

10
  • Avoiding deterioration of software quality over
    time requires a conscious effort, both on the
    part of the Product Owner and the engineering
    team.
  • Have the pre-plan before starting with the
    testing phase is one of the best steps towards
    gaining quality.
  • The test plan should be reviewed a number of
    times prior to baselining it or sending it for
    approval.
  • The quality of your test plan speaks volumes
    about the quality of the testing you or your team
    is going to perform.
  • Update the plan as and when necessary.
  • An outdated and unused document stinks and is
    worse than not having the document in the first
    place.

11
NEX SOFTSYS
Offshore Software Development Company
Head Office ( INDIA )
Branch Office ( New York )
"Royal Square 1st Floor, Off No. 110, Nr. Shilp
Tower, Tagore Road, Rajkot - 360 001, Gujarat -
India
477 Madison Avenue, 6th floor, NEW YORK 10022,
United States of America
Mail
info_at_nexsoftsys.com
Site
www.nexsoftsys.com
12
Thank You
Write a Comment
User Comments (0)
About PowerShow.com