-
Notifications
You must be signed in to change notification settings - Fork 286
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 unit tests #496
Comments
Hi! |
Hey guys! I also saw the Google Summer of Code post and I'm also interested in contributing. Is there any other communication channels to discuss this? |
We are using Github discussion for now. |
Hello,
If there isnt' any preference set yet, PyTest could be a good option. Am I thinking in the right direction? |
Hey! I am Simrann, a postgraduate student in CS and AI from IIITD. I am quite intrigued by this idea and am looking forward to contribute to it as a GSoC 2023 student! |
Hi @skat00sh and @simrann20 , We are using Github discussion for now. Anyway, @skat00sh the segmentation can have pre-segmented files to verify that the methods are working correctly. @simrann20 , please follow the instructions: https://github.com/invesalius/gsoc/blob/main/gsoc_application.md ATTENTION: New questions about GSoc 2023 most be asked in discussion: https://github.com/invesalius/invesalius3/discussions |
Use tools like unittest or pytest to add tests to InVesalius code. That way, when adding new features or bug fixes, you can verify that no previous code has been affected. Also run this code when committing and sending pull requests on Github.
https://realpython.com/python-testing/
The text was updated successfully, but these errors were encountered: