Add secure and cluster tests. #236
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
YoEight
force-pushed
the
yoeight/db-334-improve-java-client-testing
branch
from
6f42a73
to
f5f6825
Compare
YoEight
force-pushed
the
yoeight/db-334-improve-java-client-testing
branch
from
f5f6825
to
417cfef
Compare
cdevarenne
previously approved these changes
Sep 22, 2023
YoEight
force-pushed
the
yoeight/db-334-improve-java-client-testing
branch
from
7fd4471
to
4abf4b7
Compare
YoEight
force-pushed
the
yoeight/db-334-improve-java-client-testing
branch
from
4abf4b7
to
1dcdfe1
Compare
cdevarenne
approved these changes
Sep 26, 2023
pvanbuijtene
approved these changes
Oct 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changed: Add secure and cluster tests.
PR doesn't have as much changes as the diff suggests. Tests were re-organized so those can run regardless of the database topology:
Tests were almost gathered based on the scope of the ESDB api minus one caveat (Expectations):
Expectations tests are based on the image produced by the testdata repo. Those tests run a prepopulated database so we can test invariant behaviours across all clients. Those expectations tests are mostly reads operations including (persistent) subscriptions. There are projection tests too. Expectations tests do not run on a cluster, just single node setup.
Finally, this PR adds a dispatch action so we can test a specific server version manually. The version should match a version we deployed on our main repo docker registry.