← Back to articles
Technology

Run Acceptance Tests Without Developers

Run Acceptance Tests Without Developers

You handed acceptance testing to non-developers, yet engineers still get pulled in to answer questions about steps and fix environment problems. This is a common scene before a release. The cause is rarely the testers. It is that steps, environment, and a reporting path are not all in place. This article lists what PMs, QA, and support staff need to run acceptance tests on their own.

Why acceptance testing keeps coming back to developers

The reasons usually fall into three groups.

  • Steps live in someone's head: "Log in, go to that screen, use it normally" is assumed to be enough
  • The environment is unstable: no test account, stale data, or someone else used it first
  • The reporting destination is unclear: testers find a bug but do not know where to write it, so it ends up as a chat message

Fix these three in advance, and developers only appear when something actually needs fixing.

1. Steps: write them so anyone gets the same result

Write the steps at a level where someone seeing the screen for the first time will not get lost. Use a format like this.

Example of one step entry

  • Precondition: logged in as test account A (role: regular user)
  • Action: open "Orders" and press "Cancel" on the first row
  • Expected result: a confirmation dialog appears. After "Yes", the status becomes "Cancelled"
  • Check: returning to the list still shows "Cancelled"

Always write the precondition and the expected result. Without an expected result, a tester who sees something odd may stop and assume it is the spec.

2. Environment: make it checkable in five minutes

To cut the time lost to environment problems, prepare a pre-test checklist.

  • The test URL, and how to tell it apart from production (a banner at the top, the domain name)
  • A list of test accounts, with where roles and passwords are stored
  • The state of the test data (as of when, how to reset it, and who does it)
  • Assignment of areas when several people test at once
  • Which external integrations are safe to use (payments in test mode, email limited to certain recipients)

A frequent failure is several people sharing one account and one data set, so results disagree. Giving each tester their own account removes most "cannot reproduce" reports.

3. Reporting path: pick one place to write

Reporting is where acceptance tests get messy most easily. When reports scatter across chat, email, and spreadsheets, you get duplicates and gaps. Decide these rules up front.

  • Use exactly one destination (anything found in chat or in person must be copied there)
  • Minimum fields: which screen, what you did, what happened, and what you expected
  • A screenshot is required, with the problem area marked
  • Priority uses a single question: does this block the release? (yes or no)

Common sticking points and fixes

  • "I cannot tell if it is the spec": write expected results in the steps and say explicitly that reporting when unsure is fine. Too many reports is safer than too few
  • "Cannot reproduce": make it a habit to include the steps and the account used in every report
  • Mixing with production inquiries: mark acceptance test reports so it is clear they come from the test environment

Putting it into practice with Bugoon

Bugoon lets people report bugs directly in the browser after you add a single tag to your site. It suits the job of funneling acceptance test reports into one path.

  • Testers report from the on-screen widget. Annotated screenshots and a record of the steps just before the report capture what they did without relying on prose
  • Each report carries environment details such as URL, browser, and OS, which cuts the back-and-forth of asking where it happened
  • Reports connect to GitHub Issues, and a kanban board shares progress. The iOS and Android apps also accept reports, so mobile acceptance tests are covered

Automatically sorting test-environment and production reports would make this even easier to handle, but for now separating them by project is the practical approach. Start small by putting steps, environment, and a reporting path in order.

Streamline bug reporting for your team.

Bugoon is free to get started. Add one line of code to your site and transform how your team handles bugs.

Get Started