CMS testing · Verified pass

AI CMS testing across the complete publishing workflow

Mira logged in, found the homepage, edited three content blocks, saved and published the page, then returned to the public site to verify the release.

Visible result

The public page showed all three changes, status “Live,” and release ATLAS-HOME-042.

Recorded · Pass

Controlled fictional CMS and publication. No customer data was used.

The exact instruction

A business goal, not a click script

“Update and publish the Atlas Journal homepage in Atlas CMS. Start on the public site, open Admin login, and sign in with admin@atlas.test and password atlas2026. From the Pages list, edit the Homepage. Set Hero headline to ‘Ideas for a brighter city’, Introduction to ‘Meet the people and places reshaping how our cities feel.’, and Featured headline to ‘A garden grows above the station’. Save the changes, publish them, then view the page. Pass only when the public page visibly shows ‘Live’, both new headlines, and release ‘ATLAS-HOME-042’. Do not treat a saved draft or the ‘Homepage published’ message alone as success.”

CMS workflow testing

The test followed the same path as an editor

Atlas Journal public homepage before the CMS test
1. Start on the public page

Mira opened the published article site before entering the admin area.

CMS homepage editor with editable content blocks
2. Edit the page blocks

It changed the hero, introduction, and featured-story headlines.

Live public homepage showing the content published by the automated CMS test
3. Verify the live result

Only the changed public page and its release marker completed the test.

  1. 01

    Open Admin login and authenticate

  2. 02

    Find Homepage in the Pages list

  3. 03

    Update three separate content blocks

  4. 04

    Save the draft

  5. 05

    Publish the homepage

  6. 06

    View and verify the public release

What this proves

Mira can operate a multi-page CMS workflow

The recorded run covered authentication, navigation, form editing, saving, publishing, and independent verification on the public page.

What it does not prove

Every CMS uses the same path

This controlled example is not a blanket compatibility claim. A real project receives its own start URL, credentials, content rules, and visible acceptance criteria.

Video description and transcript

The film opens with the question “What about longer and more complex websites?” and states that Mira follows instructions, long or short.

The visible instruction lists opening the website, logging in as admin, choosing the homepage, editing its title and content, saving, publishing, and confirming the changes are visible. The recording then follows these actions across the public page, login, page list, editor, and publishing confirmation.

The film ends on the changed public homepage with the answer: “Everything the user can do, we can do.”

What should remain true after your next content change?

Describe the outcome. Mira checks the workflow and returns the evidence.