You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using microcks as binary and run testing stage in gitlab CI as follows:
"$CI_PROJECT_DIR/utils/microcks-cli" test
"$api_version"
"$API_ENDPOINT"
OPEN_API_SCHEMA
--microcksURL="$MICROCKS_URL"
--keycloakClientId="$KEYCLOAK_CLIENT_ID"
--keycloakClientSecret="$KEYCLOAK_CLIENT_SECRET"
--insecure-tls
--filteredOperations='["GET /api/v1/version", "GET /api/v1/services"]'
--waitFor=10sec 2>&1 | tee -a microcks-results/test-report.txt
The link to the executed test was meant to provide quick access to the UI showing the test result. So I think having a # in the URL is correct, as the Angular UI is using this for client-side navigation. I think the problem here is rather tied to the prepended /api prefix that comes from the microcksURL flag, and that should be removed when building the link.
Reproduced on current master (f9550f5) against a real microcks-uber:latest-native server.
microcks test ... --microcksURL http://localhost:18089/api prints Full TestResult details are available here: http://localhost:18089/api/#/tests/<id>.
That URL does not work: GET http://localhost:18089/api/#/tests returns 404, while http://localhost:18089/#/tests returns 200.
With --microcksURL http://localhost:18089 (no /api), the link is http://localhost:18089/#/tests/<id>, which is correct.
--output json carries the same bad link.
This confirms @lbroudoux's analysis: the # is fine, and the problem is the /api suffix of --microcksURL being kept in the link. The link is built in cmd/test.go:153, and a similar one in cmd/testDryRun.go:454 (I did not test that one). Trimming a trailing /api (and /) from the server address before building the link should fix it.
Disclosure: this comment was drafted with AI assistance, and the results were run locally.
Hi, I'd like to work on this issue. I plan to fix the URL construction for both the regular test and dry-run commands and add regression tests for URLs with and without the /api suffix.
Is anyone already working on this, or would it be okay for me to submit a PR?
Activity
lbroudoux commentedon Oct 16, 2026
Hi @astramax57
Thanks for reporting this one!
The link to the executed test was meant to provide quick access to the UI showing the test result. So I think having a
#in the URL is correct, as the Angular UI is using this for client-side navigation. I think the problem here is rather tied to the prepended/apiprefix that comes from themicrocksURLflag, and that should be removed when building the link.yada commentedon Oct 17, 2026
Reproduced on current master (f9550f5) against a real
microcks-uber:latest-nativeserver.microcks test ... --microcksURL http://localhost:18089/apiprintsFull TestResult details are available here: http://localhost:18089/api/#/tests/<id>.GET http://localhost:18089/api/#/testsreturns 404, whilehttp://localhost:18089/#/testsreturns 200.--microcksURL http://localhost:18089(no/api), the link ishttp://localhost:18089/#/tests/<id>, which is correct.--output jsoncarries the same bad link.This confirms @lbroudoux's analysis: the
#is fine, and the problem is the/apisuffix of--microcksURLbeing kept in the link. The link is built incmd/test.go:153, and a similar one incmd/testDryRun.go:454(I did not test that one). Trimming a trailing/api(and/) from the server address before building the link should fix it.Disclosure: this comment was drafted with AI assistance, and the results were run locally.
SajanBisht commentedon Oct 17, 2026
Hi, I'd like to work on this issue. I plan to fix the URL construction for both the regular test and dry-run commands and add regression tests for URLs with and without the /api suffix.
Is anyone already working on this, or would it be okay for me to submit a PR?