Tracking and Squashing Bugs

Slides:



Advertisements
Similar presentations
Object Oriented Analysis And Design-IT0207 iiI Semester
Advertisements

Test process essentials Riitta Viitamäki,
Testing and Quality Assurance
1 Software Engineering Lecture 11 Software Testing.
Abirami Poonkundran 2/22/10.  Goal  Introduction  Testing Methods  Testing Scope  My Focus  Current Progress  Explanation of Tools  Things to.
Mike Azocar Sr. Developer Technical Specialist Microsoft Corporation
Software Testing. Overview Definition of Software Testing Problems with Testing Benefits of Testing Effective Methods for Testing.
Test Environments Arun Murugan – u Rohan Ahluwalia – u Shuchi Gauri – u
©Brooks/Cole, 2003 Chapter 7 Operating Systems Dr. Barnawi.
Agile Testing with Testing Anywhere The road to automation need not be long.
CS4723 Software Validation and Quality Assurance Lecture 9 Bug Report Management.
Terms: Test (Case) vs. Test Suite
Estimation Wrap-up CSE 403, Spring 2008, Alverson Spolsky.
Project Proposal: Academic Job Market and Application Tracker Website Project designed by: Cengiz Gunay Client: Cengiz Gunay Audience: PhD candidates and.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 DAN FARRAR SQL ANYWHERE ENGINEERING JUNE 7, 2010 SCHEMA-DRIVEN EXPERIMENT MANAGEMENT DECLARATIVE TESTING WITH “DEXTERITY”
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Module CC3002 Post Implementation Issues Lecture for Week 6 AY 2013 Spring.
14 Publishing a Web Site Section 14.1 Identify the technical needs of a Web server Evaluate Web hosts Compare and contrast internal and external Web hosting.
Call For Contributions TAO 2.5. Introduction 2 How to Contribute ? What is the process ? How much effort ? What type of competencies are required ? How.
Painless Bug Tracking Michael Tsai 2011/9/30. Reference  html 2.
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.
Pass SOX security audits and Improve XA security CISTECH Security Solutions Belinda Daub, Senior Consultant Technical Services
By Touseef Tahir Software Testing Basics. Today's Agenda Software Quality assurance Software Testing Software Test cases Software Test Plans Software.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
Why use JIRA?.
QUALITY ASSURANCE PRACTICES. Quality Plan Prepared and approved at the beginning of project Soft filing system approach followed. Filing location – –
TM Copyright © 2009 NMQA Ltd. Behaviour Driven Testing with.
22-January-2003cse FunctionalSpecs © 2003 University of Washington1 Functional Specs CSE 403, Winter 2003 Software Engineering
1 Legacy Code From Feathers, Ch 2 Steve Chenoweth, RHIT Right – Your basic Legacy, from Subaru, starting at $ 20,295, 24 city, 32 highway.
Deadlock Detection and Recovery
Software Quality Assurance and Testing Fazal Rehman Shamil.
ITEC 370 Lecture 18 Testing. Review Questions? Design document due W –System can be implemented just by following it Implementation –Methods (prototype,
Testing and Evolution CSCI 201L Jeffrey Miller, Ph.D. HTTP :// WWW - SCF. USC. EDU /~ CSCI 201 USC CSCI 201L.
In today’s lesson we will be looking at: what we mean by the software development lifecycle the phases in the lifecycle We will focus particularly on testing:
Applied Software Project Management SOFTWARE TESTING Applied Software Project Management 1.
Items to consider before automating an application
Development Environment
SaralTA Batch-07 Software Testing Presented By - Chittaranjan M.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
CompSci 230 Software Construction
Integration Testing.
Security Testing Methods
Project Center Use Cases Revision 2
Project Center Use Cases
Segments Basic Uses: slides minutes
Recall The Team Skills Analyzing the Problem (with 5 steps)
Key Ideas from day 1 slides
Project Center Use Cases
Software Quality Assurance
Project Center Use Cases Revision 3
Project Center Use Cases Revision 3
Applied Software Implementation & Testing
Peer Reviews Tips for the author.
Introduction to Software Testing
© University of Liverpool
Sharing the good, the bad, the ugly & What can we do about it?
Finding and Managing Bugs CSE 403 Lecture 23
BlackBoard 5 A Definitive e-Learning Software Platform Ozgur Balsoy,
Examining the Specification
CS240: Advanced Programming Concepts
What is Software Testing?
Just-In-Time Testing Robert Sabourin President AmiBug.Com, Inc.
BIT 285: (Web) Application Programming
LESSON 01 Hands-on Training Execution
CS5123 Software Validation and Quality Assurance
Automated test.
that focus first on areas of risk.
Preparation for Final exam
Presentation transcript:

Tracking and Squashing Bugs Coder To Developer from Mike Gunderloy Chapter 9 Instructor : Dr.James Fawcett Presented by Charlie Chung chungcharlie@yahoo.com

Agenda Risk Management QA & Testing Bug Tracking Tools

Risk Management Risk Assessment Risk Control What things might go wrong badly? Cost, schedule or quality? Risk Control Take the correct action to handle it? Maintaining the Top Five Risk List Bug Triage

Risk Assessment ideas… I discover a requirement that I can not figure out how to implement I don’t have time to finish the code, I have too many other projects to do I can’t finish all the planned features in the time allowed I lose the program’s source code due to a hardware issue My code quality is too low to share without embarrassment ….

Risk Assessment

Risk Control Get things done!

Maintaining the T5 Risk List The goal of the Top 5 risk list is to give you an idea where you can immediately and easy review the most serious threats to your project ….

Bug Triage Prioritizing bugs based on their seriousness and deciding what to do about each one Fix what really need to be fixed By Design Duplicate Postponed Not Reproducible Won’t fixed Reassigned Fixed

Bug Tracking Work Flow A tester find a bug and report it The bug is assigned to a manager for initial triage The manager resolve it or assign to a developer Resolved bug returned to a tester The tester either closes the bug or reopen it with additional information or comments which start step 2 again

QA & Testing Type of Software Test QA for Lone Wolf Build a Test Network

Type of Software Testing Unit testing Chapter 5, by function or component Functional testing Walk through with specifications? Conformance testing Match industry spec? ex. XML format match W3C XML.. Compatibility testing Different OS, HW… Performance testing Check the application performance is acceptable to user

Type of Software Testing Stress testing How app fail when subjected to excessive stress Regression testing Test that were passed by previous build of the software Smoke testing Running “quick and dirty” tests that exercises major features .. Have to wait till next build if failed Black-box testing Focusing on external interfaces, (most are QA jobs) White-box testing Internal behavior of component is tested , just like unit testing

QA for the lone wolf Use unit test Most company have 1/3 manager & architect; 1/3 develops; 1/3 testers Use unit test Create a list of critical requirements Set code aside for a few days before performing functional tests Get someone don’t know your app to test Keep a written list of requirements Use bug tracking system Be sure to check absurd input If you think something might go wrong while coding, enter it as a bug in you bug tracking system. This will help you to remember Treating bugs as learning experience, not a threat to your coding skills

Building a Test Network Some advice from the author Buy preassembled machine, name brand, serious development hardware Skip tapes Store data separately Keep drive image Use virtual machines Use KVM switch ( many company do this) Get your own domain Use a firewall Set aside test machine & use mix of machines Set aside a build machines

Bug Tracking Tools Choosing a bug Tracking Tool Using a bug tracking tool

Choosing a bug Tracking Tool Cost (tool cost / license ..)? Multiple platform needs? / web based or other interfaces Send notification, distinguish or feature request? Integrate with other management tool? Where does the tool store information? What do you NEED from here?

Using a bug tracking tool What happen What the tester thinks should happen instead Steps to reproduces the problem

Bug Tracking Systems Fog Creek Corp. – Fog Bugs Managing software projects designed by software development guru Joel Spolsky http://fogcreek.com/FogBugz/index.html Project Center – Bug Tracker Supports the definition, and eventually the closure of bugs encountered in development. http://128.230.209.100/ProjectCenter/WebPages/features.aspx Problem Tracker Corp. – Problem Tracker http://demo.netresultscorp.com/pt4_demo1/ptloginok.asp http://demo.netresultscorp.com/pt4_demo.html

Example: New Case *Using Fog Bugz

Example: custom case *Using Fog Bugz

Example: List view *Using Fog Bugz

Example: Notification *Using Fog Bugz

Example: Search *Using Fog Bugz

Thank you!