Triaged Tester

March 17, 2009

Deliverables @ various phases

Filed under: Black Box Testing,Deliverables,Test Management — Triaged Tester @ 9:10 am
Tags: , ,

This diagram does not depict when and where are the test plan and test strategy documents generated.Ideally, these documents are ready before you begin the test activities

test Deliverables @ phases


February 10, 2009

Test Automation Methodology

Filed under: Automation,Checklist,Deliverables,Guidelines,Tips — Triaged Tester @ 1:03 pm




Identification of Automation Objectives/Test Requirements Study

Ø  Understanding the objectives of Automation for design of an effective test architecture

Ø  Understanding of the test requirements/application requirements for automation

Test Automation Strategy Document

Identification of Tool

Ø  Normally done in the proposal stage itself

Ø  Application of Tool Selection Process of eTest Center to arrive at the best fit for the given automation objectives


Script Planning & Design

Ø  Design of Test Architecture

Ø  Identification of Reusable functions

Ø  Identification of required libraries

Ø  Identification of test initialization parameters

Ø  Identification of all the scripts 

Ø  Preparation of Test design document – Application of Naming Conventions

Ø  Test Data Planning

Design Document

Test Environment Setup

Ø  Hardware

Ø  Software – Application, Browsers

Ø  Test Repositories

Ø  Version Control Repositories

Ø  Tool setup


Development of Libraries

Ø  Development of libraries

Ø  Debug/Testing of libraries

Phased delivery if applicable

Development of Scripts

Ø  Development of scripts

Ø  Debug/Testing of scripts

Phased delivery if applicable

Development of Test Suites

Ø  Integration of Scripts into test Suites

Ø  Debug/Testing of Suites

Test Suites & Libraries

Deployment/Testing of Scripts

Ø  Deployment of Test Suites

Test Run Results, Defect Reports, Test Report

January 23, 2009

Test Team deliverables

Filed under: Deliverables — Triaged Tester @ 7:11 am

The specific deliverables may vary from project to project. Below is just a guideline.


Product Definition Process: Early Product Planning – Plan out what we want

  • If not current delivering a product QA should be developing knowledge about
    • New Technologies the product will be based on
    • Customer segment to be addressed
  • Requirements: Nail down product and project requirements(Functional specifications)
    • High Level QA  Plan (testing practices, tools, approach, standards, tools) – QA Mgr
    • High Level Resource estimations based on Feature lists – QA Mgr
    • Review Test Plan template and propose any changes
  • Design:  Design the architecture and testing of the product (Design Documents and Test Plans)

o   Test Specs complete, reviewed and signed off

o   Bottoms up test schedules created and reviewed

o   BVTs and Automation designed

o   Security Testing Planned

o   Globalization/Localization Test Planned

o   Performance / Scale Testing planned

  • Implementation: Code the product/application (Code Complete)
    • BVTs created and automated
    • All BVTs pass 100% on 100% of features
    • Basic end-to-end scenarios pass
    • Test cases defined
    • Release Criteria Created and Signed off
  • Verification: Stabilize the product (Stabilization/Technical Preview)
    • Test automation complete
    • Security test pass
    • Globalization / Localization Validation
    • First Performance and Soak Validation
    • Evaluate Code Coverage and add Cases where needed
    • Customer Support / help and Evaluation of problems found in field
  • Evaluate the product (Beta)
    • Review Test Coverage and enhance test sets where needed
    • Expansion of platform on which automation is run
    • Large Scale Deployment Validation
    • Design change Requests
      • Speclette Reviews
      • Test Planlette creation
      • Cost Estimation
      • Approval
      • Test Execution
    • Customer / Support and Evaluation of problems found in field
    • Documentation Reviews
  • Release Candidate:  Produce Release candidate and drop to end users
    • Customer Support / Support and Evaluation of problems found in field
    • Continued automation
  • Ship the product (RTM, RTW, RTS)
    • Release Validation
    • Prepare for Sustained Engineering Handoffs
  • End of Life Process Post-RTM – Clean up and distribution.
    • Automation handoff to Sustained Engineering
    • Support Sustained Engineer
      • Regression support for enhanced feature request
      • Problem identification for problems found in field 

Create a free website or blog at