Testing: Being on point.

During the past week, I had MikeTerry (please see previous posting) doing tests to make sure he knew what he was suppose to do. MikeTerry went thru six tests case, which he successfully passed with flying colors. Here are the tests and results of this past week testing phase.

Acceptance tests are to be making sure that MikeTerry can consistently beat one or more of the sample robots that I have been using in previous assignments.

Test 1- MikeTerry VS. Fire: MikeTerry constantly won against this robot.

Test 2 - MikeTerry VS. Crazy: MikeTerry constantly won against this robot.

Behavioral tests make sure that MikeTerry that his movements and strategies are on point.

Test 3 - Clockwise path: As part of MikeTerry’s strategy, he needs to move clockwise; by doing this test I was able to see that MikeTerry always used a clockwise path without making any changes in his coding.

Test 4 - All 4 corners: One of the other strategies is to move to all four corners, which MikeTerry did successfully without any major changes in his coding.

Test 5 - Out of the center: I wanted for MikeTerry to stay within the outter wall radius and he did it consistently.

Unit test verifies that MikeTerry ‘s individual methods calculate the correct output values given various input values.

Test 6 - Firing: MikeTerry tested that his firing power was consistent. He needed to fire his enemy at the power of 2 or less when the enemy is in the range greater then 200 pixel.

During the testing phase, I discovered that my coding style didn't require alot of changes for testing. Here is MikeTerry tests and results.

Coach's last words: It is easier to code with testing in mind versus coding like a mad programmer and finding bugs everywhere to drive you to be even more mad.