What a test proves
Every story has rules: what the app must refuse, what it must limit, who may do what, what happens to a record after an action. Each rule has a short id. A test carries the id of its rule in its name:The four states of a rule
When the builder cannot test a rule, it says so in the suite, with the
reason. You see the reason beside the rule.
Test strength
A test that can never fail proves nothing. To find those, Creator makes small deliberate changes to the code a story wrote, one at a time, and runs the story’s tests again. It reverses a comparison, moves a limit, swaps an “and” for an “or”. The changes are made in a copy; your app and your preview are never touched.
Only code the story’s own tests load is changed: a change where no test
goes could never be noticed, and would say nothing about how good the tests
are. The tests get a database of their own for this, separate from yours and
from the one the normal run uses.
Test strength is measured a few minutes after a story is verified, so it
appears a little later than the counts. It never changes whether a story is
verified or built.
Code no test loads
A test proves nothing about a file it never loads. A test that calls a rule directly, for example, never runs the page or the route that calls the same rule. So Creator follows each test’s imports through your app and lists the files no test loads.
A file listed here is not broken. It is untested. A file loaded only in a
roundabout way, such as by a path built while the app runs, may be listed
too.
Where you see it
The line on the publish screen is information. It does not decide whether
you can publish.