Keep a flow going past a failed check

expect.soft(subject, name)

• subject — what to check, the same as for expect
• name — optional label that QA Wolf records with the failure

import { expect, flow } from "@qawolf/flows/web";

export default flow(
  "Review an invoice",
  { target: "Web - Chrome", launch: true },
  async ({ page }) => {
    await page.goto(`${process.env.BASE_URL}/invoices/42`);

    await expect.soft(page.getByRole("heading", { level: 1 }), "Invoice heading").toHaveText("Invoice 42");
    await expect.soft(page.getByTestId("invoice-total"), "Invoice total").toHaveText("$120.00");

    const pay = page.getByRole("button", { name: "Pay" });
    await expect(pay).toBeEnabled();
    await pay.click();
    await expect(page.getByText("Paid")).toBeVisible();
  },
);

​

When to use soft checks

• Use expect.soft for checks that nothing later in the flow depends on, such as several values on one page.
• Use expect for a check that a later step relies on, such as a button the flow clicks next.
• Don’t use expect.soft inside a loop. A check that fails on every iteration records a failure each time, and an attempt keeps at most 100 failures.

​

Name each check

​

Platforms and limits

• Platforms — web, iOS, Android and Windows flows, through the expect you already import from @qawolf/flows. In Windows flows, expect.soft dispatches on its subject the same way expect does. Node flows (@qawolf/flows/cli) don’t have expect.soft.
• Failures per attempt — at most 100. The attempt’s error counts the rest as “…and N more”.
• Call only — expect.soft(subject, name) has none of expect’s properties, such as poll, configure or extend. In web and Windows flows, expect.configure({ soft: true }) throws. Use expect.soft instead.
• Timeouts — each failing soft check still waits the full expect timeout before QA Wolf records it.