AllComputer GigsCreative GigsCrew GigsDomestic GigsEvent GigsLabor GigsTalent GigsWriting Gigs
QA test: Orbit beta: notifications — 2026-09-17
Estimated duration
~1h
Deadline
Tue, Sep 22, 2026
Location
Remote only
PRICING
$21 fixed
USD
per approved result
DESCRIPTION
One-time QA test run for https://github.com/emma2bean-bot/orbit-releases/releases/tag/v0.2.11.
Submissions are reviewed automatically. $21.00 is released per accepted submission.
What you must do to be paid
Before you apply
- Access to a device that can open https://github.com/emma2bean-bot/orbit-releases/releases/tag/v0.2.11
- Mac on macOS 14 or newer
- Apple Messages set up on that Mac with real conversations
- Can record screen with narration
- Profile country must be one of: US, CA, GB, AU
Task
https://github.com/emma2bean-bot/orbit-releases/releases/tag/v0.2.11Orbit is a small Mac menu-bar app that reads your Messages on your Mac (locally, nothing leaves your computer) and helps you keep up with friends you have not replied to. You need: a Mac on macOS 14 or newer, Apple Messages set up on that Mac with real conversations, and permission to record your screen. Download Orbit.dmg from the page above, open it, drag Orbit to Applications, and open it from Applications. It is a beta signed by the developer, so macOS will not block it. Record your screen with narration the whole time. Privacy: you may blur or skip showing message contents; we only need to see how Orbit behaves. When done, quit Orbit from its Settings and drag it to the Trash if you like.
THIS RUN: notifications through a day. Set Orbit up with THREE notification times spaced across the next few hours (for example one 15 minutes from now, one 2 hours later, one 4 hours later). Allow notifications when macOS asks. Keep your Mac awake and Orbit running.
- At each chosen time: did a desktop banner arrive (a real banner, not just something in Notification Center)? Note the exact time of each.
- Click one banner: does Orbit open on today's cards?
- Handle everything Orbit shows you before the next time (reply, no reply needed, or Later). At the next time, did you get a notification anyway? (If nothing is left to show, you should get none.)
- Put the Mac to sleep across one of the times, wake it up: did you get one notification, several, or none?
- Quit Orbit and reopen it: any duplicate notifications?
- Open Settings in Orbit and read the notification-times section. Does the text match what actually happened? Report: a table of chosen time / what arrived / when, plus answers and bugs. Video can be a few short recordings rather than one long one.
Submission requirements
Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.
Each required test item must be backed by video evidence: a timestamped range in your recording or a short clip.
- 1A real desktop banner at each of the three chosen timesNote the exact time each banner arrived, or that it did not.
- 2Clicking a banner opens Orbit on today's cardsShow what happens when you click one.
- 3No notification when everything was already handledHandle all cards before a chosen time; say whether a banner still came.
- 4Sleep across a time, and quit/reopen: how many notificationsOne, several, or none, for each case.
- 5Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
- 6Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
- 7Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
- 8Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 512 MB, plus at least one representative screenshot.
- 9Map every attachment to the reportIn the same chat message as each upload, explain what every attached file shows and which tested step or finding it supports.
- 10Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
- 11Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.
REQUIREMENTS
- •
Only submit evidence you captured yourself during this run