Software Testing Checkoff Page

This is a master list of what needs to be tested for each block to be considered functional and ready to go. Some of these test components require the hardware to be working. Note that everyblock needs to run a memory check, that is ensure that if ran for a long period of time the memory usage doesn't creep upward because of memory leaks. This also ensures that the block is stable.

Note: If your name is here, you are comitted to finish that test. If you are unable to finish it because you don't know how to test, ASK someone, if you are unable because you are 'too busy' then work harder and get it done, or work it out for someone else to handle it. This is YOUR responsibility.

BlockComponentAssigned ToTest PassedNotes
WirelessTransmittergoskabx
WirelessRecievergoskab/Only processes one packet per loop, increase to prevent buffer filling
WirelessSerial Codegoskabx
WirelessFlow Controlgoskab
WirelessMem Checkgoskab
Process ManagerStartupgoskabx
Process ManagerMessage Passinggoskabx
Process ManagerRestart Dead Threadgoskab
Process ManagerQuitsgoskab
Process ManagerMem Checkgoskab
GPSSerial Recv'ing
GPSPosition Decoded
GPSResponds to position request message
GPSMem Check
CompassSerial Recv'ing
CompassDirection Decoded
CompassResponds to position request message
CompassMem Check
LoggerMakes a new log file each timegoskab
LoggerResponds to the log/debug messagegoskab
LoggerMem Checkgoskab
Motor ControlTalks to controllermortont
Motor ControlMotors on/offmortont
Motor ControlMotor speed controlmortont
Motor ControlMem Checkmortont
System MonitorGets values correctlymortont
System MonitorMem Checkmortont
GUISends proper messages to other blocksmortont
GUIMem Checkmortont
ArmMoves the arm
ArmDoesn't flood wireless
ArmFine Control of arm
ArmMem Check
USBPicks correct device each timemortont
USBResends USB packets if neededmortont

Note: for 'Test Passed', 'X' = 100% pass, / = minor fail, - = major fail, and nothing means untested.