Local containerized testing for development #2862
Locked
remingtonc
started this conversation in
Community Discussions
Replies: 1 comment 1 reply
|
This has been already implemented in the 0.16 dev branch. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Testing appears to have long args, arbitrary system packages, or moving parts per docs: https://stalw.art/docs/development/test
Making a change and running tests thus has friction from an outside perspective.
Example to containerize and codify: https://github.com/stalwartlabs/stalwart/compare/main...remingtonc:stalwart:test-containerize?expand=1
Tests being difficult to run make changes difficult to validate.
e.g. I am trying to add the domain principal to config file provisioning i.e.
Notably not sure if this is actually needed, but seemed like it was missing compared to usual individual user provisioning flows.
All reactions