Test evidence¶
Generated by the Docs workflow from the Surefire results of the test run and the rationale comments in the test sources. Do not edit by hand.
The run executed 6 tests (0 failures, 0 errors, 0 skipped) in 0.2s across the 1 modules listed below, without Docker or any external service - see CONTRIBUTING.
| Module | Component under test | Tests | Time |
|---|---|---|---|
veredium-core |
VerediumTest |
6 | 0.1s |
veredium-core¶
6 tests.
VerediumTest¶
6 tests.
should build the User-Agent token from the name and the version
Rationale
What is tested? the product token for a known version.
How is success determined? veredium/<version>, name and version joined by a single slash.
Why does it matter? the token is what a peer's access log shows for this client; the product/version shape is the one RFC 9110 defines, and operators grep for it.
should fall back to the bare name when the version is unknown(String)[1]
Rationale
What is tested? the product token when no version is known - null (no manifest), empty and blank.
How is success determined? the bare name, without a trailing slash.
Why does it matter? veredium/ with nothing after the slash is not a valid product token; a peer that validates the header would reject the call for a cosmetic reason.
should fall back to the bare name when the version is unknown(String)[2]
Rationale
What is tested? the product token when no version is known - null (no manifest), empty and blank.
How is success determined? the bare name, without a trailing slash.
Why does it matter? veredium/ with nothing after the slash is not a valid product token; a peer that validates the header would reject the call for a cosmetic reason.
should fall back to the bare name when the version is unknown(String)[3]
Rationale
What is tested? the product token when no version is known - null (no manifest), empty and blank.
How is success determined? the bare name, without a trailing slash.
Why does it matter? veredium/ with nothing after the slash is not a valid product token; a peer that validates the header would reject the call for a cosmetic reason.
should name itself veredium
Rationale
What is tested? the NAME constant every logger name and artifact id derives from.
How is success determined? the constant equals the lowercase project name.
Why does it matter? the name is part of the operator-facing contract (logger names, artifact ids, the User-Agent token); a drift would rename what dashboards and log filters key on.
should report no version and the bare token when not loaded from a jar
Rationale
What is tested? the manifest-backed version property, read from the classes directory this test runs against.
How is success determined? the version is null and the token is the bare name - the fallback is what every IDE run and this suite see.
Why does it matter? the property must not throw outside a jar, where there is no manifest, and the public token must agree with the internal rule it delegates to.