Beta

What the Beta page is

The beta runs for twelve weeks. Each week opens one test of an integration or a feature in your area, and each day offers two or three small tasks of about five minutes. The page only shows to people in the beta, in the sidebar as Beta.

• This week’s test: the main one. It opens on its day and stays open.
• Today: small tasks, new ones each day.
• Assigned to you: extra tests we asked you to take on, on top of your camp’s.
• What you’ve tested: everything you’ve logged, with your verdicts.

Your camp

The first time you sign in during the beta, after your name, Stoaken asks How will you use Stoaken? Pick the camp closest to your work: Agency, Designer, Developer or Automater. It decides your weekly tests and your daily tasks.

Change it any time on Beta camp in Settings. What you already logged stays yours; your next tasks come from the new camp.

Why your test names a tool

Some tests work with any of several tools: a code host, an AI coding tool, a chat app. So that every tool gets tried, people in the same camp are given different ones. If you skip a test, or its week ends before you did it, it passes to someone else, and you won’t be given that tool for that test again. Changing camp passes on your open tasks too.

Done, and how it went

1. 1Follow the steps on the task (its guide link opens the integration guide).
2. 2Press Done. How did it go? asks for one of four: Worked, Partly worked, Broken or Confusing.
3. 3Add a note if anything surprised you, and a screenshot if it helps (PNG or JPEG, up to 2 MB).
4. 4Press Save.

Can’t do it? Press Skip. Changed your mind? Undo or Change on a logged task. Once a skipped task has gone to someone else, it can’t come back to you.

A Broken verdict with the exact error is the most useful thing you can send. Only you and Stoaken’s team see your notes and screenshots. The team also sees each task you were given and what became of it: done, skipped, or passed on to someone else.

When you can’t complete a task

Stuck on a step? Press I can’t complete this on the task, beside Done and Skip. What stopped you? asks for one of four: a bug (something doesn’t work), an error (you saw an error message), the instructions are wrong, or the instructions are unclear.

• For a bug or an error, say what happened: what you did, what you expected, and the exact error. For the instructions, a note is optional.
• Add a screenshot if it helps: drop it, paste it or pick it (PNG or JPEG, up to 2 MB).
• Press Send.

The task stays open and counts as neither done nor skipped, so nothing passes on because you were stuck. The card shows Stuck with when you reported it; Edit sends a new report in place of the old one (it counts toward the ten an hour), and Withdraw takes it back if you got past it.

When Stoaken’s team has fixed it, the card shows Fixed: try it again with a note on what changed, and we get in touch to ask you to retry. Marking the task done or skipping it closes your report. Still stuck after the fix? Press Still stuck and send a new one.

Tasks Stoaken notices

Some tasks show Stoaken saw this happen when your own account did the thing after the task was given to you: you made, used or revoked an API key, added a webhook, proposed a release from Figma or Penpot, approved, rejected or scheduled one, commented or suggested a change, made a group, policy, invitation or share link, connected Penpot, saved tokens or shared a listing. One action ticks one task. A test that names a tool ticks itself only when that tool leaves its own mark (a Slack, Teams, Discord, Jira, Linear, GitHub or Bitbucket webhook); for the others, and for AI tools, you mark it done. Stoaken still asks for your verdict: seeing it happen doesn’t say whether it worked for you.

When a new test opens

The bell shows a notice when your week’s test opens. Beta notices are in the app only; there are no beta emails.