Skip to content

9lives 0.4.7

Latest

Choose a tag to compare

@github-actions github-actions released this 15 Oct 11:28
· 3 commits to main since this release
v0.4.7
c5e6382

CLI and @9l/playwright 0.4.7 are released together.

SDK

  • No runtime changes; @9l/playwright 0.4.7 is released with CLI 0.4.7.

Assess

Policy assessment-source-v13; the analyzer helper version is 10 and report
version 3 is unchanged.

  • Parse .js, .mjs, .cjs and .jsx specs as Playwright loads them:
    JavaScript with JSX and no TypeScript transform. Type annotations, as,
    interface, enum, import type, non-null ! and other TypeScript-only
    syntax in such a file now fail with the new typescript-in-javascript
    diagnostic (exit 2, or the file's error in a suite) instead of a clean
    report for a spec Playwright refuses to load. TypeScript specs and sources
    with no known extension still parse as TSX. The check builds a program over
    the single in-memory file; no library, module or type root is resolved.

CLI

  • 9l run, 9l result and the MCP run_test tool tell an unexpected pass
    apart from a broken test. A test.fail() test that passed is still a
    failure, but it is listed with ⚠, the message Expected to fail, but passed. and, in the receipt's failures, Playwright's expectedStatus
    and the last attempt's status; the receipt's validation text counts
    such tests. Previously it was a bare ✗ with no error text.
  • Failure diagnostics come from each test's final completed attempt only. A
    test.fail() test that timed out and then passed on retry no longer
    inherits the earlier attempt's error, failing line or attachments. The
    failure context passed to healing and returned by run_test drops tests
    with an expected, skipped or flaky outcome and keeps top-level errors such
    as a failed global teardown, so an expected failure's error is no longer
    attributed to the run.
  • 9l prove and 9l confirm report why a spec cannot run, such as a missing
    @9l/playwright build, instead of prove requires exactly one spec file
    or not a Playwright spec this runner can execute. The help text states
    that both need @9l/playwright and that prove reaches only fetch and XHR
    requests made through its page or context fixtures.
  • Receipt, run-result and run-status contracts gain the optional
    expectedStatus and status fields on each failure (additive).

Website and documentation

  • Link the 60-second launch film from the homepage and GitHub overview.

Install the SDK in your Playwright project:

npm install --save-dev @9l/playwright@0.4.7

Download the CLI archive for your operating system and architecture below, and verify it against SHA256SUMS. See the installation guide.

Full changelog: v0.4.6...v0.4.7