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

Move unit tests in their specific module based on their goals #197

Open
geryxyz opened this issue Jun 23, 2021 · 1 comment
Open

Move unit tests in their specific module based on their goals #197

geryxyz opened this issue Jun 23, 2021 · 1 comment

Comments

@geryxyz
Copy link
Collaborator

geryxyz commented Jun 23, 2021

As far as I know, there are two kinds of test cases in the codebase. The classical unit tests and the ones used to provide a sample usage for the features. This latest one show some similarity to automatic end-user or integration tests. Currently, these are mixed into the same module (into the same py file). My suggestion is to move these later ones into their dedicated module and specify their development processes' roles more clearly.

@copernico
Copy link
Contributor

I absolutely agree, we should distinguish them. The integration tests could be moved to files named test_integration_******.py

@copernico copernico changed the title Move unit tests in there specific module based on their goals Move unit tests in their specific module based on their goals Oct 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants