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.

Sign up for GitHub

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

Jump to bottom

Detectree2 testing #131

Open
ma595 opened this issue Dec 2, 2023 · 0 comments
Open

Detectree2 testing #131

ma595 opened this issue Dec 2, 2023 · 0 comments
Assignees
@ma595
Labels
testing

Comments

@ma595
Copy link
Collaborator

ma595 commented Dec 2, 2023 •
edited
Loading

A quick review of testing in Detectree2 has highlighted the following issues:

  • There is a large amount of overlap between the integration test in demo.py and the unit testing in this directory.
  • The current testing strategy is to use unittest in coordination with pytest. Is this necessary? Pytest can be used exclusively.
  • The unit tests here are not clearly marked as such. Consider moving into unit directory.
  • test_models.py will always succeed because of the self.assertEqual(1,1).
  • test_evaluation.py is largely incomplete.
@ma595 ma595 self-assigned this Dec 2, 2023
@ma595 ma595 added the testing label Dec 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ma595 ma595

Labels
testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ma595