Content Guardian Content Guardian
Navigation
← CGS3 AI Portal Overview Features Architecture & CAS Developer Guide Security Model Testing & QA Matrix User Documentation Downloads (Pending)
CGS3 Portal / Content Guardian / Testing Results

QA Master Testing Ledger

Transparent, evidence-based test results. Clear demarcation between verified mock tests, database harnesses, and pending releases.

VERIFIED PASS PHP 8.5.12

1. Authorization Mock Suite

Tests 1–18 in preview-authorization-tests.php executed and passed on local PHP 8.5.12 runtime with exit code 0.

✓ 18 of 18 Mock Tests PASS
SYNTAX VALIDATED PHP / PDO

2. MySQL Concurrency Harness

mysql-concurrency-test.php harness corrected to fail-closed on driver/connection absence. Physical MySQL 8.0 concurrency execution is NOT_RUN in current submitted evidence.

• Physical MySQL 8.0: NOT_RUN
PENDING GATE Final Release

3. WordPress Integration & Release

Live WordPress end-to-end multi-author testing is in progress. Final public plugin release gate is not yet authorized as completed.

• Public Release Pending

Preview Authorization Mock Suite (Tests 1–18)

Executed locally on PHP 8.5.12 with full error reporting (-d error_reporting=-1). Exit code: 0.

Test # Test Scenario & Description Expected Status Result
Test 01 Valid preview request with administrator capabilities and valid nonce HTTP 200 OK + Token PASS
Test 02 Missing WordPress nonce token in request header/body HTTP 403 Forbidden PASS
Test 03 Forged or malformed WordPress nonce string HTTP 403 Forbidden PASS
Test 04 Authenticated user lacking manage_options capability HTTP 403 Forbidden PASS
Test 05 Request submitted with missing or non-numeric post ID HTTP 400 Bad Request PASS
Test 06 Request targeting a deleted or nonexistent post ID HTTP 404 Not Found PASS
Test 07 Action password required by configuration but omitted by caller HTTP 403 Forbidden PASS
Test 08 Action password submitted does not match Bcrypt hash HTTP 403 Forbidden PASS
Test 09 Valid action password verified against Bcrypt cost 12 hash HTTP 200 OK PASS
Test 10 Target post holds an active lock owned by a different user HTTP 423 Locked PASS
Test 11 Target post holds an active lock owned by the same user HTTP 200 OK (Allowed) PASS
Test 12 Target post lock timestamp has expired (> 15 mins) HTTP 200 OK (Reacquired) PASS
Test 13 Action token replay after expiration or prior consumption HTTP 403 Forbidden PASS
Test 14 Intervening edit detected in database during preview lock (Conflict detection) HTTP 409 Conflict + Lock Released PASS
Test 15 Pre-update backup verification failure (add_post_meta returns false) Fail-Closed (Zero Update) PASS
Test 16 Collation edge-case (accents/case) tested against binary CAS comparison Conflict Detected (CAS PASS) PASS
Test 17 Gutenberg block markup preservation across regex cleaning routines Blocks Preserved PASS
Test 18 Scheduled WP-Cron registration context isolation check Cron Registered Globale PASS

Case Study: Test 14 Mock Decoupling & Conflict Verification

During early diagnostic runs on PHP 8.5.12, Test 14 initially failed with HTTP 400 Bad Request instead of the expected HTTP 409 Conflict.

Root Cause Diagnosis:

The mock environment coupled the simulated WordPress post object with the underlying database query representation. Modifying the post's text before the preview handler ran caused the preview step itself to find no cleanable tokens, triggering an early 400 error before the in-lock revalidation could be reached.

Verified Correction:

By cleanly separating the mocked WordPress cached post (which provides cleanable content during initial preview) from the simulated database row (which was altered to simulate an intervening save by another author), execution successfully reached the in-lock comparison. The system properly asserted HTTP 409 Conflict and verified that the owner-bound lock was immediately released.