-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ST] default builders for plain/tls internal clients #9658
Conversation
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't go through all the changes, but I have few comments that I would like to have addressed before continuing.
As I mentioned offline, having one or two "default" methods that sets completely everything makes the tests confusing and it's not really clear to me, what are the requirements that need to be met for successfully sending/receiving messages.
If you get this "default" clients with everything set, some of the newbies will don't know that for SCRAM-SHA you need to set the username and create a KafkaUser. Same for TLS.
So I would create methods for creating the clients based on TestStorage, yes, but I would not have one method for all of the use-cases, but multiple methods that will cover multiple auth options. At least that will be (for me and I guess for anyone else) clearer to see, what's really going on and what is needed to be done before the message transmission.
systemtest/src/test/java/io/strimzi/systemtest/connect/ConnectST.java
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/connect/ConnectST.java
Outdated
Show resolved
Hide resolved
systemtest/src/main/java/io/strimzi/systemtest/utils/ClientUtils.java
Outdated
Show resolved
Hide resolved
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
@strimzi-ci run tests --testcase=RackAwarenessST --profile=all --env=STRIMZI_FEATURE_GATES=-KafkaNodePools,-UnidirectionalTopicOperator,-UseKRaft |
|
✔️ Test Summary ✔️TEST_PROFILE: all |
@strimzi-ci run tests --profile=all --env=STRIMZI_FEATURE_GATES=-KafkaNodePools,-UnidirectionalTopicOperator,-UseKRaft |
|
❌ Test Summary ❌TEST_PROFILE: all ❗ Test Failures ❗
Re-run command: |
@strimzi-ci run tests --profile=all --env=STRIMZI_FEATURE_GATES=-KafkaNodePools,-UnidirectionalTopicOperator,-UseKRaft |
|
❌ Test Summary ❌TEST_PROFILE: all ❗ Test Failures ❗
Re-run command: |
/azp list |
/azp run feature-gates-regression |
Azure Pipelines successfully started running 1 pipeline(s). |
@strimzi-ci run tests --profile=all --testcase=HttpBridgeST,MirrorMaker2ST --parallel-count=1 --env=STRIMZI_FEATURE_GATES=-KafkaNodePools,-UnidirectionalTopicOperator,-UseKRaft |
|
❌ Test Summary ❌TEST_PROFILE: all ❗ Test Failures ❗
Re-run command: |
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
…using sink Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
…well Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
Signed-off-by: hzrncik <[email protected]>
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
@see-quick last fail unrelated to the PR. |
Signed-off-by: hzrncik <[email protected]>
Type of change
Description
Changes described by files:
TestConstants
andTestStorage
Concerned mainly with new fields (added for smooth work with continuous clients)
continuousProducerName
(All 3 same as their basic counterparts but with extra suffix)continuousConsumerName
continuousTopicName
continuousMessageCount
(300 in comparison to 100)ClientUtils
Primarily following methods added:
getInstantPlainClientBuilder
getInstantTlsClientBuilder
getContinuousPlainClientBuilder
getContinuousTlsClientBuilder
Continuous methods are waiting for continuous, clients with respective
teststorage.fields
.as these clients are basically hello world (used to be called that way).
there is additionaly namespace and default user which are there for completness.
Any of them can be changed and as can be seen in specific tests they sometimes are which makes it visible what is actually important about given producer/consumer.
additional helper method
waitForContinuousClientSuccess
which waits specifically for continuous clients.<specific>ST
classeschanges include:
Environment.TEST_SUITE_NAMESPACE
with testStorage atlernative.continuous
or<random>
if not needed