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

Clean up the osier test suite #26

Open
1 task
samgdotson opened this issue Oct 14, 2022 · 0 comments
Open
1 task

Clean up the osier test suite #26

samgdotson opened this issue Oct 14, 2022 · 0 comments
Labels
Comp:Core This issue has to do with the main bulk of the code or document. (methods, main content) Difficulty:2-Challenging This issue may be complex or require specialized skills. Priority:4-Low This work is valuable, but not urgent or mission critical. Status:1-New No one has claimed this issue yet. It is in need of solving. Type:Test Is related to software testing. Failing tests, necessary new tests, test frameworks, etc.

Comments

@samgdotson
Copy link
Collaborator

The osier test suite has fairly comprehensive tests, however, some share resources and could use some reorganizing.

One of the first things that could be done is create conftest.py file that configures the test session.

  • create a conftest.py file in tests/
@samgdotson samgdotson added Comp:Core This issue has to do with the main bulk of the code or document. (methods, main content) Difficulty:2-Challenging This issue may be complex or require specialized skills. Priority:4-Low This work is valuable, but not urgent or mission critical. Status:1-New No one has claimed this issue yet. It is in need of solving. Type:Test Is related to software testing. Failing tests, necessary new tests, test frameworks, etc. labels Oct 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Comp:Core This issue has to do with the main bulk of the code or document. (methods, main content) Difficulty:2-Challenging This issue may be complex or require specialized skills. Priority:4-Low This work is valuable, but not urgent or mission critical. Status:1-New No one has claimed this issue yet. It is in need of solving. Type:Test Is related to software testing. Failing tests, necessary new tests, test frameworks, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@samgdotson