You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 theslow
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
The text was updated successfully, but these errors were encountered: