This repository has been archived by the owner on Aug 26, 2021. It is now read-only.
Clear MockKubernetesApplicationAdapterService.CREATED_DEPLOYMENT_STATES in RequestBrokerKubernetesServiceTest #327
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.
The test
com.vmware.admiral.request.kubernetes.RequestBrokerKubernetesServiceTest.testRequestStateHasK8sInfo
is not idempotent and fail if run twice in the same JVM, because it pollutes some states shared among tests. It may be good to clean this state pollution so that some other tests do not fail in the future due to the shared state polluted by this test.Detail
Running
RequestBrokerKubernetesServiceTest.testRequestStateHasK8sInfo
twice would result in the second run failing due to the following assertion error:The root cause is that the static
MockKubernetesApplicationAdapterService.CREATED_DEPLOYMENT_STATES
is updated during the first test run, but doesn't get cleared upon test exits.The suggested fix is to clear the static variable
MockKubernetesApplicationAdapterService.CREATED_DEPLOYMENT_STATES
inMockKubernetesApplicationAdapterService.clear()
, which is already invoked in thesetup()
function. This will ensure that this static variable is reset before each test is run.With the proposed fix, the test does not pollute the shared state (and passes when run twice in the same JVM).