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

Distinguish unit tests vs integration tests #15

Open
delucchi-cmu opened this issue Apr 17, 2023 · 3 comments
Open

Distinguish unit tests vs integration tests #15

delucchi-cmu opened this issue Apr 17, 2023 · 3 comments
Labels
question Further information is requested

Comments

@delucchi-cmu
Copy link
Contributor

Creating tiers of test targets could reduce typical test-driven-development build cycle times.

@delucchi-cmu delucchi-cmu added the question Further information is requested label Apr 17, 2023
@delucchi-cmu delucchi-cmu self-assigned this Apr 17, 2023
@delucchi-cmu
Copy link
Contributor Author

delucchi-cmu commented Apr 24, 2023

  • run black / isort
  • add pytest.mark.slow to pytest configuration and mark tests that are > 1s as @slow
  • make sure tests can be run in any order (may spawn further actions to achieve)
  • modify CI to run pytest "not slow" and then pytest "slow"

@eacharles
Copy link
Collaborator

We probably want to integrate this in to the template for the relevent github workflows and then push it to various repos.

@eacharles eacharles transferred this issue from LSSTDESC/rail_attic Jun 14, 2023
@eacharles
Copy link
Collaborator

This is large done by moving the longer stuff to the notebooks where are run in the rail smoke tests.

@delucchi-cmu delucchi-cmu removed their assignment Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants