Tracking and Squashing Bugs Coder To Developer from Mike Gunderloy Chapter 9 Instructor : Dr. James Fawcett Presented by Charlie Chung chungcharlie@yahoo. com
Agenda n Risk Management n QA & Testing n Bug Tracking Tools
Risk Management n Risk Assessment n What things might go wrong badly? n Cost, schedule or quality? n Risk Control n Take the correct action to handle it? n Maintaining the Top Five Risk List n Bug Triage
Risk Assessment ideas… n I discover a requirement that I can not figure out how n n n 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 n Get things done!
Maintaining the T 5 Risk List n 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 n Prioritizing bugs based on their seriousness and deciding what to do about each one n Fix what really need to be fixed By Design n Duplicate n Postponed n Not Reproducible n Won’t fixed n Reassigned n Fixed n
Bug Tracking Work Flow n A tester find a bug and report it n The bug is assigned to a manager for initial triage n The manager resolve it or assign to a developer n Resolved bug returned to a tester n The tester either closes the bug or reopen it with additional information or comments which start step 2 again
QA & Testing n Type of Software Test n QA for Lone Wolf n Build a Test Network
Type of Software Testing n Unit testing Chapter 5, by function or component n Functional testing Walk through with specifications? n Conformance testing Match industry spec? ex. XML format match W 3 C XML. . n Compatibility testing Different OS, HW… n Performance testing Check the application performance is acceptable to user
Type of Software Testing n Stress testing How app fail when subjected to excessive stress n Regression testing Test that were passed by previous build of the software n Smoke testing Running “quick and dirty” tests that exercises major features. . Have to wait till next build if failed n Black-box testing Focusing on external interfaces, (most are QA jobs) n White-box testing Internal behavior of component is tested , just like unit testing
QA for the lone wolf Most company have 1/3 manager & architect; 1/3 develops; 1/3 testers n Use unit test n Create a list of critical requirements n Set code aside for a few days before performing n n n 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 n Some advice from the author n Buy preassembled machine, name brand, serious development hardware n Skip tapes n Store data separately n Keep drive image n Use virtual machines n Use KVM switch ( many company do this) n Get your own domain n Use a firewall n Set aside test machine & use mix of machines n Set aside a build machines
Bug Tracking Tools n Choosing a bug Tracking Tool n Using a bug tracking tool
Choosing a bug Tracking Tool n n n 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 n What happen n What the tester thinks should happen instead n Steps to reproduces the problem
Bug Tracking Systems n Fog Creek Corp. – Fog Bugs n Managing software projects designed by software development guru Joel Spolsky n http: //fogcreek. com/Fog. Bugz/index. html n Project Center – Bug Tracker n Supports the definition, and eventually the closure of bugs encountered in development. n http: //128. 230. 209. 100/Project. Center/Web. Pages/featur es. aspx n Problem Tracker Corp. – Problem Tracker n http: //demo. netresultscorp. com/pt 4_demo 1/ptloginok. a sp n http: //demo. netresultscorp. com/pt 4_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!
Скачать презентацию Tracking and Squashing Bugs Coder To Developer from
708c456a88620ac209251136cf1b1dc6.ppt