take two.

Free course · Registered members · Lesson 10 / 10

Verify, release and evolve the blog

Deliver a reviewable result and identify what remains before a public community launch.

40 minutes including practiceAll courses

Editorial team: Take Two · Published

Lesson preview

A test matrix

Check public reading, successful/failed login, roles, CSRF, drafts, search, HTML output, concurrent saves and repeated imports. Events add hostile URLs, impossible dates, week and DST boundaries, changed markup and model-invented IDs. Fixtures make these checks repeatable without depending on a changing calendar. Real collection is an additional smoke check rather than the stable suite.

Which checks were run

The download was checked with PHP lint, date/source tests and HTTP tests against a temporary MySQL database. Login, roles, tokens, draft privacy, escaping, edit conflicts and duplicates passed. A real Turismo Roma HTML page parsed correctly. Docker build and authenticated Codex inference were not run; docs/verification.json records them separately. Repeat the checks on your own result after changing the project.

What to check as you practise

  • Reported results backed by checks.
  • Deployment and secrets outside model work.
  • Version limitations stated explicitly.

Continue with the full lesson

Register free to access the complete explanation, examples, exercise and commented answer. This preview stays open to everyone.

Register / sign in free →

Workshop files · Version 1

The reference project

Download the complete blog, English and Italian instructions, SQL schema, agent contracts, fictional fixtures and tests. The sample blog interface is in English. This is a local learning project: password recovery, email verification and MFA remain extensions before opening it to a public community.

Download the blog project (ZIP) →

Free download. Full lessons require a free Take Two account. Codex access depends on your own plan.

Sources and further reading