Skip to content

docs: refresh README Status + TESTING to v1.3.1 and live-verified test counts#95

Merged
dknauss merged 3 commits into
mainfrom
docs/readme-status-v1.3.1
Jul 6, 2026
Merged

docs: refresh README Status + TESTING to v1.3.1 and live-verified test counts#95
dknauss merged 3 commits into
mainfrom
docs/readme-status-v1.3.1

Conversation

@dknauss

@dknauss dknauss commented Jul 6, 2026

Copy link
Copy Markdown
Owner

What

Two docs-only fixes to stale content, each in its own commit.

1. docs: refresh Status/TESTING counts + live release. The README ## Status section was stale and contradicted shipped reality:

  • Claimed v1.1.1 was the live wp.org release — v1.3.1 has shipped.
  • Cited unit 44 / integration 29 — both suites have grown.

This updates the Status line and the matching stale counts in TESTING.md. Structure and voice unchanged.

2. docs(testing): fix stale E2E setup reference. PR #94 replaced the E2E globalSetup with a Playwright setup project at tests/e2e/auth.setup.ts, but TESTING.md still linked to the removed tests/e2e/global-setup.ts — a dead link that fails the Markdown link-and-anchor (lychee) check. Surfaced here after rebasing onto current main. Fixed the link + the "global setup" wording; the behavior it describes is unchanged.

Numbers re-derived from live commands (not memory or another doc)

Claim Source command Result
Live release = v1.3.1 wp.org plugins/info API 1.3.1
Unit = 90 tests, 101 assertions composer test:unit OK (90 tests, 101 assertions)
Integration = 47 tests, 122 assertions npm run test:php (wp-env tests-cli) OK (47 tests, 122 assertions)

Integration was run in wp-env on isolated local ports (a concurrent unrelated env held the defaults); that override was local-only and not committed.

Risk

Docs-only. No runtime or test code touched.

🤖 Generated with Claude Code

The README "## Status" section still claimed v1.1.1 as the live wp.org
release and cited unit 44 / integration 29; both are stale. v1.3.1 has
shipped and the suites have grown.

Re-derived every number from a live command, not from memory or another
doc:
- wp.org API (plugins/info) confirms 1.3.1 is the live release.
- composer test:unit  -> OK (90 tests, 101 assertions)
- npm run test:php    -> OK (47 tests, 122 assertions)

Updates the README Status line (v1.3.1; unit 90, integration 47) and the
matching stale counts in TESTING.md (unit 90/90 with 101 assertions,
integration 47/47 with 122 assertions). Structure and voice unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@dknauss dknauss force-pushed the docs/readme-status-v1.3.1 branch from 9a70402 to 27199e4 Compare July 6, 2026 00:54
@dknauss

dknauss commented Jul 6, 2026

Copy link
Copy Markdown
Owner Author

Note: the Review gate (P1/P2 addressed) check became a required status check on main just after this PR opened, so its first run didn't fire automatically. This comment triggers the gate (via the issue_comment trigger) so it posts a status and unblocks the PR.

PR #94 replaced the E2E `globalSetup` function with a Playwright *setup
project* at tests/e2e/auth.setup.ts, but TESTING.md still linked to the
removed tests/e2e/global-setup.ts — a dead link that fails the Markdown
link-and-anchor (lychee) check. Point the link at auth.setup.ts and drop
the "global setup" wording for the setup-project reality. The
password-normalization and single-login/stored-session behavior it
describes is unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Refreshes documentation to match the current shipped release and the current, empirically re-verified test suite sizes, and fixes an outdated E2E setup reference after the migration away from a Playwright globalSetup.

Changes:

  • Update README “Status” to reflect the current wp.org live release (v1.3.1) and current unit/integration test counts.
  • Update TESTING.md expected-status counts to match current unit/integration suite output.
  • Fix TESTING.md E2E setup documentation to reference tests/e2e/auth.setup.ts (setup project) instead of the removed global-setup.ts.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
TESTING.md Updates expected test counts and corrects the E2E setup reference to the current Playwright setup project.
README.md Updates the Status section to the current live release and current test counts.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

PR #94 renamed the E2E globalSetup to a Playwright setup project at
tests/e2e/auth.setup.ts, but left comments in fixtures.ts and
capture-screenshots.spec.ts still naming the removed global-setup.ts.
Comment-only; no behavior change. Archived .planning/ phase records keep
their original point-in-time wording.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@dknauss dknauss merged commit 441b3ce into main Jul 6, 2026
16 checks passed
@dknauss dknauss deleted the docs/readme-status-v1.3.1 branch July 6, 2026 01:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants