Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change name of "test" folder #24

Open
Mockapapella opened this issue Dec 13, 2022 · 1 comment
Open

Change name of "test" folder #24

Mockapapella opened this issue Dec 13, 2022 · 1 comment
Labels

Comments

@Mockapapella
Copy link
Member

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

@cfinn68916
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants