Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?

Slides:



Advertisements
Similar presentations
Test process essentials Riitta Viitamäki,
Advertisements

Ch-11 Project Execution and Termination. System Testing This involves two different phases with two different outputs First phase is system test planning.
Requirements Specification and Management
Test Automation Success: Choosing the Right People & Process
Software Quality Assurance Plan
IS2210: Systems Analysis and Systems Design and Change
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Software Architecture Prof.Dr.ir. F. Gielen
Project Management.
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
GAI Proprietary Information
Cadle & Yeates Ch 5 Revised by Ivor Perry Sept Detailed Planning - 1.
1 Test Planning CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 9, 2007.
Illinois Institute of Technology
Testing HCI Usability Testing. Chronological order of testing Individual program units are built and tested (white-box testing / unit testing) Units are.
CASE Tools CIS 376 Bruce R. Maxim UM-Dearborn. Prerequisites to Software Tool Use Collection of useful tools that help in every step of building a product.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
High Level: Generic Test Process (from chapter 6 of your text and earlier lesson) Test Planning & Preparation Test Execution Goals met? Analysis & Follow-up.
CSE Senior Design II Test Planning Mike O’Dell Based on an earlier presentation by Mike O’Dell, UTA.
Introduction to Software Testing
Design, Implementation and Maintenance
12 Steps to Useful Software Metrics
Software projects Management & Development Alireza Saebi
 ETL: Extract Transformation and Load  Term is used to describe data migration or data conversion process  ETL may be part of the business process repeated.
Web Development Process Description
S/W Project Management
Extreme Programming Software Development Written by Sanjay Kumar.
Software Testing Lifecycle Practice
Test Organization and Management
SOFTWARE TESTING STRATEGIES CIS518001VA : ADVANCED SOFTWARE ENGINEERING TERM PAPER.
Software Testing Life Cycle
Rational Unified Process Fundamentals Module 4: Disciplines II.
Don’t Just “Test”… Validate!!
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Common Activities Activities and Tasks in the WBS.
CSE 7314 Software Testing and Reliability Robert Oshana Lectures 5 - 8
© Mahindra Satyam 2009 Configuration Management QMS Training.
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
What is Testing? Testing is the process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies.
Project Management All projects need to be “managed” –Cost (people-effort, tools, education, etc.) –schedule –deliverables and “associated” characteristics.
Effort.vs. Software Product “Quality” Effort Product “Quality” Which curve? - linear? - logarithmic? - exponential?
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
Software Testing Process By: M. Muzaffar Hameed.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
System Test Planning SYSTTPLAN 1 Location of Test Planning Responsibilities for Test Planning Results of Test Planning Structure of a Test Plan Test Definitions.
Project Management.
PI2134 Software Engineering IT Telkom.  Layered technology  Software Process  Generic Process (by Pressman)  Fundamental activities (by Sommerville)
QMS Training TM Module.
CIS-74 Computer Software Quality Assurance
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
Test Planning The purpose of test planning  The areas to consider in planning.
CIS 375 Bruce R. Maxim UM-Dearborn
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Software Engineering (CSI 321)
BA Continuum India Pvt Ltd
Software and Systems Integration
12 Steps to Useful Software Metrics
Manfred Huber Based on an earlier presentation by Mike O’Dell, UTA
Introduction to Software Testing
Chapter 1 (pages 4-9); Overview of SDLC
Course: Module: Lesson # & Name Instructional Material 1 of 32 Lesson Delivery Mode: Lesson Duration: Document Name: 1. Professional Diploma in ERP Systems.
Software Testing Lifecycle Practice
{Project Name} Organizational Chart, Roles and Responsibilities
Chapter 2: Building a System
Building a “System” Moving from writing a program to building a system. What’s the difference?! Complexity, size, complexity, size complexity Breadth.
Unit IV – Chapter 2 V-Test Model.
Presentation transcript:

Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan? –A document that outlines What is the goal of this testing effort (exit criteria) What are the items to be tested –High level list –Detailed features What test process will be used –For different deliverables and different features –What record keeping and measurements will be performed What resources are needed What is the schedule What are the risks and contingencies

Goal(s) of Your Testing Goals may be different for each test. –They often need to match the product goal or the project goal –Generic : “Meets customer requirements or satisfaction” is a bit too broad. –A Level Deeper Examples are: Ensure that all the (requirements) features exist in the system Ensure that the developed components and the purchased components integrate as specified Ensure that performance targets (response time, resource capacity, transaction rate, etc) are met. Ensure the system is robust (stress the system) Ensure that the user interface is “clear,” “novel,” or “catchy,” etc. Ensure that the required functionality and features are “high quality.” Ensure that industry standards are met. Ensure that internationalism works (laws and looks) Ensure that the software is migratable

Test Items Testing the deliverables (Depends on the goal): –Requirements specification –Design specification –Executable code –User guides –Initialization data Testing the individual function/features (Depends on the goal): –Logical application functions (list all of them – usually from requirement spec from the users perspective) –At the detail level for small applications (list all the modules – from design spec. or build list from development perspective) –User interfaces (list all the screens – usually from Req. and Design spec.) –Navigation (if usability is a goal)

Not included in the Test List of items not included in this test Possible Reasons: –Low risk items –Future release item that is finished coding phase –Not a high priority item (from req. spec.)

Test Process What testing methodology will be applied: –Non executable – formal inspection, informal reviews, (unit test user guide examples) –Executable – unit test, functional test, system test, regression test, etc. Blackbox testing –Data flow testing –Boundary analysis –Stress testing and performance testing –Installation test Whitebox testing –Path testing –Object testing (inheritance, polymorphism, etc.) What test-fix methodology will be applied What “promotion” and locking mechanism will be used. What data will be gathered and what metrics will be used to gauge testing. –# of Problems found by severity, by area, by source, by time –# of problems fixed, returned with no resolution, in abeyance –# of problems resolved by severity, turn around time, by area, etc. How to gauge if goals are met –Metrics for validating the goal –Decision process for release

Test Resources Based on the amount of testing items and testing process defined so far, estimate the people resources needed –The skills of the people –Additional training needs –# of people The non-people resources needed –Tools Configuration management Automated test tool Test script writing tool –Hardware, network, database –Environment (access to developers, support, systems, etc.)

Test Schedule Based on: –Amount of test items –Test process and methodology –Test resources A schedule containing the following information should be stated: –Task –Assigned person –Time duration

Risks and Contingencies Examples of Risks: –Changes to original requirements or design –Lack of available and qualified personnel –Lack of (or late) delivery from the development organization: Requirements Design Code –Late delivery of tools and other resources State the contingencies –Move schedule –Do less testing –Change the goals and exit criteria