Structure/Organize tests section #100
Assignees
Labels
Comments
Merged
lu-pl
added a commit
that referenced
this issue
Oct 29, 2024
This branch implements a restructuring of the test suite. Rationale: Over-modularization of test parameter definitions clutters up the test suite and leads to lengthy/repetitive import statements. For now, the structure of the test suite should (loosely) mirror the rdfproxy package structure, e.g. sparql_utils should be tested in tests_sparql_utils etc. Test types (unit, integration, end2end, etc) should be indicated in docstrings or a separate tests README. Closes #100
|
Consider separating the test suite into unit, integration and end2end tests. What would be the exact distinction between integration and end2end testing for |
lu-pl
added a commit
that referenced
this issue
Nov 5, 2024
This branch implements a restructuring of the test suite. Rationale: Over-modularization of test parameter definitions clutters up the test suite and leads to lengthy/repetitive import statements. For now, the structure of the test suite should only differentiate 1. unit tests and 2. all other tests. Additional test categories may be introduced at a later point. The test category should be indiciated in the test module doc string. Closes #100
lu-pl
added a commit
that referenced
this issue
Nov 5, 2024
This branch implements a restructuring of the test suite. Rationale: Over-modularization of test parameter definitions clutters up the test suite and leads to lengthy/repetitive import statements. For now, the structure of the test suite should only differentiate 1. unit tests and 2. all other tests. Additional test categories may be introduced at a later point. The test category should be indicated in the test module doc string. Closes #100
lu-pl
added a commit
that referenced
this issue
Nov 6, 2024
This branch implements a restructuring of the test suite. Rationale: Over-modularization of test parameter definitions clutters up the test suite and leads to lengthy/repetitive import statements. For now, the structure of the test suite should only differentiate 1. unit tests and 2. all other tests. Additional test categories may be introduced at a later point. The test category should be indicated in the test module doc string. Closes #100
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The tests section needs urgent restructuring/cleaning up.
Currently the tests folder structure (and e.g. also
tests.utils._types) is tightly coupled withinstantiate_model_from_bindingstests.The text was updated successfully, but these errors were encountered: