java/test-without-assertion
A test that cannot fail — no assertion or verify on the production result, an expected-exception `try` with no `fail()`/`assertThrows`, a `catch (Throwable|AssertionError)` that swallows the assertion, or mocks stubbed but never handed to the code under test. Assert on the real output; use `assertThrows`.
**/*.javaservice-javastandards/stacks/java.md:44Read it in the terminal
The same facts, from the checkout you are already in — no browser, and no network.
$ npx redlinegate explain java/test-without-assertion
Where this came from
You are most likely here from a review comment. A finding names its rule and, when your repository has told Redline where the standard is published, its address:
Redline/HIGH [java/test-without-assertion]: … → …/r/java/test-without-assertion
That second line is written by redline init --docs-url and is empty until an organisation sets one — there is no default, because a link to somebody else's copy of the standard is worse than no link. See Onboard a repository.
In context
The Java (Spring Boot) standard lists this rule with the rest of its stack, in the file a reviewer and an AI assistant both read.
Other HIGH rules in this stack
java/optional-misuse`Optional` misuse: `Optional.get()` without presence check, `Optional` as field or method parameter.java/entity-equals-hashcode`equals`/`hashCode` on JPA entities using generated IDs incorrectly (breaks in sets before persist) — or missing entirely on value objects.java/missing-bean-validationMissing `@Valid` + Bean Validation on request DTOs at controller boundary.java/transaction-scope-too-wideTransaction scope too wide: external HTTP calls or message publishing inside `@Transactional` — holds connections, couples commit to remote latency.java/async-without-executor`@Async`/`CompletableFuture` work without dedicated executor — default pool starvation.java/exception-detail-in-responseException details (stack traces, SQL) returned in API error responses — map to problem-detail responses.