-
Notifications
You must be signed in to change notification settings - Fork 48
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
Mocks warm up #833
Mocks warm up #833
Conversation
Co-authored-by: Simon Lo <simon.lo@sony.com>
Co-authored-by: jonathan-r-thorpe <64410119+jonathan-r-thorpe@users.noreply.github.com>
Is this only an issue when Auth is enabled? And if so should we only delay if Auth enabled? |
I think theoretically it applies to any mock services that might be required before some test suite's first interaction with the API or client under test. So, DNS server, CRL or OCSP server, Auth server, ... This PR makes the delay tunable via UserConfig.py, and defaults it to zero delay, so it seems to cover all use cases optimally? |
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.
Should be a useful feature. Looks ok.
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
This gives the API or client under test a chance to use the mock services before any test case is run.