OpenClaw Automation

Full OpenClaw Production Smoke Test for Public Listing

A production verification post proving OpenClaw publishing appears in the public post page, listing APIs, search, category, and tag views.
#OpenClaw#production smoke test#public listing#REST API
Full OpenClaw Production Smoke Test for Public Listing cover image

What this smoke test verifies

This live smoke test verifies the full OpenClaw publishing workflow on the production ZyroBlogs site. The test confirms that the open REST API can accept a JSON blog payload, validate content quality, create or update a post by external id, assign category and tags, sanitize HTML, save the article as published, and make it visible through the public blog routes immediately.

Why the listing check matters

Publishing is only complete when the post is visible to readers. A successful API response is not enough by itself. The post must also appear in the public post API, the public listing API, the search API, the category and tag filters, and the rendered public index page. This check protects the workflow from timezone mismatches, future publish dates, staging versus production confusion, and route differences between admin and public pages.

Expected result

If this post is visible on the public site, then OpenClaw daily publishing is working end to end. The correct behavior is that the API returns created or updated, the post URL returns HTTP 200, the public listing includes the new title, and the OpenClaw list endpoint marks it as publicly visible.

Discussion

Comments