Closed YutongLi291 closed 2 months ago
In our tests, we will have tests that wish to verify that worker is in a STOPPING status, without waiting for the worker to be STOPPED.
STOPPING
STOPPED
Add an option for the Worker.stop() function to not wait for worker to be STOPPED, so that in tests we can verify that a worker is STOPPING
Worker.stop()
More flexibility in test code
hatch run fmt, hatch build
hatch run fmt
hatch build
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issues 0 New issues 0 Accepted issues
Measures 0 Security Hotspots 0.0% Coverage on New Code 0.0% Duplication on New Code
See analysis details on SonarCloud
What was the problem/requirement? (What/Why)
In our tests, we will have tests that wish to verify that worker is in a
STOPPING
status, without waiting for the worker to beSTOPPED
.What was the solution? (How)
Add an option for the
Worker.stop()
function to not wait for worker to beSTOPPED
, so that in tests we can verify that a worker isSTOPPING
What is the impact of this change?
More flexibility in test code
How was this change tested?
hatch run fmt
,hatch build
Was this change documented?
No
Is this a breaking change?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.