Compare commits

..

3 Commits

Author SHA1 Message Date
peptiderepo
0c5c30196b merge: resolve main conflict — conserve board smoke (PR #13) + dossier smoke (PR #14)
Conflict: CHANGELOG.md (add/add) and package.json (v1.1.0 vs v1.2.0).

Resolution:
- CHANGELOG.md: keep both entries, v1.2.0 above v1.1.0 (chronological order).
  Updated v1.2.0 description to reference v0.19.2 / v0.19.3 (hotfix context).
- package.json: use version 1.2.0 (PR #14 head; dossier smoke is the newer addition).
- tests/03-admin-plugins.spec.ts: auto-merged by git — board describe block (PR #13)
  at line 97, dossier describe block (PR #14) at line 158. Both conserved.

Dossier smoke selector #prab-dossier verified against v0.19.3 template
(templates/admin/dossier-page.php line 62/86) — registration parent change
does not affect markup.

Agent-Session: dossier-403-hotfix-20260612
2026-06-12 11:20:30 +00:00
Engineer PRAutoBlogger
fd2d0823d6 test(smoke): dossier page smoke guard — assert HTTP 200 + #prab-dossier + no fatal (v1.2.0)
Adds dossier smoke test to 03-admin-plugins.spec.ts (describe block:
'WP Admin — PRAutoBlogger Article Dossier').

Guards:
- Menu-ordering regression: wrong hookname -> wp_die 404 (same class as v0.19.1 board bug)
- PHP fatal on dossier load
- Missing #prab-dossier container (template regression)
- Stage-section regression (conditional on run data existing)

Defensive strategy:
- Tries canonical staging posts 925/930 via REST API first
- Falls back to most recent post via /wp-json/wp/v2/posts
- Falls back to post_id=0 (graceful empty state) with loud test.info() annotation
- Stage-section assertions conditional: if stages present they must render; if absent
  the pre-substrate graceful state is expected (no failure)

npx playwright test --list shows 24 tests (was 23).
New test at 03-admin-plugins.spec.ts:185.
TypeScript compiles without errors.

Part of PRAutoBlogger v0.19.2 M2 milestone. Companion PR: peptiderepo/prautoblogger#158.

Agent-Session: claude-sonnet-4-6
2026-06-12 10:40:49 +00:00
peptiderepo
113bb17e43 test(smoke): board page smoke guard — assert HTTP 200 + #prab-board (v1.1.0)
Add board page smoke test to 03-admin-plugins.spec.ts under the
'WP Admin — PRAutoBlogger board page' describe block.

The test navigates to /wp-admin/admin.php?page=prautoblogger-board and
asserts:
  1. HTTP 200 (not wp_die 404)
  2. #wpbody visible (authenticated admin session confirmed)
  3. body does NOT contain 'Invalid plugin page' (the wp_die string)
  4. #prab-board container visible (selector from templates/admin/board-page.php)

This guards against the v0.19.1 regression class: PRAutoBlogger_Board_Page
was registered at admin_menu priority 10, before the parent top-level menu
(also 10). WordPress computed the wrong hookname (admin_page_*) at
add_submenu_page() time; at request time it recomputed prautoblogger_page_*,
found nothing, and called wp_die() — 404. The board was un-navigable since
v0.19.0 shipped. With this test in the deploy gate, this failure class is
now un-shippable.

Spec compiles and lists cleanly (npx playwright test --list: 23 tests).
Cannot be validated against prod until v0.19.1 deploys; stated in spec comment.

Agent-Session: board-404-hotfix-20260612
2026-06-12 08:32:08 +00:00
3 changed files with 11 additions and 69 deletions

View File

@@ -2,26 +2,6 @@
All notable changes to the peptide-e2e smoke suite will be documented here.
## [1.3.0] - 2026-06-12
### Fixed
- **Auth setup survives `ERR_ABORTED` on wp-login.php** (`global.setup.ts`).
When Hostinger's LiteSpeed throttles a GitHub runner IP, `page.goto` can
throw `net::ERR_ABORTED` rather than a `TimeoutError`. Playwright marks the
browser context closed internally on abort, so the existing
`context.close()` call in the catch block threw
`"browserContext.close: Target page, context or browser has been closed"`,
which propagated out of catch and killed setup before the remaining retries
ran. Two production deploys were blocked by this flake on 2026-06-12.
Fix: introduced `safeClose()` helper that swallows the already-closed
error, so an aborted context never terminates the retry loop. Max attempts
raised from 3 → 5; backoff is now exponential (5 s / 10 s / 20 s / 40 s)
instead of a flat 15 s, giving the throttle window more time to clear.
Worst-case timing: 5 × 90 s navigation + 75 s backoff = ~525 s, well under
the 900 s (15 min) job timeout. Final-failure message explicitly names the
LiteSpeed throttle hypothesis so future CI logs self-diagnose.
## [1.2.0] - 2026-06-12
### Added

View File

@@ -8,25 +8,10 @@
* The saved auth state (playwright/.auth/admin.json) is reused by the
* "chromium" project so individual tests don't each incur a login round-trip.
*
* Retry hardening (2026-06-12 v1): Hostinger rate-limits GitHub runner IPs on
* Retry hardening (2026-06-12): Hostinger rate-limits GitHub runner IPs on
* wp-login.php, causing TimeoutError on page.goto. The login attempt is now
* retried up to MAX_ATTEMPTS times with a fresh browser context per attempt
* and BACKOFF_MS delay between attempts so transient throttle windows clear.
*
* Retry hardening (2026-06-12 v2 — ERR_ABORTED fix): When Hostinger aborts
* the connection (net::ERR_ABORTED), Playwright marks the context as closed
* internally. A subsequent context.close() call throws
* "browserContext.close: Target page, context or browser has been closed",
* which propagated out of the catch block and crashed setup without consuming
* remaining retries. Fix: context.close() is now guarded in its own
* try/catch so an already-closed context never aborts the retry loop.
* MAX_ATTEMPTS raised to 5; backoff doubled each time (5s/10s/20s/40s) so the
* LiteSpeed throttle window has time to clear before each retry.
*
* Timing math (job timeout-minutes: 15 = 900 s):
* 5 attempts × NAV_TIMEOUT (90 s) = 450 s navigation ceiling
* 4 inter-attempt waits (5+10+20+40 s) = 75 s backoff ceiling
* Total worst-case: ~525 s — well under the 900 s job timeout.
*/
import { test as setup, expect } from '@playwright/test';
@@ -35,22 +20,9 @@ import * as fs from 'fs';
const AUTH_FILE = path.join(__dirname, 'playwright/.auth/admin.json');
const MAX_ATTEMPTS = 5;
const NAV_TIMEOUT = 90_000; // 90 s per navigation attempt
/** Exponential backoff delays (ms) between attempts: 5 s, 10 s, 20 s, 40 s */
function backoffMs(attempt: number): number {
return 5_000 * Math.pow(2, attempt - 1);
}
/** Safely close a context that Playwright may have already closed internally. */
async function safeClose(context: import('@playwright/test').BrowserContext): Promise<void> {
try {
await context.close();
} catch {
// Ignored: context was already closed (e.g. after ERR_ABORTED or crash).
}
}
const MAX_ATTEMPTS = 3;
const BACKOFF_MS = 15_000; // 15 s between attempts
const NAV_TIMEOUT = 90_000; // raised from 30 s → 90 s per attempt
setup('authenticate as WP admin', async ({ browser }) => {
const user = process.env.WP_ADMIN_USER;
@@ -103,7 +75,7 @@ setup('authenticate as WP admin', async ({ browser }) => {
await page.context().storageState({ path: AUTH_FILE });
console.log(`[setup] Login succeeded on attempt ${attempt}/${MAX_ATTEMPTS}`);
await safeClose(context);
await context.close();
return; // success — exit setup
} catch (err) {
lastError = err;
@@ -112,20 +84,11 @@ setup('authenticate as WP admin', async ({ browser }) => {
`[setup] Login attempt ${attempt}/${MAX_ATTEMPTS} FAILED: ${message}`
);
// IMPORTANT: use safeClose — if Playwright received ERR_ABORTED it marks
// the context closed internally, so a plain context.close() throws
// "Target page, context or browser has been closed". Without this guard
// that secondary throw propagated out of catch and killed setup before
// the remaining retries ran.
await safeClose(context);
await context.close();
if (attempt < MAX_ATTEMPTS) {
const wait = backoffMs(attempt);
console.log(
`[setup] Waiting ${wait / 1000}s before retry ` +
`(LiteSpeed throttle cool-down — attempt ${attempt + 1}/${MAX_ATTEMPTS}) ...`
);
await new Promise((resolve) => setTimeout(resolve, wait));
console.log(`[setup] Waiting ${BACKOFF_MS / 1000}s before retry ...`);
await new Promise((resolve) => setTimeout(resolve, BACKOFF_MS));
}
}
}
@@ -134,8 +97,7 @@ setup('authenticate as WP admin', async ({ browser }) => {
throw new Error(
`[setup] All ${MAX_ATTEMPTS} login attempts failed. ` +
`Last error: ${lastError instanceof Error ? lastError.message : String(lastError)}\n` +
`Hypothesis: Hostinger LiteSpeed is throttling GitHub runner IPs on wp-login.php — ` +
`connections abort (ERR_ABORTED) or time out in bursts. ` +
`Re-run the workflow once the throttle window clears, or increase MAX_ATTEMPTS / backoffMs().`
`Hint: Hostinger may still be throttling GitHub runner IPs. ` +
`Re-run the workflow once the throttle window clears, or increase BACKOFF_MS / MAX_ATTEMPTS.`
);
});

View File

@@ -1,6 +1,6 @@
{
"name": "peptide-e2e",
"version": "1.3.0",
"version": "1.2.0",
"description": "Playwright smoke tests for peptiderepo.com (staging + production)",
"private": true,
"scripts": {