add some basic unit tests

[flynneva]

Unit testing software will allow you to:

• confirm software is doing what you expect
• confirm old code still works as new code is added (adding something new here doesnt break something over there)
• if code can pass the test, you can delete unused or unnecessary code
• automatically run tests using Github Actions when new code is added

A lot of times people in the software industry write the tests first, then they write the actual software. This reduces bloat in code since you only write code to accomplish some task.

FIRST robotics has a page about unit testing that seems like a good place to start.

• write a basic unit test to test some of the code in this repo

[An3Dev]

I created a very simple unit test for the drive train subsystem and it looks like it's working. When I build the project, visual studio code lets me know that the unit test passed. The test I wrote just checks that the motors are not spinning when the robot is enabled.

Now I need to add more tests to make sure everything works as expected.
Here is a list of tests we should add:

• Test that the DriveTrainSubsystem methods correctly spin its motors.
• Test that the ShootingSubsystem methods correctly spin its motors.
• Test that ArcadeDriveCommand correctly controls the drive train.
• Test that ShootCommand correctly controls the motors.
• Test that AutoDriveCommand will turn to the left if the object it's tracking is to the left, and that it will turn to the right if the object it's tracking is to the right. If it's not tracking anything, it should spin.
• Test that the bull mode does the right thing in every time period.

I'm probably missing something, so feel free to add more tests.

[An3Dev]

I'm also going to make GIthub run the unit tests using Github Actions. I'm gonna follow this article:
https://medium.com/@dev.soni04/github-action-for-unit-testing-57faefc9633

• Create github action that runs the unit tests on pull request or push

[flynneva]

Create github action that runs the unit tests on pull request or push

@An3Dev I think tests were already being ran in the normal CI job but I could be wrong. It might not be worth it to separate out the tests into its own pipeline...but maybe it is? Not sure.

[An3Dev]

Oh, you're right. I didn't notice that. I'll keep the tests on the normal CI job.