INTRODUCTION 1. QA Department business systems 2. All the bug reports and all the bug tracking systems are very similar.

Slides:



Advertisements
Similar presentations
INTRODUCTION 1. Business systems and QA Department business systems 2. All the bug reports and all the bug tracking systems are very similar.
Advertisements

Testing and Quality Assurance
Defect Tracking and Management
Chapter 4 Quality Assurance in Context
Software Construction
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
Project Life Cycle SDLC (Software Development Life Cycle) WDLC (Web Development Life Cycle)
CMPE 287 Software Quality and Testing Lab Test Problem and Report Tools Element tool.
Software Testing and Quality Assurance: Introduction and Terminology
Project Management and MS Project. The project management triangle: Time Resources Scope.
PowerPoint Presentation for IS-207 Copyright 2006 © Michael W. Schaffer. All rights reserved. Slide 1 System Analysis & Design Shrink-wrap Tools and Techniques.
Software Testing Prasad G.
Chapter 25 – Configuration Management 1Chapter 25 Configuration management.
© 2006, Cognizant Technology Solutions. All Rights Reserved. The information contained herein is subject to change without notice. Automation – How to.
Michael Solomon Tugboat Software Managing the Software Development Process.
Data Structures and Programming.  John Edgar2.
Test Design Techniques
Selecting a Tool 1 When to start evaluating: Current method is not effective Can solve an immediate problem/challenge Can increase productivity and deliverables.
A Bug Tracking Story Danny R. Faught Tejas Software Consulting ASEE Software Engineering Process Improvement Workshop 2002.
How To Apply Quality Management
Software Development Life Cycle Decisions Project Management Disciplines Stacey Shearn September 8, 2005.
Software Testing Online Training DEFECT TRACKING & CORRECTION
DMS Training 2017年4月22日(土) Instructor:
Software Testing Life Cycle
Software testing basic. Main contents  Why is testing necessary?  What is testing?  Test Design techniques  Test level  Test type  How to write.
1 CEN 4072 Software Testing PPT2: Tracking the problem.
Tracking The Problem  By Aaron Jackson. What’s a Problem?  A suspicious or unwanted behavior in a program  Not all problems are errors as some perceived.
Lean6σ GOLD Urgent Support A Reduction in Urgent Customer Requests Resolution Cycle Time Charles Hollingsworth.
1 SEG4912 University of Ottawa by Jason Kealey Software Engineering Capstone Project Tools and Technologies.
Surveys (Evaluations) At Oxford Dr Adam Marshall Oxford University Computing Services weblearn.ox.ac.uk.
Requirements and Estimation Process From a CMM Level 5 Organization Alan Prosser.
Monitor & Control Risks 1 MEC-4. What is Monitoring & Controlling Risks? 2 » Monitoring & Controlling Risks is the process of: implementing Risk Response.
QUALITY ASSURANCE PRACTICES. Quality Plan Prepared and approved at the beginning of project Soft filing system approach followed. Filing location – –
QA and Testing. QA Activity Processes monitoring Standards compliance monitoring Software testing Infrastructure testing Documentation testing Usability.
CMPE 287/196H Software Quality and Testing Lab Test Problem and Report Tools Instructor: Jerry Gao Ph.D. Student Assistant: Yi-Tien Ian Lin San Jose State.
Software Maintenance Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
Testing, Testing & Testing - By M.D.ACHARYA QA doesn't make software but makes it better.
Debugging of # P. Hristov 04/03/2013. Introduction Difficult problem – The behavior is “random” and depends on the “history” – The debugger doesn’t.
CSC 4700 Software Engineering
Test status report Test status report is important to track the important project issues, accomplishments of the projects, pending work and milestone analysis(
Monitor & Control Risks 1 MEC-4. What is Monitoring & Controlling Risks? 2 » Monitoring & Controlling Risks is the process of: implementing Risk Response.
W. Pokorski - EP/SFT Simulation Project1 Generator Services Subproject Witek Pokorski
Eriq Muhammad Adams J | 03 |QA and Testing (1) Eriq Muhammad Adams J |
Software Quality Assurance and Testing Fazal Rehman Shamil.
October 4-7, 2004 Los Angeles, CA The importance of Testing Tools and Quality Assurance Pathangi Janardhanan HCL Technologies
Testing and Debugging. Testing Fundamentals  Test as you develop Easier to find bugs early rather than later Prototyping helps identify problems early.
Designed by : Aarthi Sneha 1 Software Testing NTC Infotec.
Introduction to Bugzilla. May 12, 2011 What is Bugzilla? Bugzilla is a defect- or issue-tracking system Allows individual or groups of developers effectively.
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.
Reporting Bugs Why all bugs aren't always fixed What you can do to make it more likely that the bugs you find are fixed What techniques you can use to.
Chapter 8: Maintenance and Software Evolution Ronald J. Leach Copyright Ronald J. Leach, 1997, 2009, 2014,
ERA Project Team Meeting Project Management Plan April 23, 2002.
Presenter(s) Name(s) Department May 18, 2010 Title of Presentation.
Software Testing-STLC
Introduction to CAST Technical Support
Progile Automated Verification Engineer • PAVE •
Software Testing Lab 1.
Tracking and Squashing Bugs
Quality Assurance Week 5 Winter quarter 02/04/02 SOS
Improving the Defect Life Cycle Management Process
Testing for patch certification
Using OzART to Test Websites in Higher Education: A George Mason U
Regression testing is a type of software testing that seeks to uncover new software bugs, or regressions, in existing functional and non-functional areas.
Strategies For Software Test Documentation
Software Quality Engineering
Introduction to CAST Technical Support
© University of Liverpool
Finding and Managing Bugs CSE 403 Lecture 23
Using OzART to Test Websites in Higher Education: A George Mason U
LESSON 01 Hands-on Training Execution
Presentation transcript:

INTRODUCTION 1. QA Department business systems 2. All the bug reports and all the bug tracking systems are very similar

BUG REPORTS Why writing bug reports? Getting the bug fixed Getting the bug fixed What makes a good bug report? How to reproduce the bug How to reproduce the bug Analyze the problem to minimize number of steps to reproduce it Analyze the problem to minimize number of steps to reproduce it Complete, easy to understand, non-conflicting Complete, easy to understand, non-conflicting

BUG REPORTS When should you write a bug report? Immediately upon identifying the bug Immediately upon identifying the bug Describe Content of the bug report? Short Description/Synopsis Short Description/Synopsis Steps to reproduce Steps to reproduce Severity Severity Priority Priority Status Status Many more – see the bug reporting form Many more – see the bug reporting form

BUG REPORTS Name 4 levels of the seriousness of the problem (Severity)? Critical/Fatal (crash, data corruption, hang) Critical/Fatal (crash, data corruption, hang) Serious (workaround) Serious (workaround) Minor Minor Suggestion/Enhancement Suggestion/Enhancement

BUG REPORTS Name 3 levels of priority? High High Medium Medium Low Low Who can assign/change severity or priority in a bug report? Tester assigns severity Tester assigns severity Development/Project Manager assigns Priority Development/Project Manager assigns Priority

BUG REPORTS Why looking for most serious consequences of the bug? To assign higher severity (get higher priority) To assign higher severity (get higher priority) What is reproducible bug? (discussion) What is reproducible bug? (discussion)

BUG REPORTS Why should tester look for simplest and most general conditions under which bug will be easily reproducible? Look for more than one path to a same problem. Look for more than one path to a same problem. The easier to understand – the better chances to have it fixed The easier to understand – the better chances to have it fixed The faster the fix - the better the chance it will be done The faster the fix - the better the chance it will be done

BUG REPORTS Things to remember: Look for configuration dependence Look for configuration dependence Reproduce the bug before it is reported Reproduce the bug before it is reported Is that first-time-only bug ? Is that first-time-only bug ?

BUG TRACKING DATABASE Why do we need Bug Tracking Database? Accountability Accountability Communication tool Communication tool Monitoring individual performance Monitoring individual performance What is a prime objective of a Bug Tracking Database? To get the bugs fixed To get the bugs fixed

BUG TRACKING DATABASE Describe Bug's life cycle? Bug gets reported Bug gets reported It goes to Development/Project Manager to get “Assigned To” and “Priority” It goes to Development/Project Manager to get “Assigned To” and “Priority” Developer sees the report, fixes the bug, marks it as “Fixed” Developer sees the report, fixes the bug, marks it as “Fixed” It goes to Tester for verification of the fix It goes to Tester for verification of the fix

BUG TRACKING DATABASE What happens if reported bug cannot be reproduced by a developer? Retest on your system Retest on your system Retest on a few other systems Retest on a few other systems Compare the environments Compare the environments Reproduce on developer’s system Reproduce on developer’s system Developer debugs on QA system Developer debugs on QA system

BUG TRACKING DATABASE What happens next after the bug is (allegedly) fixed? Validate the fix Validate the fix Do regression testing Do regression testing What does that mean Deferred Bug? Who can make a decision to defer a bug? Discussion Discussion