Drop single namespace assumption from E2E tests #1446
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
thbkrkr
reviewed
Aug 1, 2019
Also adds a test for cross namespace association that currently only works in local mode.
charith-elastic
force-pushed
the
e2e-cross-ns-assoc
branch
from
0613060
to
42b7e70
Compare
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.
Currently the E2E test utilities assume that resources are all within a single namespace. This PR removes that assumption in order to support running tests across multiple namespaces.
Also adds a test for cross namespace ES-KB association that currently only
works in local mode due to reasons described in #1438.
Partially fixes #782