Refer to Figure 4.26.
What isolation steps should you perform?
In addition to missing isolation, there are at least three improvements needed to bring this report in line with the 10-step process outlined earlier. Identify them.
The calculator is exhibiting this behavior in the binary, octal, and hexadecimal modes because it apparently works in an integer-only fashion in these modes. (Note that division causes truncation of the remainder, too.) If the decimal key (".") were properly grayed out, would that be a sufficient indication of an integer-only mode? Explain your reasoning.
What is the appropriate severity and priority for this bug?
If you have two or more people available, have a bug triage discussion about this bug.
Using either exploratory testing or the test cases you created in Chapter 3, find a functionality bug in an application or utility running on your PC or workstation. (Sadly, this will not be hard.)
Write a bug report following the 10-step process outlined in this chapter.
Have a colleague or fellow student review your bug report. How many changes did you make based on the review?
Repeat steps 2.a and 2.b for a user interface or usability bug.
Figure 4.27 shows a fancy workflow (life cycle) from an automated bug tracking tool. A well-suited bug reporting workflow fits into the organizational context in which the project occurs, and therefore looking at the workflow can tell you a lot about the organization's team structure (i.e., org chart) or at least ...