Question:
Walk me through your test plan. Give an example where a test case later found a bug in your code by things a teammate added later. (Or explain why you chose a test case specifically because you wanted to ensure that a teammate would know if they broke your code.)
Explanation:
- I noticed that my forward test broke when Ben changed the map to add holes in the wall, which essentially told us that the user can fall out of the map because of these holes.
- Another good one was creating a mass number of lights, and I was able to see that not
all the lights were working.
- This in turn allowed me to see in the pause menu that not all lights were activated, and I needed to change the pixel amount in rendering to allow more lights per object.
- I had a bunch of boundary tests, and I deliberately went in each direction to check whether someone changed the map, whether the boundaries worked properly, whether someone changed speeds and such.
- I actually noticed one of my tests going backwards somewhat broken with the bunker by going up on top of part of the bunker when it is not supposed to be able to do that.
- I also noticed that my forward test broke when Ben changed the map to add holes in the wall, which essentially told us that the user can fall out of the map because of these holes.
- I also noticed that my stress test took about 1000x more speed to break the game when we changed the map from a terrain to a blender-built map.
Test Plan: