English | MP4 | AVC 1280×720 | AAC 48KHz 2ch | 0h 58m | 121 MB
Bug writing and management are critical to software development. Quality managers, developers, and everyone else associated with a product’s launch are deeply invested in the process. Bad bugs—those with inaccurate or unclear information—lead to a lot of wasted time and effort. However, when bugs are well written and managed properly, the project runs smoother and faster. This course teaches best practices for identifying, writing, and tracking bugs discovered during software testing. Learn how to recognize, classify, and document issues, as well as monitor, maintain, and eventually close reported bugs in a tracking system like Jira. Instructor Mike Fine—a senior test manager with over 25 years of experience—provides a concise and practical guide to bug reporting, so that the information you submit is meaningful and useful to developers.
Topics include:
- Identifying bugs
- Writing effective bugs
- Avoiding common bug reporting issues
- Using a bug tracking system
- Closing and archiving bugs
Table of Contents
1 Understand bugs and their importance
2 Base knowledge
3 Identifying bugs
4 Elements of bug composition
5 What makes a good bug
6 Common bug reporting issues
7 Traditional bug forms and responses
8 Bugs vs. suggestions
9 Using a bug tracking system
10 The life of bugs
11 Bug history and management
12 Regression and update testing
13 Closing bugs
14 Archiving old bugs
15 The importance of bugs
16 Next steps
Resolve the captcha to access the links!