Lab 10: Bug bash

About bug bashes (5 min)

In Discord > Everyone

The goal of a bug bash is to break an application in as many different ways as possible. Keep careful attention to exactly how you break it, so that you can help the authors to know what they need to fix. This is your last chance to get free testing before you deploy and are graded on functional correctness.

Note: Since we moved the deadline for HW6, this may not be your *last* chance to get free testing per se, but it will certainly be the last in-class, organized opportunity for feedback. Make good use of it! The more bugs you find today and fix before next week's deployment, the fewer bugs Amy & Alannah will find (and deduct points for) when grading your final projects.

A few tips:

• The tester should think aloud and narrate their thought process as they're using the website.
• The observer should take notes and share them with their team after the bug bash.
• Use the entire 15 minutes! Testers should do their best to break the website in as many ways as possible. If you feel like you're running out of things to test, look to the requirements list and verification plan for the project (which should be accessible on the team's repo).
• The tester should report bugs on the observer's repo using the GitHub issues feature.

Try a classmate's project (15 min)

In Discord > Random Pairs

1. Choose a random pair channel. 
2. Choose which one of you will be the tester and who will be the observer.
3. The tester should ask the observer to show them how to setup and use the observer's project, and bring up the tester's repository.
4. The observer should run through the main project scenario with your partner.
5. While the observer silently watches, try using your partner's project without any guidance or help. Click and tap on anything you want.
6. If the application behaves incorrectly (in the tester's opinion) or does not do what you (the tester) expected, write an issue on your partner's repo (find team repos here Links to an external site.). Include the description of the bug and reproduction steps! Then explain the problem to your partner. Then, look for more bugs!

Swap roles and repeat (15 min)

Repeat the process above with you and your partner switching roles.

Submit (5 min)

For credit, submit a short summary of the project you tested and bugs you found. (If you didn't find any bugs, you probably were not looking hard enough.)