-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add tests to the project #9
Comments
If the codebase is to be tested, it must first be testable. For the codebase to be testable, we must refactor as per issue #4. |
Sounds as it would be a good idea to refactor then. |
It’s already started it just needs to be merged into dev |
Should we add a separate vs project for the test classes? |
Isn't that the way it's usually done? As far as I can tell |
Yes but I believe it's also possible to do it in the same project. Just curious if you guys wanted the extra overhead of a second project. Alternatively, I think we could have a testing branch so that only the people who want to run the tests have to pull them. |
Testing branch is a fair point, but it will require more synchronisation. I don't think the second project adds any significant overhead - in fact, it prevents us from compiling test code into the release build. |
I would also go with a second project for tests |
Alright let's go with the second project then. |
Maybe some tests would be a good idea, because then you can see if your changes break anything or have other unexpected effects.
The text was updated successfully, but these errors were encountered: