Testing and Debugging Exercise

Notes and Exercises for Chapter 6 in TOSS

This chapter had some really useful information concerning bugs and how to handle and report them, especially since I'm currently interning at Hawkes Learning testing math software and reporting bugs, just as the chapter describes.

As for our Fortune Hunter involvement, we found all of two active bugs during the last class. The "oldest" bug (6.4 Exercise) happens to be the one we're planning to work on, so that works somewhat in our favor. I reproduced the bug (6.6 Exercise) while playing the game during last class (only in CS classes is that considered okay...). While their description of the bug is short, it's very much to the point, and does include the necessary information.

I also created an account at fedoraproject.org and applied to join the gitfortune_hunter group, assuming that's the right one. However, it looks like I can log in to the bug tracker Trac simply using my Google account, with full access to everything I might need for bugs. (6.5 Exercise)
I created a Sugar Labs user page here following the directions of Jon from the Math4 RIT team (as always, very helpful), and sent him a rather late email introducing myself, and more importantly, asking how to get Fortune Hunter's screen resolution down to a reasonable size for our laptops. It's very difficult to replicate bugs and simulate gameplay when the screen must be continuously moved to see the playing area and the accompanying messages.

The first bug (and oldest) involves the "scan" method during an attack actually dealing damage instead. Enemies are quickly defeated using this method. Its priority is "major," as it should be, high enough to be  of importance, but not the highest since it does not affect movement through the game (it actually helps it). But those sly fourth-graders might realize the bug's presence and use it to their advantage, defeating the game's purpose of teaching math.
The second bug ("newest") is getting stuck in the 3rd dungeon. I have no idea what "Dungeon 3" is, maybe because we haven't had enough experience with the game yet. I'm sure upon reaching that dungeon, I would suddenly become very aware of it if the bug is still in effect. Its "critical" priority is sound, considering getting stuck in a dungeon would ruin your progress and defeat the purpose of playing the game (since you can't win). (6.7 Exercise)