← Recipe: replay declarative motion

5. Check and run

luastra/motion · stable UI identity · about 15 minutes
left → right → left

Automated checks prove the descriptor and state contracts; the preview separately proves visible scheduling in this browser.

When to use it

Run from motion-recipe after all three files are saved.

  • check and test must report PASS with one passing test.
  • Each press updates Luau once; app.render is not called for every animation frame.
  • Enable reduced motion in the operating system or browser and reload: content must appear immediately in its final position.
  • The animation must never be the only indication of the run or direction; the status text carries the same meaning.

Focused example

luastra check
luastra test
luastra run
# Expect Run 0: from left.
# Press Replay from right, then expect Run 1: from right.

Complete inventory

View all pages in Recipe: replay declarative motion
← Previous: 4. Replace tests/smoke.luauNext: 6. Understand the boundaries →