search

robotpy / robotpy-wpilib

Moved to https://github.com/robotpy/mostrobotpy
https://robotpy.github.io
Other
169 stars 59 forks source link

Unit tests for WPILib #10

Closed virtuald closed 8 years ago

virtuald commented 9 years ago

Ideally, we should be able to get a really high rate of coverage on all of WPILib, so that we are assured that bugs that could crash the robot won't find their way in. Once this is all said and done, we can setup a travis-ci job to check all new pushes and pull requests.

Also, the existing magicmock unit tests should be converted to use the simulated hal.. maybe. See https://github.com/frc1418/robotpy-2015/issues/9.

There are already unit tests for some things, we can use the coverage tool to find things that haven't been tested yet.

As you start working on tests, add a note here.

computer-whisperer commented 9 years ago

It seems pretty clear that we won't be able to obtain a "really high rate" of coverage prior to kickoff.

Perhaps it makes sense to instead create an issue targeting 65% coverage for 2015.1.0, another targeting 75% for 2015.1.1, and so on.

virtuald commented 9 years ago

I think a better strategy is to identify the key systems that teams are probably going to use, and make sure those have a really high rate of coverage.