-
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] Big refactor of Test Storage usage in ST #9569
Conversation
@strimzi-ci run tests --cluster-type=ocp --cluster-version=4.14 --install-type=bundle --profile=acceptance |
|
❌ Test Summary ❌TEST_PROFILE: acceptance ❗ Test Failures ❗
Re-run command: |
bcdc029
to
92843e6
Compare
systemtest/src/test/java/io/strimzi/systemtest/bridge/HttpBridgeST.java
Outdated
Show resolved
Hide resolved
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.
yeah as Lukas mentioned, in the discussion we agreed to go with having all data from extensionContext
or/and going with TestStorage
, but apart from this I do believe that rest of refactor is as we spoke about so LGTM so far.
Also should we not run more than acceptance profile on changes in basically almost all of the test classes ?
Based on the character of this refactor, i took the acceptance testrun as a minimum pass indicator, you are correct as all tests should be run. |
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
/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.
LGTM, assuming that tests pass.
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run upgrade |
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.
Thanks for the PR, few nits
systemtest/src/test/java/io/strimzi/systemtest/log/LogSettingST.java
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/log/LogSettingST.java
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/log/LogSettingST.java
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/metrics/MetricsST.java
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/metrics/MetricsST.java
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/operators/ReconciliationST.java
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/operators/ReconciliationST.java
Outdated
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/operators/topic/ThrottlingQuotaST.java
Show resolved
Hide resolved
systemtest/src/test/java/io/strimzi/systemtest/rollingupdate/RollingUpdateST.java
Show resolved
Hide resolved
612a1ed
to
cccf391
Compare
cccf391
to
6950aa9
Compare
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
The only issue in azp regression is with testKafkaConnectAndConnectorStatus => missing topic |
/azp run upgrade |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp list |
/azp run namespace-rbac-scope-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.
LGTM, thanks
Signed-off-by: jkalinic <[email protected]>
Signed-off-by: jkalinic <[email protected]>
Signed-off-by: jkalinic <[email protected]>
Signed-off-by: jkalinic <[email protected]>
Signed-off-by: jkalinic <[email protected]>
632a66a
to
75e59f1
Compare
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
Type of change
Description
This PR should consist of all the planned changes for testStorage class and its usage throughout the STs. The main focus point is the replacement of redundant variables that were being set directly from test storage, now there are only those with specific meaning to them. This PR also includes the changes to initialization of the TestStorage, every test should get it via the extensionContext from StorageMap.
Checklist