Test Reporting Best Practices By Gabriel Rodriguez.

Slides:



Advertisements
Similar presentations
Performing Test Best Practices By Gabriel Rodriguez.
Advertisements

The Value of a Project Management Office Copyright: Kathy J. Lang, 2004.
By Guy Yariv Project Closure – Finally…
Defect Tracking and Management
Automated Software Testing: Test Execution and Review Amritha Muralidharan (axm16u)
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
Copyright © 2003 by The McGraw-Hill Companies, Inc. All rights reserved. Business and Administrative Communication SIXTH EDITION.
Final Report Document. Format Title Page Executive Summary Table of Contents Introduction Mission Statement Main PDS items Brief justification of the.
(c) 2007 Mauro Pezzè & Michal Young Ch 24, slide 1 Documenting Analysis and Test.
10.5 Report Performance The process of collecting and distributing performance information, including status reports, progress measurements and forecasts.
Tester’s Role in Software Development and Acquisition Best Practice By Gabriel Rodriguez.
Folder Structure Management Best Practice By Gabriel Rodriguez.
Best Practices By Gabriel Rodriguez
Progress Report: Working Points
Certified Software Tester V2.0 CSTE Certification Process.
Best Practices By Gabriel Rodriguez
Enterprise Product Implementation Process. Components of a Successful Implementation  A detailed Scope Document for customer review and signoff  Creation.
CPIS 357 Software Quality & Testing
Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.
S Q A.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
How To Build a Testing Project 1 Onyx Gabriel Rodriguez.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Boston University Project Management Association Website Development Group 3 Team3 CS632 Dr. Vijay Kanabar Team Members Mario Soto Emily Ziegler Kevin.
1 Hair, Babin, Money & Samouel, Essentials of Business Research, Wiley, REPORTING AND PRESENTING RESEARCH Chapter 12 Learning Objectives: 1.Convey.
Project Scope Management Project management Digital Media Department Unit Credit Value : 4 Essential Learning time : 120 hours.
Team Assignment 15 Team 04 Class K15T2. Agenda 1. Introduction 2. Measurement process 3. GQM 4. Strength Weakness of metrics.
Project Status Report Presenter Name Presentation Date.
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.
Software Testing. What is Testing? The process consisting of all life cycle activities, both static and dynamic, concerned with planning, preparation.
Monitoring and Evaluation Management of a Training Program.
Applied Software Project Management
Presenter Date Page Project manager The PROGRAM The Company Name 03/21/01 STOPLIGHT METRICS Stoplight Charts provide a means of communicating the status.
QA Methodology By Rajib Roy Independent Consultant Qcon.
Certified Software Tester CSTE Certification Process.
IFS310: Module 7 Business Requirements Statement Interpersonal Skills and Communications.
Monterrey Software Quality Assurance Association (MSQAA) MSQAA QAI Federation Chapter.
PRJ566 Project Planning & Management Software Architecture.
Test Manager’s Role Best Practice By Gabriel Rodriguez.
Monterrey QAI Federation Chapter Overview MSQAA Federation Chapter.
Module 5 Session 5.2 Visual 1 Module 5 Refining Objectives, Scope, and Other Project Parameters Session 5.2 Reviewing the PAR and refining key project.
Test status report Test status report is important to track the important project issues, accomplishments of the projects, pending work and milestone analysis(
Test Strategy Best Practices By Gabriel Rodriguez.
Monterrey Software Quality Assurance Association (MSQAA) Leadership and Planning.
Certified Software Tester Certification Training Proposal.
Final Year Project 1 (FYP 1) CHAPTER 1 : INTRODUCTION
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Parts of a Report. Feasibility Reports An outline of a feasibility report may look something like this: Project overview Market Budget Survey Results.
The Planning Phase Recognize the problem MIS steering committee 7. ManagerSystems analyst Define the problem Set system objectives Identify system constraints.
Chapter 4 Short Reports Copyright © 2012 Pearson Canada Inc., Toronto, Ontario.
Certified Software Tester How To Build a Testing Project, Part 2.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
PROGRESS REPORT LECTURE 7. What is a Progress Report? A Progress Report : documents the status of a project describes the various tasks that make up the.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
Information Technology Project Management, Seventh Edition.
1 Advanced Computer Programming Project Management: Basics Copyright © Texas Education Agency, 2013.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
Slide 1ICT 327 Management of IT ProjectsSemester 1, 2005 Topic 3 Executing & Controlling & Closing Projects.
Certified Software Tester How To Build a Testing Project, Part 1.
Project Report Format for Final Year Engineering Students.
Chapter 18 Formal Reports
Building Software Testers For Outsourcing
Welcome to our presentation
Team Project Review the background information and project teams on our course site Work with the engineers (4-5) and your PM team member(s) You have.
Topic of the final thesis
Identifying the Work to Be Done
Presentation transcript:

Test Reporting Best Practices By Gabriel Rodriguez

Copyright MSQAA Federation Chapter. Agenda Developing Test Status Reports Test Metrics Preparing Test Reports Q&A Reference

Copyright MSQAA Federation Chapter. Developing Test Reports

Copyright MSQAA Federation Chapter. Developing Test Status Reports The test status reports explained in these slides are generated by the Test Manager or Test Lead. Not all the projects require these status reports. These reports enables senior IT management to easily determine the status of the project, and can be issued as needed. There are two levels of project status reports: – Summary Status Report Provides a general view of all project components. It is used to determine which projects need immediate attention and which are on schedule with no apparent problems.

Copyright MSQAA Federation Chapter. Developing Test Status Reports The content of a summary status report is: – Report Date Information – Project information – Time Line Information – Legend Information The following slide depicts a summary status report.

Copyright MSQAA Federation Chapter. Developing Test Status Reports Summary Status Report Example

Copyright MSQAA Federation Chapter. Developing Test Status Reports The second level of project status report: – Project Status Report Shows detailed information about a specific project component, allowing the reader to see up-to-date information about – Schedules – Budgets – Project resources Each report is limited to one page so that only vital statistics are included.

Copyright MSQAA Federation Chapter. Developing Test Status Reports The content of a project status report is: – Vital Project Information – General Project Information – Project Activities Information – Essential Elements Information – Legend Information – Project Highlights Information The following slide depicts a project status report.

Copyright MSQAA Federation Chapter. Developing Test Status Reports Project Status Report Example

Copyright MSQAA Federation Chapter. Developing Test Status Reports There is one more important status report in testing, this status report is generated weekly depending on the project needs. This weekly status report shows the progress of the testing process in a systematic way.

Copyright MSQAA Federation Chapter. Developing Test Status Reports The content of the weekly status report is: – Product Name – Report No. – Week Ending – Tester(s) – Project Schedule – Progress and changes since last week – Urgent Items – Issue bin – To-do Tasks by Next Report

Copyright MSQAA Federation Chapter. Developing Test Status Reports Weekly Status Report Example

Copyright MSQAA Federation Chapter. Test Metrics

Copyright MSQAA Federation Chapter. Test Metric Metrics specific to testing includes data regarding testing, defect tracking, and software performance. Testers are responsible for reporting their test status at regular intervals. The following measurements generated during testing are applicable: – Total number of tests – Number of tests executed to date – Number of tests executed successfully to date

Copyright MSQAA Federation Chapter. Test Metric Examples of metrics and their uses are as follows: MetricUse of Metric User Participation Involvement Number of TestsExtent of testing Acceptance Criteria TestedExtent of testing Test CostResources consumed in testing Program Phase Testing Effectiveness Effectiveness of testing

Copyright MSQAA Federation Chapter. Preparing Test Reports

Copyright MSQAA Federation Chapter. Preparing Test Reports Test Reporting is the means of communicating the results of testing A final test report should be prepared at the conclusion of each test activity. Not all the projects follow this practice. The test reports are designed to document the results of testing as defined in the test plan. Without a well-developed test plan, it is difficult to develop a meaningful test report. A test report is designed to accomplished three objectives: – Define the scope of testing: Normally a brief recap of the test plan – Present the results of testing. – Draw conclusions and make recommendations based on those results.

Copyright MSQAA Federation Chapter. Preparing Test Reports The test report is divided in: – Scope of testing This section documents: – Feature to be tested All the areas tested need to be outlined – Features not to be tested – Results of Testing This section documents all the defects found during the test execution.

Copyright MSQAA Federation Chapter. Preparing Test Reports – What Works/What Does Not Work This section documents all the areas that are working properly as well as the areas that are not working – Recommendations This section documents any recommendation to mitigate any issues The following slide depicts a test report

Copyright MSQAA Federation Chapter. Preparing Test Reports Test Report Example

Copyright MSQAA Federation Chapter. Preparing Test Reports Test Report Part II Example

Copyright MSQAA Federation Chapter. Q&A Any questions…

Copyright MSQAA Federation Chapter. Reference CSTE Study Guide 2002 by QAI CSTE Study Guide 2006 by QAI

Copyright MSQAA Federation Chapter. Thank you…