By :

“My software never has bugs, it just develops random features” – Justine Hunter

TALK FLOW STLC MODELS PHASES OF STLC STLC & SDLC THE TEST PROCESS OVERVIEW DOCUMENTATION OVERVIEW USES OF DOCUMENTATION DOCUMENTATION LIST TESTING PHASES REFERENCES

STLC MODELS

Waterfall Methodology

The waterfall method is a variation of the systems development life cycle model used in software engineering. The method is seen as the classical approach to the systems development life cycle .

The name from this method comes from its biggest draw back. Once water has passed over the edge of the waterfall it cannot go back, similarly, once a stage has been completed there is no going back to it

Spiral-Iterative Methodology

The spiral is a risk-reduction oriented model that breaks a software project up into mini-projects, each addressing one or more major risks. After major risks have been addressed, the spiral model terminates as a waterfall model.

Developed by Barry Boehm in 1988. it provides the potential for rapid development of incremental versions of the software

The V-Model

The V-model can be said to have developed as a result of the evolution of software testing. Various testing techniques were defined and various kinds of testing were clearly separated from each other which led to the waterfall model evolving into the V-modelThe V is for how it looks like. The ‘V’ can also stand for the terms Verification and Validation

Verification Phases•Requirements analysis•System Design•Architecture Design•Module Design•Coding

Validation phases•Unit Testing•Integration Testing•System Testing•User Acceptance Testing

The V-Model-Contd

The Agile method is a low-overhead method that minimizes risk by making sure that software engineers focus on smaller areas of work. It emphasizes values and principles rather than processes. Agility is the ability to cope with the change

Agile Methodology

Agile methods try to keep overheads such as rationale, justification, documentation and meetings as low as possible Agile and as a result of it, agile methods seem benefit small teams where the requirements are often changing, rather than larger projects

SDLC and STLC

The Testing Process overviewProject Initiation

Test Strategy and Planning

Test Environment setup

Test Case Designing

Test Execution

Defect Reporting and Tracking

Project closure

Test Cycles

• Introduction– Integral part of formalization of testing– Important for conducting the test and reuse of the test program during maintenance– Test documentation should start in the requirements phase and continue throughoutthe life cycle of the project– Document test process that has been outlined in each phase of the life cycle.– Structured documentation is easier to update and reuse

Uses of Documentation

– Verify correctness of requirements– Improve user understanding of information services– Improve user understanding of application systems– Justify test resources– Determine test risk– Create test transactions– Evaluate test results– Retest the system– Analyze the effectiveness of the system

STANDARS USED

• Standards of documentation– TCS follows IEEE approach of documentation– IEEE provides a hierarchy of documentation for carrying out tests• Details of each test document should include– Purpose of document– Name of document and Identification Number

(TCS follows the Internationally accepted IEEE standard)

DOCUMENTATION LIST

– Test Strategy Plan– Test Plan– Test Design Specification– Test Case Specification– Test Log– Test Defect Report– Test Summary Report

• Test Strategy Plan

– Contains the following sections• Scope• Test Activities• Test Documentation list• Testing Responsibilities• Methodologies, techniques and tools

• Test Plan

– The test plan provides an overview of the testing effort for the product.– A Test Plan is according to the IEEE Test Plan and includes any refinement ofapproach that would go into the IEEE Test Design Specification

– Structure of Test Plan

• Test Plan Identifier• Introduction• Test Items• Features to be Tested• Features not to be Tested• Approach• Item pass/fail criteria• Testing Guidelines and Standards• Severity Level Classification• Testing Tasks• Test Deliverables• Environmental needs• Responsibilities• Staffing and Training needs• Schedule• Risks and Contingencies• Approvals• Suspension and Resumption Criteria

Test Design Specification

– Contains the following sections• Test design specification identifier• Features to be tested• Approach Refinements• Test identification• Feature pass/fail criteria

Test Case Specification

– Includes the following sections• Test case specification identifier.• Test items• Input specifications• Output specifications• Environmental needs• Special procedural requirements• Inter- case dependencies

• Test Log

– Contains the following sections• Test Log identifier• Description• Activity and event entries– Execution description– Procedure results– Environmental information– Unexpected events

• Test Defect Report

– A Test Defect Report describes any event that occurs during testing that requiresfurther investigation.– A defect-tracking tool would be used for Test Defect Reporting.– It follow a process of Acceptance, Investigation and Closure through Change Notes,the entire life cycle of which is controlled through the tool

• Test Summary Report

– Contains the following sections• Test summary report identifier• Summary of Product tested• Any deviations from the specified test procedures• Summary of results• Summary of activities• Sign Off documents

Test Plan

• What is a Test Plan?– Test plan is a document that describes how testing will be accomplished. It is similar to Project Plan.

Need for Test Plan• If you fail to plan – you plan to fail• One of the keys to successful software testing• Discuss issues early• Enables to decide in advance:– how a project’s objectives will be met– with the resources available– to the time scales required– and the quality desired– while controlling risk

Test Plans for different levels of Testing

• Level-specific Test Plan– Master Test Plan– Unit Test Plan– Integration Test Plan– System Test Plan– Acceptance Test Plan

• Major considerations are the same, but differ in scope– Scope depends on the level of testing

Master Test Plan• Major communication and control device for Test Manager• Used to decide important issues and how to deal with them– Testing strategy– Resource Utilization– Responsibilities– Risks– Priorities• Not to create a list of Test cases• Other test plans (Acceptance, System) are focused in approach catering to need of aparticular test

Test Plan• The five main items in a Test Plan– Scope– Resources– Time– Quality– Risk– And the others…….• ToC of a Test Plan confirming to IEEE standards

Contents of Test Plan

• Scope clauses define what will be covered in a project– Test items• Items of software, and hardware, and combinations of these, which will be tested.– Programmers or Developers point of view– Contents depend on level of the Test Plan– Features to be tested• Which parts of the software specification are to be tested?– User or customer point of view– Contents depend on level of the Test Plan– Help to focus on software risks– Features not to be tested• Which parts of the software specification are to be excluded?– Reason for not testing– Normally lists low risk features

• Resource clauses give overall view of the resources to deliver the tasks.– Environmental Needs• What is needed in the way of testing software, hardware, offices etc.– Hardware configuration– Data– Interfaces– Facilities, Security Access, etc.– Responsibilities• Lists who has responsibility for delivering various part of the plan

– Staffing and training needs• Number people and skills needed to execute the plan• Training needs might include– How to use tool– Testing Methodology– Interfacing systems– Management systems such as defect tracking, configuration management,basic Business knowledge (related to the system under test), etc.

• Time clauses specify the tasks to be undertaken to meet the quality objectives and when they occur.– Testing tasks• Tasks that are necessary for and perform test execution and the dependencies,the elapsed time they will take, and resource required.– Schedule• This specifies when the tasks will take place.– Build around milestones– Reference to project schedule– Include deadlines– Estimation and resources are considered• Quality clauses cover to what standard the testing will be completed against the scope.– Introduction section• This gives a high level view of the testing standard. Specifies overall testobjectives.– A basic description of the project or release including key features, history,etc.,– An introduction to the plan that describes the scope of the plan.– Item pass/fail criteria• This defines how the item being tested has passed.– Each test item needs to have an expected result.– Describes severity

• Quality (cont..)– Approach• Heart of the Test Plan• This gives details of how the testing process will be followed.– Overview of procedures to carry out Testing activities– Entry and exit criteria for every levels (in Master Plan)– Configuration management– Change Management– Test Environment, Fixing, Reviewing and Retesting– Metrics collection– Use of Tools– Test deliverables• This specifies the test documents and other deliverables produced.– Test Plans– Test Design Specs– Test Cases– Custom Tools– Defect Reports– Test Summary Reports– Simulators (if any).

• Others– Test plan identifier• This is a unique name or code by which the plan can be identified in the project'sdocumentation including version.– Approvals• This clause contains the signatures of the various stakeholders in the plan, toshow they agree in advance with what it says.– Various stakeholders signature– Different Approvers for different levels of Test Plan– Approvers should involve in the creation and/or review of the plan

http://www.softwaretestinggenius.com/articalDetails.php?qry=159

http://www.coolinterview.com/interview/15292/

https://iqmskm.ultimatix.net/km/index.php/Testing

https://iqmskm.ultimatix.net/km/index.php/Test_Automation_Process_HanDbook

http://www.softwaregeeks.com/articalDetails.php?qry=443