PHPAML

Documentation · Chapter 16

Create a release gate the team can trust.

This workshop defines one command sequence whose success is required before a release can be published.

Every lesson starts from the problem, explains the mechanism, then gives a concrete verification.

LESSON OBJECTIVE

What you will be able to do

Define an ordered release gate whose artifacts and decision can be audited later.

Build the gate

Order fast checks first: formatting, static analysis, unit tests, integration matrix, build, then smoke test the artifact.

phpaml — zsh
aml test
aml doctor --production
aml build
sha256sum output/*.zip

Fail on regression

Any failed required step blocks publication. Never convert a flaky test into an ignored warning without owning the uncovered risk.

Keep the evidence

Record commit, tool versions, test result, artifact checksum, deployment target, and smoke result so the decision can be audited.

CHECKPOINT

Before you continue

Can you identify exactly which failed check blocks publication and where its evidence is stored?

SUMMARY

What to remember

  • Testing starts from product and security risks.
  • Each layer proves a different boundary.
  • Production readiness includes recovery, not only deployment.
  • A release gate records reproducible evidence.