Testing Blueprint systems before they ship

Blueprint systems are easy to break without noticing: a renamed variable, a struct that changed, a reference to another folder that works on your machine and fails on the buyer's. Every Rookspire release goes through the same gate before it ships.

What the gate runs

1. A full rebuild of every Blueprint from its script, so nothing depends on an edit made by hand.
2. Compile with zero errors and zero warnings.
3. A reference check that refuses any asset pointing outside the product's own folder. This is what keeps each system installable on its own.
4. Every map run for 30 seconds with zero runtime messages in the log.
5. Functional tests in Play In Editor, one per behaviour that matters.

A test that never failed proves nothing

A new test is written to fail first: the behaviour is broken on purpose, the test must go red, then the fix makes it green. A test that has only ever passed may not be testing anything at all.

And a person, at the end

Some things only a person can see: whether a drag feels right, whether a prompt is readable over a bright sky. Each release also gets a manual run through its demo map.