Brief Buck
Start a campaign
✦ Task type · Website testing

Nobody tests the unhappy path, and it is where people leave

Forms are tested by filling them in correctly. Customers fill them in incorrectly, which is the only circumstance under which your error messages are ever read.

Post this taskThinking of taking one instead?

Every form has two paths and only one gets tested. The unhappy path is where abandonment happens, and it is entirely composed of things nobody wrote deliberately.

What to put in the public brief

Keep the URL and the specific failure list private.

What to put in the private instructions

  1. List the failures to attempt, one per line

    Specific and realistic. A name with an apostrophe, a number with spaces, a mismatched confirmation, an oversized upload.

  2. Ask what happened to their correct entries

    Whether the form kept them. Clearing valid fields on one error is the single most abandonment-causing behaviour a form has, and it is often invisible to the team because they retype quickly.

  3. Ask them to press back after a failed submit

    And report what they find. Lost data at this moment ends the session.

  4. Ask whether they could tell what to fix

    Not whether the message was polite. Actionability is the property that matters.

Proof worth requiring

Ask for

The recording, a note per failure on what the form did, and whether previously entered data survived.

Do not ask for

Real personal data as test input. Invented values are sufficient for every case here, and asking someone to submit their own address to trigger a validation error is collecting data you have no reason to hold.

When this task type is the wrong tool

If people abandon before reaching a form field, the problem is earlier and a first-impression test will find it.

If the form works and people still do not complete it, you are looking at what is being asked rather than how, and that is a different conversation with the same customers.

Common questions

What failures should I test?

The ones real people produce, not the ones a QA plan lists. A phone number with spaces, a name with an apostrophe, a postcode from the wrong country, a password that meets a rule the form never showed, and the back button after a failed submit. That last one destroys more forms than any validation rule.

What reward is fair?

Eight to sixteen dollars. Deliberately failing a form repeatedly is more tedious than filling it in, and tedium is what you are compensating.

Why not just check the error strings myself?

Because the failure is rarely the wording. It is that the message appears above the fold while the broken field is below it, that the form cleared four correct fields to punish one mistake, or that the error is announced nowhere a screen reader will find it.

Should I test accessibility here too?

Ask about it explicitly if so, and consider a separate campaign with a screen reader user. Error announcement is one of the most commonly broken things in accessible forms and it is invisible to sighted testing.

Thinking of taking this task?

The same job, from the other side. Rewards are set by the poster, so treat these as the range this task type usually sits in rather than a promise.

Usually pays
$8 to $16
You need
Any device with a browser
Proof expected
A recording, and a note on what the form did for each failure

Use invented values, never your own real address or details. You are deliberately breaking the form; that is the task rather than a mistake.

Create a worker account

Test your errors

Set the reward and how many testers you need. Workers reserve a spot; your URL and the failure list stay private until they do.

Post this task