"Step N passed" log entry carries the step's return value as data
context.assert accepts an optional details argument; on failure the
assertion:fail entry stores { details, error } as data
assertion failures throw AssertionFailedError so "Step N failed" and
"Snippet X failed" entries name only the assertion, without repeating
the details; the step run description keeps the full message
exported e2e runtime accepts and prints assert details
log output shows elapsed time in whole seconds, matching the stored
timestamp resolution
run artifact and scenario file names link to the inline file content
in a new tab
- "Step N passed" log entry carries the step's return value as data
- context.assert accepts an optional details argument; on failure the
assertion:fail entry stores { details, error } as data
- assertion failures throw AssertionFailedError so "Step N failed" and
"Snippet X failed" entries name only the assertion, without repeating
the details; the step run description keeps the full message
- exported e2e runtime accepts and prints assert details
- log output shows elapsed time in whole seconds, matching the stored
timestamp resolution
- run artifact and scenario file names link to the inline file content
in a new tab
- "Step N passed" log entry carries the step's return value as data
- context.assert accepts an optional details argument; on failure the
assertion:fail entry stores { details, error } as data
- assertion failures throw AssertionFailedError so "Step N failed" and
"Snippet X failed" entries name only the assertion, without repeating
the details; the step run description keeps the full message
- exported e2e runtime accepts and prints assert details
- log output shows elapsed time in whole seconds, matching the stored
timestamp resolution
- run artifact and scenario file names link to the inline file content
in a new tab
ars9
self-assigned this 2026-10-02 11:06:03 +03:00
ars9
merged commit 0f84db57f1 into master2026-10-02 11:09:52 +03:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
assertion:fail entry stores { details, error } as data
"Snippet X failed" entries name only the assertion, without repeating
the details; the step run description keeps the full message
timestamp resolution
in a new tab
- "Step N passed" log entry carries the step's return value as data - context.assert accepts an optional details argument; on failure the assertion:fail entry stores { details, error } as data - assertion failures throw AssertionFailedError so "Step N failed" and "Snippet X failed" entries name only the assertion, without repeating the details; the step run description keeps the full message - exported e2e runtime accepts and prints assert details - log output shows elapsed time in whole seconds, matching the stored timestamp resolution - run artifact and scenario file names link to the inline file content in a new tab