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

Integration tests #28

Open
fopina opened this issue Mar 19, 2023 · 0 comments
Open

Integration tests #28

fopina opened this issue Mar 19, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@fopina
Copy link
Contributor

fopina commented Mar 19, 2023

Related software versions

All

Description

To easily validate newer dkron versions, it would be good to have integration tests going asserting each call to dkron server behaves as expected.

These tests ideally will not run as the normal unit test battery as they will be slower and impacts local development workflow, but they should always run in CI / actions.

How to properly separate them from the rest?
Use pytest marks (such as the slow one), and no longer support running tests using default django test runner?
Create new app for those?
Or simply create separte test module in the existing one and every one should just run the "unit" module locally (and "sit" whenever they wanted)? This is probably the easiest IMO

Use cases

Quickly validate newer versions of dkron as sometimes there are breaking changes, such as renames flags in the CLI (#14) or API behavior (such as the fix that resolves #19)

References

No response

@fopina fopina added the enhancement New feature or request label Mar 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant