Firefox Tools API

The Firefox Tools API topic covers browser automation design for Firefox: navigation, selectors, screenshots, and evidence. Start with a specific user journey and decide what would demonstrate that it worked.

Define the browser context

A Firefox workflow should identify the browser and automation environment, then verify the same user-facing outcome that matters in other supported browsers. Keep test intent shared while allowing setup and diagnostics to describe the actual environment.

Check what your result represents

When a result differs across browsers, compare the page state and the expected behavior before assuming the test or the browser is wrong. A clear assertion and a reproducible fixture make that investigation more useful.

Build a readable flow

• Open the intended page in the chosen session.
• Wait for the meaningful state needed by the next action.
• Use an unambiguous locator for the intended control.
• Assert the outcome and collect the relevant evidence.

Record the configuration that affects the journey, including language, viewport, and relevant preferences. Avoid changing several conditions during an investigation: a smaller controlled comparison makes the cause easier to identify.

Investigate the first divergence

A missing element, an unexpected redirect, and an unavailable browser are different failures. Keep them distinguishable in logs. Save an image when it helps explain the outcome, but retain the event context that tells a reviewer how the page reached that state.

Use the browser automation and selectors guide to improve target selection. The navigation workflow and screenshot workflow provide focused checklists. Compare the broader browser tools API approach before expanding your environment matrix.