Skip to content
certyn logoCertyn
Start Free
RecipesDoc

Act Out a Customer's Whole Workflow, Find Awkward Steps and Missing Features

Certyn plays one kind of customer from start to end and reports bugs, awkward steps and what that customer would miss.

For teams who want to see the app through one kind of customer, not only check each function.

Your setup

  • A web app for teams, with projects, teammates, permissions and reports.
  • A customer you care about, for example an agency with five clients.
  • A test account that can create projects and invite people, on a test environment.

Say this to Certyn

Act as a marketing agency with five clients. Set up a project per client, invite two teammates, give one of them access to only two clients, and prepare a monthly report for one client. Tell me where it is slow or confusing, and what an agency would miss.

What Certyn does

  1. If no test account is saved, opens the sign-in form (sign_in).
  2. Starts an explore run with your story as the goal (app.run.create type explore), for example 90 minutes.
  3. Writes a checklist from the story: each step, and what the agency needs there.
  4. Uses realistic data with names it can find again, for example five named clients.
  5. Invites teammates at its own run inbox, one address per teammate. It reads each invite email, accepts it, and signs in as that teammate to check what they can see.
  6. Counts the steps of each task, and notes where it had to guess or retype, or got no feedback.
  7. Files a bug when a step fails or blocks the task, and an improvement when a step works but is awkward, or when a capability your message asks for is missing.
  8. Writes the run report: the story step by step, what worked, and the gaps.

What you get

  • Bugs and improvements in review, with screenshots and steps.
  • A run report that walks through the customer's work.
  • On request, test cases for the steps that worked.

Limits

  • A missing feature is filed only when your message, the wiki or a spec says the customer needs it. Otherwise it is listed in the report. Write the customer's needs in your message.
  • Awkward steps are judged from facts such as step counts and unclear labels, not from real customers.
  • The run creates real data. Use a test environment, and ask Certyn to delete what it created.
  • A run waits at most 3 minutes for each email. If invites only go to your company's domain, give extra test accounts instead (Several Roles).
  • A run has up to 240 minutes. Split a long story into several runs.
PreviousDashboard, API and CSV Export Show the Same NumbersNextTwo Test Organizations, One Cannot See or Change the Other's Records