CS4723 Software Validation and Quality Assurance Lecture 15 Advanced Topics Test Plans and Management.

Slides:



Advertisements
Similar presentations
Effective Test Planning: Scope, Estimates, and Schedule Presented By: Shaun Bradshaw
Advertisements

Testing Workflow Purpose
Test Yaodong Bi.
Test process essentials Riitta Viitamäki,
Verification and Validation
Software Process Models
Stoimen Stoimenov QA Engineer SitefinityLeads, SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
T. E. Potok - University of Tennessee Software Engineering Dr. Thomas E. Potok Adjunct Professor UT Research Staff Member ORNL.
Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 Pittsburgh, PA Lecture 6: Team Planning.
1 In-Process Metrics for Software Testing Kan Ch 10 Steve Chenoweth, RHIT Left – In materials testing, the goal always is to break it! That’s how you know.
ACS 567: Software Project Management Spring 2009 Instructor: Dr. John Tanik.
The Production Process
SE 450 Software Processes & Product Metrics Reliability: An Introduction.
Software Release Readiness Metric ShipIT [0,1] Piyush Ranjan Satapathy Department of Computer Science & Engineering University of California Riverside.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Execution and Reporting Adrian Marshall.
(c) 2007 Mauro Pezzè & Michal Young Ch 1, slide 1 Software Test and Analysis in a Nutshell.
Testing Metrics Software Reliability
Testing - an Overview September 10, What is it, Why do it? Testing is a set of activities aimed at validating that an attribute or capability.
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?
Software Testing Prasad G.
Stoimen Stoimenov QA Engineer QA Engineer SitefinityLeads,SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
Introduction to Software Testing
Extreme Programming Software Development Written by Sanjay Kumar.
Semester 1, 2003 Week 7 CSE9020 / 1 Software Testing and Quality Assurance With thanks to Shonali Krishnaswamy and Sylvia Tucker.
Software Quality Assurance Lecture #8 By: Faraz Ahmed.
On the Testing Maturity of Software Producing Organizations Mats Grindal Jeff Offutt Jonas Mellin.
Software Testing Lifecycle Practice
Test Organization and Management
Testing – A Methodology of Science and Art. Agenda To show, A global Test Process which work Like a solution Black Box for an Software Implementation.
Fourteenth Lecture Hour 9:30 – 10:20 am, Sunday, September 16 Software Management Disciplines Project Control and Process Automation (from Part III, Chapter.
Final Exam Review June 2, 2011SE 477: Final Review1/19.
Software Testing Course Shmuel Ur
1 © Quality House QUALITY HOUSE The best testing partner in Bulgaria.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Top Down View of Estimation Test Managers Forum 25 th April 2007.
QUALITY ASSURANCE PRACTICES. Quality Plan Prepared and approved at the beginning of project Soft filing system approach followed. Filing location – –
Verification and Validation Assuring that a software system meets a user's needs.
CS3100 Software Project Management: Monitoring & Control 1 Software Project Management Week 10: Project Monitoring & control Ian Blackman.
February 15, 2004 Software Risk Management Copyright © , Dennis J. Frailey, All Rights Reserved Simple Steps for Effective Software Risk Management.
Chair of Software Engineering Exercise Session 6: V & V Software Engineering Prof. Dr. Bertrand Meyer March–June 2007.
Slide title In CAPITALS 50 pt Slide subtitle 32 pt Risk-based regression testing in a telecommunication system node Master’s thesis presentation
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
Software Engineering Lecture 8: Quality Assurance.
T EST T OOLS U NIT VI This unit contains the overview of the test tools. Also prerequisites for applying these tools, tools selection and implementation.
QC – User Interface QUALITY CENTER. QC – Testing Process QC testing process includes four phases: Specifying Requirements Specifying Requirements Planning.
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?
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
Week # 4 Quality Assurance Software Quality Engineering 1.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
Applied Software Project Management SOFTWARE TESTING Applied Software Project Management 1.
Chapter 11 Project Management.
Automated Software Testing
Software Engineering (CSI 321)
CSC 480 Software Engineering
Software Testing.
Software testing
Importance Of Software Testing Why software testing is important? Importance of Software Testing is precisely about to look at the item quality using various.
Introduction to Software Testing
Rest of Project Management
Software Assurance Maturity Model
Risk Management - Manage them or they will manage you...
Fundamental Test Process
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Quality Measurable characteristic Cyclomatic complexity Cohesion
Project Management Chapter 11.
Software Testing Lifecycle Practice
Presentation transcript:

CS4723 Software Validation and Quality Assurance Lecture 15 Advanced Topics Test Plans and Management

Test Plan & Management Something you are going to think about when you are a project manager instead of a tester / developer About handle the testing progress of a whole software project About quality assurance at highest level Approach: risk based testing

Presentation Outline Introduction - The ChallengeWhy? Risk Analysis and Testing Risk Based Test Approach What? Test Metrics Risk Based Test Metrics Risk Analysis in Risk Based Testing Risk Analysis in Practice Plan and Manage - Metrics How? Quality and Progress Monitoring Warning! Organization and Process...

The Challenges Time Constraints Resource Constraints Quality Requirements Risk Factors: New technology Lack of knowledge Lack of experience Take Control!

Presentation Outline Introduction - The Challenge Risk Analysis and TestingWhat? Risk Based Test Approach Test Metrics Risk Based Test Metrics Risk Analysis in Risk Based Testing Theory and Practice Plan and Manage Quality and Progress Monitoring Warning! Organization and Process...

Risk Analysis and Testing Risk Identfication Risk Strategy Risk Assessment Risk Mitigation Risk Reporting Risk Prediction Testing, Inspection etc. Test Plan Metrics: Cost and Probability Test Item Tree Test Metrics

Risk Based Testing - Approach Risk Identification / Test Items Identify the items to be tested Functions, classes, features, transactions, … Risk Strategy / Test Plan: Setup approaches to generating test cases Automatic / Manual Original / Regression Load / Security / Usability /,,, Risk Assessment / Metrics Assess risk of each test items

Risk Based Testing - Approach Risk Mitigation / Testing Generate and execute the concrete test cases Risk Reporting Measure how much have we mitigated the risk Test coverage Found and fixed bugs Risk Prediction Based on the risk reports, predict risks of test items for new round of testing

Risk Based Testing - Metrics Identify Areas with “High Risk Exposure” Probability and Cost All functions/modules should be tested to a “minimum level” “Extra Testing” in areas with high risk exposure Establish Test Plan and Schedule Monitor Quality Number of Faults per function and time Monitor Progress Number of hours in test and fix -> ETC

The Formula Re(f) - Risk Exposure of function f P(f) - Probability of a fault in function f C(f) - Cost related to a fault in function f Risk Based Testing - Theory

Simple Test Metrics Test Planning Number of test cases per function Number of hours testing per function Progress Tracking Number of tests planned, executed and completed Number of faults per function Number of hours used for test and fix Estimated to Complete

Simple Test Metrics Probability of faults - Indicators New functionality Size Complexity Quality of previous phases and documents Cost of Faults

Presentation Outline Introduction - The Challenge Risk Analysis and Testing Risk Based Test Approach Test Metrics Risk Based Test Metrics Risk Analysis in Risk Based TestingHow? Theory and Practice Plan and Manage Quality and Progress Monitoring Warning! Organization and Process...

Risk Based Testing - Example Other Probability Factors might include: Function Points, Frequency of Use etc. Ranking the functions based on Risk Exposure The Probability of a Fault The Cost of a Fault Example:

Consequence Probability Low High Risk Based Testing - Reporting LowMedium High Consequence Probability

Prior to test execution: identify critical transactions 1 Test Execution identifies “bad” transactions 2 Extra Testing: - Additional testing by product specialist - Automated regression testing 3 Risk Based Testing - Practice

Presentation Outline Introduction - The Challenge Risk Analysis and Testing Risk Based Test Approach Test Metrics Risk Based Test Metrics Risk Analysis in Risk Based Testing Theory and Practice Plan and ManageHow? Quality and Progress Monitoring Warning! Organization and Process...

Two Strategies On-line Risk Analysis Usually used for first time testing Cold start with little data Minimal testing and a small list of critical features provide by customers Batch Risk Analysis Assume a large amount of data at the beginning Different metrics

Planned Executed QAed Planning and Progress Tracking

Progress Indicators - “To be vs. Actual” “To be fixed” vs. “Actually fixed” To be retestedAct. retested Rejected To Be Restested, Actually Retested and Rejected Number of Faults “To be Retested” vs. “Actually Retested” Actually fixed To Be Fixed and Actually Fixed Number of Faults To Be Fixed

Progress Indicators - Hours Used Batch Number of hours for finding one fault and for fixing one Online Number of hours for finding one fault and for fixing one Hours per Fault for Test and Fix Date Hours per Fault Test Fix Test Fix Hours per Fault for Test and Fix Hours per Fault

“Estimated to Complete” ETC for system test based on: Number of hours testing per fault found Number of hours fixing per fault Number of faults found per function Number of fixes being rejected Number of remaining tests (functions to be tested) Estimated to Complete at Time t Actual to Complete at Time t

Benefits of Risk Based Testing Improved Quality? all critical functions tested Reduced Time and Money in Testing effort not wasted on non critical or low risk functions Improved customer confidence due to customer involvement and good reporting and progress tracking

Presentation Outline Introduction - The Challenge Risk Analysis and Testing Risk Based Test Approach Test Metrics Risk Based Test Metrics Risk Analysis in Risk Based TestingHow? Theory and Practice Plan and Manage Quality and Progress Monitoring Warning! Organization and Process...

WARNING! Require a focused Organization… Strong Test Management Testers to “drive” the Programmers Responsibility …and a well defined Process Documentation Planning and Execution Procedures Control Procedures Planning and Progress Tracking

LD PD Test Exec PTDs Raised Fix CR Fix Procedure Problem Mngmnt. Procedure Test Exec. Procedure Case Build Procedure Case Quality Standards Change Mngmnt. Procedure Re- test Good/ Bad Test Completed Regression Test Good Bad ProAte QC / QA Basic Test Data Test Case Risk Identification Risk Assessment Risk Mitigation Risk Reporting Risk Prediction Test Process Work Flow

Summary Risk Based Test Approach Focused Testing Reduced Resources Improved Quality Metrics are fundamental Process and Organization must support the new strategy Metrics must support the organization and process