Tests
A line set before you start, results, and the verdict
Learn › Tests checks a belief against a line you set before the test starts, so nobody argues with the result.
- New test: what you expect, what you count (pre-payments, sign-ups…) and where it is counted from (logged by you, your payments CSV, or a web form's sign-ups), the line ("10 or more by 15 Oct"), what a pass moves the belief to, your own call, and what you'll do if it passes or misses. Save as draft, or Start and lock: from then on the line, the metric, what a pass moves and your call cannot change. Only the deadline moves, and the move is logged with its reason. Draft it with Mind (1 credit) writes one from the belief's weakest evidence.
- Results: log each one by hand, or import your payments CSV (for example Stripe's payments export): you see the first rows and confirm which columns hold the email, amount, date and reference first. Importing the same file again adds nothing, and a row matching a result you logged by hand within two days counts once. Results are voided with a reason, never deleted.
- The verdict is recorded once the deadline day has passed in your time zone: passed or missed against your line, with your call checked. A pass is the only way a belief reaches Pays. Results coming in never move a belief by themselves. A verdict never changes; a correction is a new verdict with its reason.
- After a verdict, a decision is drafted from your own "if it passes / if it misses" line. Nothing is logged until you press Log it.
Your calls on the Tests page shows how many of your calls were right; a pattern shows after ten. Nothing reads your Stripe account: pre-payments come from what you log or import.