You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Normally in software projects, the "test(s)" folder is where all your Unit Tests are, not experimental code. "Unit Tests" are functions that assert various states about your code. If you have code that activates a motor when you press a button, it's good to have a separate piece of code that verifies that functionality. If the behavior of that function is modified in the future, say by changing what button needs to be pressed to activate the motor, the test will catch that and will fail as a result. This can be used in combination with git hooks to prevent code from being committed to a branch unless all tests pass.
I suggest that we split it into "experiments" and "archive". "Experiments" would be for stuff like the led test code. "Archive" would be for stuff that should have never been in tests, like DEATH STARE(++) and nt-drive.
Normally in software projects, the "test(s)" folder is where all your Unit Tests are, not experimental code. "Unit Tests" are functions that assert various states about your code. If you have code that activates a motor when you press a button, it's good to have a separate piece of code that verifies that functionality. If the behavior of that function is modified in the future, say by changing what button needs to be pressed to activate the motor, the test will catch that and will fail as a result. This can be used in combination with git hooks to prevent code from being committed to a branch unless all tests pass.
I would suggest "experimental" or "sandbox" for the folder names. More information here: https://docs.wpilib.org/en/stable/docs/software/wpilib-tools/robot-simulation/unit-testing.html
The text was updated successfully, but these errors were encountered: