5. Check before running
luastra/ui · app.render · app.handle · about 15 minutesluastra check → luastra test
First validate the manifest and strict module graph, then execute the declared behavior test.
When to use it
Run these commands from beginner-counter after all three files are saved.
- check must report result=PASS and project=dev.luastra.beginner-counter.
- test must report tests=1 and passed=1.
- A check error names the source or manifest problem. Fix its first concrete path or line before interpreting later errors.
- If test fails, read the assertion message: it names the product behavior that no longer matches the code.
Focused example
luastra check luastra test