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
I have a hosted server that we can use for ongoing testing, does it make sense to set up a simple commit-hook trigger to rebuild containers and re-run full interop tests?
The text was updated successfully, but these errors were encountered:
That would definitely work. The only problem with this is that it would be harder to test rare edge cases. But then again, maybe that should be solved in a different way (something like endurance testing combined with a chaos monkey at the transport layer).
I definitely prefer commit-hook integration tests to be easily reproducible and consistent, and to do noise/integration testing independently. Now that I understand tournament mode, it makes sense to me to have a way to let that run continuously and then introduce chaos into that system :)
I have a hosted server that we can use for ongoing testing, does it make sense to set up a simple commit-hook trigger to rebuild containers and re-run full interop tests?
The text was updated successfully, but these errors were encountered: