# Globalnews Magazine QA Report

## Automated code and package checks

- PHP syntax: 39 PHP files passed `php -l`.
- JavaScript syntax: four JavaScript files passed `node --check`.
- JSON: `theme.json` and all four `block.json` files parsed successfully.
- CSS: all stylesheets parsed without syntax errors using `tinycss2`.
- Theme metadata, required templates, direct-access guards, function-prefix uniqueness, text-domain consistency, local asset references, image decoding, site-icon sizes, and the 1200×900 theme screenshot were checked.
- No Custom HTML blocks, shortcode page builder, custom database tables, unsafe deserialization, dynamic execution, bundled font binaries, Bootstrap, jQuery, or proprietary plugin packages were found.
- The final ZIP is extracted into a clean directory and the same validation suite is rerun against the extracted packaged copy. ZIP integrity and the single `globalnews-magazine/` root are checked separately.

## Gutenberg and importer checks

A deterministic WordPress-API mock exercised the complete demo-import routine three times:

- First run: 28 Posts, nine Pages, 43 Media Library records, 24 category/tag terms, 12 comments, four menus, and six block widgets were represented without importer errors.
- Second run: zero new records; all stable records were reused.
- Third run after moving the imported Home page to Trash: zero new records; the Home page was restored.
- A manual edit to imported Home page block content remained unchanged on rerun.
- Imported page, post, and widget content produced 802 Gutenberg block markers with balanced nesting and valid JSON attributes.
- No `core/html` / Custom HTML block was produced.

This mock validates importer control flow, idempotency logic, generated block serialization, menu/widget assignment logic, media path use, and permalink configuration. It does not replace activation against a real WordPress database.

## Responsive and interaction checks

A Chromium/Playwright rendering harness used the theme's actual CSS, JavaScript, representative production markup, and bundled images at:

`320, 360, 375, 390, 414, 480, 768, 1024, 1280, 1440, and 1920 pixels`

The harness found no document-level horizontal overflow, known header/hero/grid/footer collisions, escaping form controls, undersized visible buttons, or broken mobile menu/search/submenu behavior. Slider and ticker pause states updated their accessibility attributes correctly. Reduced-motion emulation suppressed automatic rotation.

## Runtime limitation

The build environment did not provide WordPress core, a compatible database driver/server, or WP-CLI. Therefore theme activation, the actual Admin Import screen, database-backed import, Gutenberg editor opening, WordPress routing, mail delivery, and plugin interoperability were not executed in a live WordPress installation. Those runtime checks remain appropriate staging-site acceptance tests before production deployment.
