Toaster

Toaster / Use cases

Bug tracking from the first report to an accepted fix

Developers know what needs fixing; reviewers know what to retest. The description, evidence and decisions stay attached to the issue.

Create a workspace

For developers, testers and team leads who need a clear next action for each issue.

How to organize the workflow

“It does not work” rarely provides enough context. “Done” does not tell you whether a fix has been tested. Toaster connects development with verification and preserves who made each decision.

  1. Describe a reproducible problem

    Explain what happened and what you expected. Add steps, the page URL, priority and relevant reproduction conditions.

  2. Choose an owner

    Assign a developer. The issue appears in their work queue while the shared project sheet keeps the team view.

  3. Send the fix for retest

    After development, send the issue for review. The reviewer repeats the original scenario and evaluates the result.

  4. Accept or reopen with a reason

    Accepting the fix closes the issue and records a successful retest. If the problem remains or returns, reopen it with an explanation.

Illustrative workflow, not customer data

A bug report a developer can act on

Steps
Open the cart, choose two products and change the first product quantity from 1 to 2.
Expected
The total includes the new quantity.
Actual
The quantity changes, but the total stays unchanged until the page is refreshed.
Context
Include the browser, device and tested version. Attach a screencast showing the actions and result.

Before you start

Can we report bugs outside a test run?

Yes. Create standalone project issues or link an issue to a check result.

Does it automatically capture console and network logs?

This workflow uses manually attached evidence. Automatic browser console or network capture is not part of the workflow described here.

What happens to earlier reviews when an issue is reopened?

Previous verification decisions remain in history. The new decision records the current outcome and the reason for reopening.

Related workflows

Website acceptance without scattered spreadsheets

Bring design, QA and client feedback into one website acceptance sheet. Assign owners, attach screenshots and videos, and keep a history of fix verification.

Testing checklists with a history you can trust

Organize manual QA with testing checklists, sections, run results and linked issues. Keep previous checks and execution history in your project workspace.

Try it on your own project

Create a workspace, add a project and invite your team. Start with one real workflow.

Create a workspace