QA Testing Dental Notes App
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted1 hour ago
Dental Note AI is a web application that generates clinical notes for dental practices. It is built on Django and React, hosted on Heroku, and is about to open its beta to its first practices in Australia. I am the founder, and I have been doing the release testing myself. I now need a careful, methodical tester to take over the scripted part of that work so I can focus on clinical and product judgment.
What the work is
- Run a written checklist against the staging site before each release and against the production site after it. The checklists exist as self-saving HTML trackers: you tick each item, write what you saw in plain English, and save the dated file. Roughly two to three hours per release.
- Verify individual fixes on staging where the pass condition is written on the GitHub card, and post a short plain-English comment with the result. No code reading is required.
- Walk the sign-in, session, sign-up and password-reset journeys on a fixed fortnightly cadence, and a monthly pass on Chrome, Edge, Safari and one tablet.
- Reproduce incoming bug reports from practices so the developers receive exact steps.
What the work is not
- No code review, no clinical judgment on note content, no access to real patient data. Test workspaces and test patients only.
What I need from you
- Written English that is precise about what you saw, not what you assume. If a screen looks right but the record behind it is wrong, I need you to notice the difference.
- Comfort with browser developer tools (Network tab, Local Storage) at a reading level; I will show you what to look for.
- Reliability on a fixed weekly schedule of your choosing, plus availability for release days, agreed in advance.
- Familiarity with GitHub issues as a reader and commenter.
How we work
- All coordination in a Freelancer group chat with the two developers and me; each card on GitHub carries its own record. Short written updates at the end of each session listing exactly what you ran and what you found.
- Start after the beta goes live, expected early October, with a first production sweep as the opening task and a one-month review of scope and hours after that.
To apply, tell me in three or four sentences about a time you found a defect the developers hadn't seen, and how you wrote it up. Please also include your time zone and the days and hours you can commit.
What the work is
- Run a written checklist against the staging site before each release and against the production site after it. The checklists exist as self-saving HTML trackers: you tick each item, write what you saw in plain English, and save the dated file. Roughly two to three hours per release.
- Verify individual fixes on staging where the pass condition is written on the GitHub card, and post a short plain-English comment with the result. No code reading is required.
- Walk the sign-in, session, sign-up and password-reset journeys on a fixed fortnightly cadence, and a monthly pass on Chrome, Edge, Safari and one tablet.
- Reproduce incoming bug reports from practices so the developers receive exact steps.
What the work is not
- No code review, no clinical judgment on note content, no access to real patient data. Test workspaces and test patients only.
What I need from you
- Written English that is precise about what you saw, not what you assume. If a screen looks right but the record behind it is wrong, I need you to notice the difference.
- Comfort with browser developer tools (Network tab, Local Storage) at a reading level; I will show you what to look for.
- Reliability on a fixed weekly schedule of your choosing, plus availability for release days, agreed in advance.
- Familiarity with GitHub issues as a reader and commenter.
How we work
- All coordination in a Freelancer group chat with the two developers and me; each card on GitHub carries its own record. Short written updates at the end of each session listing exactly what you ran and what you found.
- Start after the beta goes live, expected early October, with a first production sweep as the opening task and a one-month review of scope and hours after that.
To apply, tell me in three or four sentences about a time you found a defect the developers hadn't seen, and how you wrote it up. Please also include your time zone and the days and hours you can commit.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.