The test shows what the rule would do
The test is already on when you open the editor (the flask button, Live test, turns it on and off). The result appears just below the top bar; click it to open What the test would do, with the path taken and what would change. If the rule should spend 2 Mana, look for that there. In tests, dice always give the same result so you can compare attempts; Roll again draws new numbers. The test uses the sheet's current values: to try another value, change it on a test sheet. In On roll rules, the Test event section lets you choose where the roll came from and its total.
The test is only a simulation: it does not spend points, give cards or save anything to the sheet. Save stores the rule, which takes effect when it is actually used. In this page's examples, Save changes only the example.
In tests, Ask answers by itself: 0 for number questions, yes for confirmations and the first option in lists. Choose also picks by itself. That is why the healing example shows Health 8 staying at 8: the simulated answer was 0. To test real answers and the Cancel button, use a test sheet.
A short list before saving
In the bonus example, Strength 3 should give +2 and Strength 2 should give 0. Make similar checks for your rule. Remember that real actions really change the sheet; try them on a test sheet first. To make one, go to Characters, open the character's Sheet actions menu and choose Duplicate: the copy gets (copy) in its name and you can change it freely.
- Test one case where the answer is yes and one where it is no. Also test the exact limit: for example, Mana equal to 2 for an ability that costs 2.
- If the rule changes a field, check that it is the right one: current Health or maximum Health, for example. If it uses a list, also check the case where it is empty.
- If the rule uses Ask or Choose, answer and cancel for real on a test sheet. The test's automatic answer does not cover every case.
- If Review issues (with the number of problems) appears in place of Save, click it: the editor selects the step with the problem so you can fix it. A step with no line coming from the start never runs: connect it or delete it.
- Save the automation and, if the surrounding screen also has a save button, save there too. Then check the result on the test sheet. If a step fails midway, whatever was spent before it is not refunded automatically.
If you open an older rule
The editor may convert an older rule to the new format and leave notes about what needs review. Read the notes and test before saving. Until you save, the old version stays in use.
The Join and Stop steps may appear in older rules, but they are no longer in the step list. You do not need them: a path ends on its own when there are no more lines. If an old Join waits for paths that never happen together (such as the Yes and No of the same If), the rule gets stuck there; replace it with direct lines.