1 11-Jul-08 COPYRIGHT NOTICE Copyright © 2008 Polaris Software Lab Limited All rights reserved. These materials are confidential and proprietary to Polaris.

Slides:



Advertisements
Similar presentations
PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
Advertisements

Automated Software Testing: Test Execution and Review Amritha Muralidharan (axm16u)
HP Quality Center Overview.
OPSM 639, C. Akkan Monitoring Progress How does a project get one year late? … One day at a time –Frederick P. Brooks MBWA: Management by Walking Around.
Software Testing Workshop Regression Automation 11-Jul-08 COPYRIGHT NOTICE Copyright © 2008 Polaris Software Lab Limited All rights reserved. These materials.
Copyright Princeton University This work is the intellectual property of Princeton University. Permission is granted for this material to be shared.
Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Software Testing Workshop 11-Jul-08 COPYRIGHT NOTICE Copyright © 2008 Polaris Software Lab Limited All rights reserved. These materials are confidential.
Stoimen Stoimenov QA Engineer SitefinityLeads, SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
Project Change Management
Project Closure 18-Jun-09. It’s All Over but the Partyin’ Not quite. You need to perform certain steps to formally close out your project. 1.Do a Lessons.
IS 214 Needs Assessment and Evaluation of Information Systems Managing Usability © Copyright 2001 Kevin McBride.
Week 7: Requirements validation Structured walkthroughs Why have walkthroughs When to have walkthroughs Who participates What procedures are helpful Thoughtless.
Residential Lending Property of Citigroup:Internal Document 0 Project Blacksmith Portal Server Investigation Prepared by: Technical Architecture & Strategy.
10.5 Report Performance The process of collecting and distributing performance information, including status reports, progress measurements and forecasts.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Stoimen Stoimenov QA Engineer QA Engineer SitefinityLeads,SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
Requirements Management
© 2006, Cognizant Technology Solutions. All Rights Reserved. The information contained herein is subject to change without notice. Automation – How to.
What is Business Analysis Planning & Monitoring?
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Project Management Process Overview
S/W Project Management
The information contained in this document is highly confidential and privileged. No part of this document may be copied or circulated without express.
COMPGZ07 Project Management Presentations Graham Collins, UCL
© VESP International Pty Limited To Contents Slide CLICK to advance slides/ bullet points within slides Integrated Master Planner An Overview.
Software Testing Lifecycle Practice
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Test Organization and Management
Best Practices By Gabriel Rodriguez
BSBPMG503A Manage Project Time Manage Project Time Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG503A.
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.
Conditions and Terms of Use
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Independent User Acceptance Test Process (IUAT)
Project Planning QMS Training.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
© Copyright 2011 John Wiley & Sons, Inc.
Project Tracking and Monitoring QMS Training. 2 Objective To track and monitor the progress of the project and take appropriate corrective actions to.
The Development of BPR Pertemuan 6 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
© 2014 Pearson Education, Inc., Upper Saddle River, NJ. All rights reserved. This material is protected by Copyright and written permission should be obtained.
Develop Project Charter
Chapter 5 Initiating and Planning Systems Development Projects Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph.
Test Manager’s Role Best Practice By Gabriel Rodriguez.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Project management Topic 7 Controls. What is a control? Decision making activities – Planning – Monitor progress – Compare achievement with plan – Detect.
Project Management Basics
eSpeed Electronic Trading Interface Message Flow Diagrams.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.1.
Report Performance Monitor & Control Risk Administer Procurement MONITORING & CONTROLLING PROCESS.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
Info-Tech Research Group1 Info-Tech Research Group, Inc. Is a global leader in providing IT research and advice. Info-Tech’s products and services combine.
Software Testing-STLC
Managing the Project Lifecycle
TechStambha PMP Certification Training
Project Management PTM721S
Project Management Processes
Strategies For Software Test Documentation
Reviewing Requirements and Capturing Questions
The Software Testing Life Cycle
Software Testing Lifecycle Practice
Testing Workshop.
Managing Project Work, Scope, Schedules, and Cost
Presentation transcript:

1 11-Jul-08 COPYRIGHT NOTICE Copyright © 2008 Polaris Software Lab Limited All rights reserved. These materials are confidential and proprietary to Polaris and no part of these materials should be reproduced, published in any form by any means, electronic or mechanical including photocopy or any information storage or retrieval system nor should the materials be disclosed to third parties without the express written authorization of Polaris Software Lab Limited. Software Testing Workshop Manual Testing

2 Presentation path Test Planning Test Preparation Test Closure Test Execution Test Process

3 Test planning Understand Project, Functional & Testing scope Define Functional & Testing scope Estimate efforts Prepare Test Plan Prove your understanding Obtain sign off

4 Test planning Understand Project, Functional & Testing scope Define Functional & Testing scope Estimate efforts Prepare Test Plan Prove your understanding Best Practices Have a formal query-tracker and raise all queries through this tracker (no question is a stupid question if not asked again & again) Treat the module owner as a Subject Matter Authority Write out-of-scope in enough detail so that every one understands clearly. Otherwise, potentially, you are dropping off your guards. Understand the existing Test processes & Tools If working application is all what you have to refer – prepare a document and use this for traceability. Risks Look for Requirement, Schedule, Effort, Test environment, Test Data related risks Metrics Turnaround time for the query-response Checkpoint: At module level, do number of queries correspond to the complexity, ambiguity and size of the functionality

5 Test planning Understand Project, Functional & Testing scope Define Functional & Testing scope Estimate efforts Prepare Test Plan Prove your understanding Best Practices Find out the defect density and factor it in effort estimate Assess and publish the productivity factors for key testing activities State the risks, issues and assumptions Invite all the stakeholders for reverse presentations Include functionality, testing scope, test process in the reverse presentation Risks Interfaces, Data feeds, Batch jobs, Test environment components

6 Test Preparation Prepare Test scenarios, Test cases & Traceability Detailed peer reviews Document Test Data requirements Obtain sign-off on the test artefacts Best Practices Traceability is not an after-thought Negative test cases to include functionally-negative conditions Peer reviews can bring out >95% of the defects in the artefacts Understand the process and efforts behind test data preparation Walkthrough the test cases for critical & new functionality Risks Gaps in test coverage Convoluted flow of test cases Metrics Productivity: Number of Test cases per person-day / Tester Quality of the deliverable: Number of defects / Unit volume Review efficiency: Defects leaked %

7 Test Execution Execute Test cases Log and Manage defects Publish Progress & Status Increase the rigor of testing as required Best Practices Encourage exploratory testing along with formal Test case based testing Log defects after a thorough re-test and ensure defect details are impersonal, detailed & persuasive Accurate progress & status reporting Keep track of the test cases (a) that are incorrect, (b) that cannot be executed Risks Test suspension, excessive re-testing, too many impeding defects, frequent builds, unstable test environment Metrics Productivity: Number of Test cases executed per person-day Actual defect density found Vs assumed

8 Test Closure Publish Test report & recommendation Conduct closure meeting Handover to the BAU team Best Practices Record the best practices & lessons learnt Risks Metrics Publish all the metrics: Schedule variance, Effort variance, Size variance, Test coverage, Defect density, Defect leakage, Process compliance Index

9 Points to ponder… Test Strategy Early detection of defects Defect prevention Limitations of manual testing

Thank You COPYRIGHT NOTICE Copyright © 2008 Polaris Software Lab Limited All rights reserved. These materials are confidential and proprietary to Polaris and no part of these materials should be reproduced, published in any form by any means, electronic or mechanical including photocopy or any information storage or retrieval system nor should the materials be disclosed to third parties without the express written authorization of Polaris Software Lab Limited. For further details Please contact: