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
The number of tests is increasing to avoid being lost in the testing some parts of the code. I think it's important to choose a good organisation of tests and correct names.
The general idea is to create a file test_....py for each python file. Each test has a name starting with 'test_'. If an aspect requires multiple tests to be tested, these tests are grouped into a class.
In addition to it, we need to one-line docstring to limit the tests to a specific aspect and to document the tests.
The text was updated successfully, but these errors were encountered:
The number of tests is increasing to avoid being lost in the testing some parts of the code. I think it's important to choose a good organisation of tests and correct names.
I propose to follow the name suggestion of numpy:
https://numpy.org/doc/stable/reference/testing.html#writing-your-own-tests
The general idea is to create a file test_....py for each python file. Each test has a name starting with 'test_'. If an aspect requires multiple tests to be tested, these tests are grouped into a class.
In addition to it, we need to one-line docstring to limit the tests to a specific aspect and to document the tests.
The text was updated successfully, but these errors were encountered: