-
Notifications
You must be signed in to change notification settings - Fork 187
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
[full-ci][tests-only] Refactor service health and ready url in tests #10808
Conversation
7fff1a5
to
819e885
Compare
819e885
to
1f17ee3
Compare
1f17ee3
to
cae9910
Compare
| %base_url_hostname%:9297/healthz | antivirus | | ||
When a user sends "GET" request to the following url with no authentication | ||
| endpoint | service | | ||
| http://%base_url_hostname%:9297/healthz | antivirus | |
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.
so we were sending request to https
instead of http
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.
we are sending request to service health endpoint i.e http://hostname:service_debug_port/...
bf33695
to
64e9ec5
Compare
LGTM 👍 |
5c988c1
to
59447d3
Compare
tests/acceptance/features/apiAntivirus/serviceAvailabilityCheck.feature
Outdated
Show resolved
Hide resolved
59447d3
to
1f32eec
Compare
1f32eec
to
acc993a
Compare
Quality Gate passedIssues Measures |
[full-ci][tests-only] Refactor service health and ready url in tests
[full-ci][tests-only] Refactor service health and ready url in tests
Description
The problem lies in the test code, which is sending requests to the following incorrect URL: https://localhost:9200/ocalhost:9229/healthz and https://localhost:9200/ocalhost:9229/readyz
As a result, the server returns a 200 status code, but the request is not directed to the intended endpoint, causing tests to pass erroneously.
This PR update test code base to send request to proper url
Note: This PR isolates the problematic service into a separate scenario for testing. Once issue #10661 is resolved, the scenario separation introduced in this PR should be reverted.
A follow-up QA point has been added in #10316.
Related Issue
Part of
500
status code #10661Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: