Join the social network of Tech Nerds, increase skill rank, get work, manage projects...
  • Test procedures before releasing the software

    • 0
    • 1
    • 1
    • 1
    • 0
    • 0
    • 0
    • 0
    • 128
    Comment on it

    We follow few steps before giving release of the application:

    1. Test Strategy:
    A Test Strategy document is a high level document which are prepared by a Test Lead or project manager. This document can be explain about Software Testing Approach to achieve Software testing goals. The Test Strategy is basically acquired from the Business Requirement Specification document. Some companies prepare the Test Approach or Strategy inside the Test Plan document, which is sufficient for small-size projects. For larger projects, it is advisable to prepare a separate Test Strategy document describing the overall strategy and a individual test plan for each level of testing.

    Components of the Test Strategy document

    • Scope and Objectives
    • Business issues
    • Roles and responsibilities
    • Communication and status reporting
    • Test deliverables
    • Industry standards to follow
    • Test automation and tools
    • Testing measurements and metrics
    • Risks and mitigation
    • Defect reporting and tracking
    • Change and configuration management
    • Training plan

    2. Test Methodology:

    Following Methodologies used Software Testing:

    • Unit Testing
    • Acceptance Testing
    • Functional Testing
    • Performance Testing
    • Security Testing

    3. Test Plan:

    The Test Lead and Test Manager prepares the Test Plan document generally before testing starts with and objective to describe "what to test, how to test, when to test and who will do". For the test phases, each test phase have its own Test Plan documents.

    Components of the Test Plan document

    • Test Plan id
    • Introduction
    • Test items
    • Features to be tested
    • Features not to be tested
    • Test techniques
    • Testing tasks
    • Suspension criteria
    • Features pass or fail criteria
    • Test environment (Entry criteria, Exit criteria)
    • Test deliverables
    • Staff and training needs
    • Responsibilities
    • Schedule
    • Test design

    A test design technique helps tester to select whether a set of test is good or not from rest of other set of test or we can say that it helps tester to chose a good set of tests given system. There are many different types of software testing technique, each with its own strengths and weaknesses.

    Following are the typical design techniques in software engineering:

    1. Black box test design technique.

    • Boundary Value Analysis (BVA)
    • Equivalence Partitioning (EP)
    • Decision Table Testing
    • State Transition Diagrams
    • Use Case Testing

    2. Component or System testing.

    • Statement Coverage
    • Branch Coverage
    • Path Coverage
    • LCSAJ Testing

    3. Its based on tester's experience:

    • Error Guessing
    • Exploratory Testing

    6. Test execution:

    Test execution process are used in the final stage to testing, It involves the execution of test cases or test script, manually or in an automated form with the help of Test execution process able to fix the identified bugs as soon as possible.

    7. Test reporting:

    Following documents will be prepared for Test reporting:

    • Test Strategy document
    • Test Plan document
    • Test case doc
    • Traceability matrix
    • Bug Report

    8. Test Closure:

    Once the testing phase completed successfully then Test Lead prepare closure report. Which can be reviewed by various stake holders like Test architect, Test manager, Business Analyst, Project manager and finally approved by clients.

 0 Comment(s)

Sign In

Sign up using

Forgot Password
Fill out the form below and instructions to reset your password will be emailed to you:
Reset Password
Fill out the form below and reset your password: