Failed Status

Choose what status a Test Step reports when it fails.

Failed Status sets what happens when a Test Step does not meet its expected result. Use it when a mismatch should warn or pass instead of failing the whole Test Case.

Most steps default to Failed. Change the advanced field when the journey should keep going with a softer outcome.

Options

Status	What it means
Failed (default)	The step fails. Treat it as a problem that needs attention.
Passed with warning	The step did not match, but the Test Case continues with a warning.
Passed	The step is treated as successful even when the check did not match.

When to use each option

• Keep Failed for assertions that must be true, such as login success or payment confirmation.

• Use Passed with warning for optional UI, third-party banners, or soft quality signals.

• Use Passed when the step is informational and should never stop the Run.

Pro tip: Prefer fixing the Element or expectation before softening Failed Status. Soft outcomes help optional checks; they should not hide a broken happy path.

Related

• Timeout Override

• Element states

• Understand your results