What is a smartwatch or fitness tracker beta test?

A pre-release or early-access trial where a manufacturer lets real users wear an unfinished watch, tracker, firmware or app and report faults before general release. The tester's job is to find problems in real use and describe them so engineers can reproduce them.

How can I check a smartwatch's heart rate or GPS accuracy?

Compare it with a reference you trust: a chest strap for heart rate at a steady effort, and a route you have measured for GPS distance. Start both together, keep the conditions the same each time and photograph the watch and the reference together. It is a comparison for your own testing, not a clinical or lab result.

Can I use a beta smartwatch to make health decisions?

No. Beta hardware and software can be wrong, so treat every reading as unverified. This guide is not medical advice. Don't change medication or treatment because of a beta device, and talk to a health professional about any concern.

Is BetaSuite a TestFlight alternative?

No. BetaSuite: Tester's Toolkit is not an app-beta tool and has no connection to TestFlight or Google Play testing tracks. It is for people who beta test physical products in the field and need timestamped evidence and a report for the manufacturer.

Is BetaSuite a subscription?

No. It is a one-time purchase from the App Store or Google Play, with no subscription, no ads and no account. Each store sets the price.

How to test a smartwatch or fitness tracker

To beta test a smartwatch or fitness tracker well, compare it against a reference you trust (a route you have measured for GPS, a chest strap for heart rate), repeat the same checks each week and record the conditions every time. BetaSuite: Tester's Toolkit (betasuite.app) is an iPhone, iPad and Android app built for this: it burns the date and time into every photo and video, and its dual recording captures your phone's screen and the watch together. It doesn't read the watch's sensors, and nothing here is medical advice. The checklist below works with any tool, and there is a free 12-step protocol to import.

Updated 2 October 2026 · Written by Goodfield Studio, the maker of BetaSuite

What to test in a wearable beta

Start with pairing, sync and battery, because every other result depends on the watch staying connected and charged. Then work through the sensors and features, and repeat anything that fails so you can say how often it happens.

Area	What you are checking	Evidence worth capturing
Set-up and pairing	Time to pair with the phone and app, the profile and permissions set-up, and whether pairing survives a restart of the watch or the phone, or an update.	A screen recording of the pairing, and a screenshot of any error with the time visible.
GPS accuracy	Distance and route against a reference on a route you know well. Lock time from a cold start. Behaviour under trees, near tall buildings and in tunnels.	A photo of the watch's summary next to the reference, and screenshots of both tracks.
Heart rate	Readings against a chest strap at a steady effort, and how well the watch follows a change (intervals, a hill, a stop). Cold weather and a loose strap matter too.	A photo of the watch and the strap's display together, with the time visible.
Activity and workout tracking	Start, pause and stop, auto-detect and auto-pause, laps, and whether a saved workout matches what you did. Counting 100 steps by hand is a quick check on step counts.	A screenshot of the workout summary and a note of what you did.
Sleep tracking	Whether bedtime, wake time and any wake-ups roughly match what you remember, across several nights. Treat it as an estimate, not a measurement.	A dated screenshot of each night's summary, with a note of your own estimate.
Battery life	Battery against the maker's claim, on the settings you actually use (always-on display, GPS use, notifications). Start from the same level each time.	A dated tally of the battery percentage at fixed times, and the settings you used.
Sync reliability	How quickly workouts, sleep and settings reach the phone app, and whether anything is missing, duplicated or stuck after a Bluetooth drop.	Screenshots of the app and the watch side by side with the time visible.
Notifications	Delay between the phone and the watch, duplicates, missed alerts, and whether actions such as dismiss and reply work. Check with the phone locked and with Do Not Disturb on.	A dual recording of the phone's screen and the watch together.
Water resistance	Only within the rating and the conditions the manufacturer states. Check the screen, buttons and touch afterwards, and look for any moisture under the glass.	A photo of the watch before and after, and a note of what it went through.
Screen, buttons and comfort	Readability in sun, touch response with wet hands, the feel of the buttons, strap comfort and any skin irritation over a long wear.	Photos of the screen outdoors, and a note of how long you wore it.

Not medical advice. Heart rate, sleep, blood oxygen and similar readings from a wearable are consumer estimates unless the manufacturer says otherwise, and a beta device can be wrong. Comparing a watch with a chest strap shows how the watch behaves in your test, not whether it is clinically accurate, and neither this guide nor BetaSuite can diagnose anything. Don't change medication, training or anything else about your health because of a beta device, and talk to a health professional about any concern. Take the watch off if it irritates your skin or feels too hot, and don't test emergency features such as SOS or fall detection unless the brief says how, because they can contact real emergency services.

A repeatable accuracy test

"It seems about right" can't be compared from one week to the next. This test can, so you can tell whether a firmware update or a setting made things better or worse. It is a relative test, not a lab result.

Choose a route you can measure on a map or with a measuring app (a lap of a park or a running track), and use the same one every time. Write down the length your reference gives.
Wear the watch snugly on the same wrist, and a chest strap if you have one, with the strap's display or app in view.
Wait for the watch to lock GPS before you start, and note how long that took.
Start the watch and the reference at the same moment. Do a steady effort for ten minutes, then a few short harder efforts with a rest between (only as hard as is safe for you), so you test both steady and changing heart rate.
At the end, photograph the watch and the reference together, with the time visible, and screenshot both app summaries.
Work out the result: distance error % = (watch distance − reference distance) ÷ reference distance × 100. Note the heart-rate gap during the steady part and after each effort.
Repeat after every firmware or settings change, in the same conditions where you can, and log the result in the same row each time.

Tree cover, tall buildings and tunnels change GPS results, so repeat on an open route before you blame the watch. A second watch is a comparison, not a reference: if the two disagree, you know one is off but not which.

Conditions to record every time

A fault you can't reproduce is just a story. Log the same details every time so engineers can line your problem up against everyone else's.

Record	Why it matters
Date, time and time zone	Engineers can match your report to the watch's own logs and your account, if the manufacturer collects them. Note it again after travel across time zones.
Wear	Which wrist, the strap type and how tight it is. Fit changes optical heart-rate readings a lot, and so do cold and sweat.
Activity	The type of activity, how long, how hard and the route. Use the same activity and route where you can.
Weather and surroundings	Temperature, rain, open sky or tree cover, and buildings nearby. All of them affect GPS and heart-rate results.
Reference devices	What you compared against (a chest strap model, a measured route, a second GPS device) and how it was set up.
Watch settings	Always-on display, GPS mode, heart-rate sampling, notifications, power saving and any custom settings. Battery percentage at the start and end of each check.
Phone	Phone model and operating system, Bluetooth on or off, and background permissions for the watch's app. Many sync problems are phone settings.
Software	Watch firmware and app version. Note them again after every update.

BetaSuite adds the date and time to every photo and video for you, and can add GPS, live weather, the season and the time zone, each of which you can turn on or off in Settings.

A first-week routine

Adjust this to your brief. The point is to do the same checks in the same order, so a change in the result means something changed in the watch.

When	Focus
Day 1	Charge, pair and set up the watch. Note the firmware, the settings and the battery level. Photograph it on your wrist. Take a first walk to check GPS lock time and the basics.
Days 2–3	Run the accuracy test on your measured route, with a chest strap if you have one. Check workout start, pause and stop. Count 100 steps by hand once.
Days 4–5	Test notifications with the phone locked and unlocked. Check sync after each workout, and after a Bluetooth drop (walk away from the phone and come back).
Days 6–7	Wear it overnight to see sleep tracking and the overnight battery drop. Log the result each morning.
One full battery cycle	Run the battery down on your normal settings, noting the percentage at fixed times and what you did, then compare the result with the maker's claim.
After any update	Repeat the accuracy test, the sync check and the notification check.

A pass/fail checklist for a wearable

Agree your thresholds with the manufacturer's brief first. If it doesn't give any, write your own before you start (for example, "distance within 3 percent of the reference") so you aren't judging after the fact.

Pairs with the phone and app first time and keeps its settings through a restart.
Locks GPS in the time the maker gives, in the open.
Records a route within your agreed distance error of the reference, without big jumps or cut corners.
Reads heart rate within your agreed gap of a chest strap at a steady effort.
Follows a change in effort without a long lag or odd spikes.
Starts, pauses and saves workouts reliably, with no lost sessions.
Gives sleep summaries that roughly match your own experience over several nights.
Delivers phone notifications within a few seconds, without duplicates.
Syncs to the app without manual re-pairing, with nothing missing or duplicated.
Meets the battery claim, or comes close, on the settings you use.
Survives water exposure within its rating (don't test it beyond that).
Installs a firmware update without losing your data or settings.

A fail isn't a verdict on the watch. It's a finding. Write it up with the conditions and a clip.

Health and location data are personal. Before you start, check what the watch and its app store and where they send it. A GPS track can show where you live and work, so crop or leave out the start and end of a route before you share it. If the unit is under NDA, check what you may show.

How to capture evidence engineers can use

Put the watch and the reference in one frame. Photograph the watch's display next to the strap, the second device or the map, so both numbers carry the same timestamp.
Put the phone and the watch in one clip. Dual recording in BetaSuite records your phone's screen and the rear camera into a single video, so a notification on the phone and the alert on your wrist sit side by side on one timeline.
Screenshot what you can't film. Workout summaries, sleep, sync status, battery graphs and error messages, each with the time visible. Export the track file too if the app offers one.
Start wide, then close. First the watch on your wrist in its setting, then the detail: the screen, the error, the strap.
Keep location private. Crop or leave out where a route starts and ends before you share it, unless the manufacturer asks for it, and turn off BetaSuite's GPS stamp for shots taken at home.
Burn the time into the picture. A stamp that is part of the image travels with the file. File metadata is often stripped when a photo is shared or compressed. BetaSuite stamps every photo and video, with optional GPS, weather, season and time zone. More on that in the timestamp camera app guide.
Catch the intermittent faults. A freeze, a restart or a missed buzz is easy to miss. With the watch in front of you, Instant Capture in BetaSuite keeps a rolling buffer and saves the last 15–30 seconds when you tap. Without a tool like that, film the start of each test you run.
Mark it as it happens. Add a one-tap marker or a quick voice note with the time, then write it up properly later.
One issue per clip. Name it by what happened ("Heart rate lag, hill repeats"), not "Video 14".

What to send the manufacturer

A good report is short at the top, specific in the middle and backed up at the bottom. See how to write a beta test report for the full structure.

Section	What goes in it
At a glance	Model and serial number, watch firmware and app versions, phone model and operating system, test dates, the reference devices you used and how you wore the watch. Three sentences on how it went.
Findings, worst first	Safety or skin issues first, then anything that loses or corrupts your data, then annoyances. For each one: what happened, what you expected, how to repeat it, how often it happens and the conditions.
Evidence	Time-stamped photos and clips matched to each finding by name or time, with route start and end points left out if you prefer.
What worked	A short list. Engineers also need to know what not to change.
Data files	A CSV or JSON of your findings if they ask, so they can load it into their own tools. BetaSuite reports can ship with both.

Here is the format for one finding. The values are made up, to show the shape.

Title:      Heart rate reads about 20 beats low after each interval
Severity:   Medium (workout data is misleading)
Expected:   Within a few beats of the chest strap
Actual:     The watch lagged and read about 20 below the strap for 30 seconds after each effort
Frequency:  4 of 4 interval sessions
Conditions: Outdoors, 6°C, left wrist, snug strap, firmware 1.8.0
Evidence:   Photo of the watch and strap together stamped 07:42:18, plus both app summaries

Want to see a finished report? Open the sample report (PDF). It has an At a Glance summary, findings sorted by severity and an image appendix.

Running it in BetaSuite

Create a project for the watch, and note the model, serial number and firmware in your first session.
Import the free protocol below.
Start a session each time you test. Capture the photos and clips the steps ask for, and drop a marker whenever something happens.
At the end of the week, generate a PDF or Word report with an At a Glance summary and findings by severity, plus JSON and CSV data files if you want them.

AI summaries are optional and opt-in. For units under NDA, Confidential Mode blocks cloud AI and cloud uploads and warns you before you share or export anything; on a supported iPhone or iPad, on-device Apple Intelligence can still write summaries. Everything is stored on your device, with no account.

Free BetaSuite protocol: smartwatch and tracker test

This is a ready-made, 12-step protocol for the first week or two with a smartwatch or fitness tracker. It was built with the site's own Protocol Builder, so the link below is a real import link. It mixes pass/fail checks with choice, multiple-choice and rating questions, and asks for a photo or dual recording where the evidence matters. It is a comparison for your own testing, not a health or lab test. For the general idea, see the test protocol template.

Smartwatch and tracker test · 12 steps · free to import and edit

Open this protocol

Set-up: pair the watch with the phone and its app. It pairs on the first attempt, shows the right time and profile, and keeps its settings after a restart of the watch and of the phone.Pass / Fail
GPS distance: on a route you have measured, how far from the reference was the watch's recorded distance? Photo: the watch's summary next to the reference.Options: Within 1 percent · 1 to 3 percent · 3 to 5 percent · More than 5 percent offChoicePhoto required
Route shape: the recorded track follows the real path without big jumps, cut corners or drift, including near trees or tall buildings. Screenshot: the track in the watch's app.Pass / Fail
Heart rate at a steady effort, compared with a chest strap: how close were they? Photo: the watch and the strap's display together.Options: Within 3 beats · 4 to 6 beats apart · 7 or more beats apart · No strap to compareChoicePhoto required
Changing effort: during intervals or a hill, the watch's heart rate follows the change without a long lag or odd spikes.Pass / Fail
Sleep tracking: over three nights, how closely did the sleep summary match how you felt? 1 = not at all, 5 = very closely.Rating (1–5)
Notifications: a message and an app alert reach the watch within a few seconds of the phone, without duplicates, and dismissing one on the watch works. Record the phone's screen and the watch together. Test an incoming call separately, with no recording running, and note the result.Pass / FailDual recording required
Sync: after a workout and after a night, the data reaches the phone app by itself, with nothing missing or duplicated, including after the watch drops its Bluetooth connection.Pass / Fail
Battery life on your normal settings, compared with the maker's claim:Options: Met or beat the claim · A little short · Well short · Not measured yetChoice
Water resistance: only within the rating and the conditions the manufacturer states, the watch works normally afterwards, with a clear screen, working buttons and touch, and no moisture under the glass.Pass / Fail
Which problems did you see? Tick all that apply.Options: Slow or failed GPS lock · Heart-rate dropouts or spikes · Late or missed notifications · Sync failed · Disconnected from the phone · Froze or restarted · Skin irritation or discomfort · None of theseMultiple choice
How happy would you be to wear this watch every day? 1 = not at all, 5 = very.Rating (1–5)

Steps marked required show the tester a Start capture button for that photo, video or dual recording, and the capture is attached to the step's result. Answers roll up into the report: pass rates, ratings and every result grouped by question. A step that asks for a screenshot has no capture button: take it with your phone's own buttons, then import it from your photo library afterwards.

Show the raw code

BSPROTO1:H4sIAAAAAAAAE-1YTY_kthH9KwVd9iIOWt9SA8Yi68BxgHhh7BjYQ7CHarLUYoYSFZKaTsfY_24UpemeHmecBDBgb5CjKKo-Xr1XVd0_JjjPyT55RwHvFx0oSZMHPalkn8zOBiut8UmaPCb7LH12sv_rj8mEIyX75H5EF04Y5AA4KQgO5QM5CORDkiaaLVVdU1VFXYoqq6UoVU4C67oXO4VdoUiWZYNJmjh6TPZ5mvhAM7tI7imIZd7DjNpBGAhWNycdhvg4D3ai6FUHDzjPd_DnEG97sFO80mvnA2AINM4hBT_Yk48vnD4OAYIeVwOzs702lMaHB6LZR5ueQtDT0QP2gRwgOPIBXQDbPwuIv9kOYkh3SZr86ft7UNoHnCTtORoEZ5dAcLYLDPhIMBL6xZFKYbAn6NFB7-y4Bkc9OZokO_BXR288OJLWKVIX22_h-8EGu7-55ZdxRHeGif4RINhbmxzdhxiKH3Cm_fZ2sxvrB7015oIUoYEZwwq8XQIc9BH-toyzT0EuAaR1EzHkDpTTfUhBT9IsSk9HmAgdBEcUXwc0Bg6LNvzO38G9dESTH2xYo1id6-kmGa5rkibfEuPuMBBgAAQfCNUZqO-tCylIO87oSK3sQJAD-QA-OJz3EWBprCc4kSO2fv45bit9B1o_euMZ4tngGYI9UhjIcRRfDzgdObHV7x7U4vhRT4HcI5qYJsKgjUlvshiu4T8HV7I9uiCLYOx0BINHtmOVAj_rB_Ls-t4QzStEejruwT6yzAZHBBOT2afXPM0ZlN6yiZ89MWKMmfI95mFPJryFDL6CyYYIK4ddwVfwSO78ZIqdv7dB91pi0Hbye0AYyXs8ruLBiYsEaIhTJJTDC7Vqpn9PJ_Ak7aT8jVrSS_ZqmQ37IL_qUGk_au8ZXxa6nZ6bte7B38GHyNurMSZ_JNWlmuv1Sw3hB-YFTsxRO7JpyaT0NCMXx5zXcGCymyb4ilumSU_HNarJBtqE4RcTYmnOk9xfegSHFovJ0GxnsUIrIxQGXFEi_7yNzTMcztx1yPSXIBi7I1xQcFeM1HOZrW6u6Spntw72ziwUrA0DSDtNJLmAHPI77onuDEb3EdmzXRxM1o1oLl3vparY_ogP5N54kAb1uE_S5COya0f-WbMz56eyR5wwxBi3gjADdOTRZnBaepRhceTAh7X6L-q8BWbOa6IndMqnF6Ub7jFr1dN4n70dlhDYRfRqFzk8FQ9Gqz17g2VSG2hHgz5q7OOg5cDD4GBo9FFDrBNP9BZ-0PKBBQJhYKXM86qMb-0JBpznM5zsYtb7B-Kue4q9b9B-S4WiqBSeX5fcXfIpTf6-kI_4xDE7OzvOgQftFzwNn1YK9P4b1IZP6Jzsk66leqfqgjeDWpRZvROt6nMhKW_KHKsdNjL5nD5D4fc9V7c8WayGvh6slrxQ2fmpnMnHVRYZzOQkTbwiZWypeHZQ8EH17OA7G4cWTtdTsH3PXJE4M5cZWw73Amzfy51qVCVKwl6UWErRZYjicMhUrcoqK-TuFtgvcCV4jVW7sqp73EnRdKUUZV40okMk0R4ktW1WFrtc3Sb_-1gu_lP2FHAgDLyXl0yVen0EnNExXRrGdWTO3J6_t6t3_mbL6JcolCHuGipJdEV-ECX1mTgomQlZtc0uU0VeV9ktir_hcvQaFZQsizLLapEXWc8NphOtKgshyxIblddVW9FtEr_pmrWlsU7M6pIF5U1eVHkuDk2XibLIpMCua0R-6LoCq0NRF-1tFv_f135pX_s5W64iUAuaD0-WLhVo86LbFXkjsJFcgb4ThwJLcWhL1bQF7QpVvODRl7cTviYilK1SlLWiqnIlSqRCtHVdilw1jez7ppQd3ib_q22X_7YlfkeBIeBOt_YM_jJJkz-A0SEYnmg2dr-PxLTZHt7bcNkT4EyB--Caa93LPm-xE0XZ7kTZdoXosC1ERm1VU6m6Q_VidvxPLcCvUaAsu90u6yuBWVOKUnVSdDvZCkKVYV30VUbdC1j--1V6cz4uJuh_Vet7Y09c7B61IQW8ChorH57-HBBxgDDN7RLirFnnQ5Imf-E3PBW19xRbwrU7br_fNqtJmvxR-00XpK67Y1RkkibfOPvPaGtbfuMn9w96Au2cDtFmFCVbGfsnvnE_jE3U05Vsu7ZpsqY-iEIRihLVTrRdRqJtdk2ldnnRdC-2tF_518arE6dq-2pXEomqrHOWfC_w0Jei7fuuxiZryqZNPn_6_OnzTx6ZgYFCFAAA

How to import it

On your phone, tap Open this protocol. If BetaSuite is installed, it opens its import sheet with the code filled in. If the link opens in your browser instead, tap Copy code there (or here).
In BetaSuite, open Test protocols, choose Import and paste the code or link.
Edit any step to suit your unit, then run it. Your answers are saved to a session and roll up into the report. Protocols, sessions and reports are part of Advanced mode; if you're in Basic mode, Test protocols offers to switch for you.

Want to change the steps first? Open the link in the free Protocol Builder. It runs in your browser with no account, and you can generate a fresh code from your edits. Running a whole beta programme? See how to give every tester the same protocol and merge the results.

When BetaSuite is the wrong choice

BetaSuite covers everything from a single stamped photo to a full report for the manufacturer. It is the wrong tool only when:

You need data from the watch itself. BetaSuite doesn't connect to the watch or read its sensors, so it can't pull heart-rate, GPS or sleep data. You photograph, screenshot or export from the watch's own app.
You need clinical or lab accuracy. A chest strap and a measured route are a consumer comparison. BetaSuite isn't a medical tool and can't validate a sensor for health use.
You want to analyse tracks. BetaSuite stamps your evidence. It doesn't overlay or analyse GPS tracks, so use the watch's app or a mapping tool and bring screenshots as evidence.
You want to measure charging power. BetaSuite's charge-port logging (volts, amps and watts) is Android-only and covers the phone's own port, not a watch charger. Note battery percentage by hand instead.
You want to test an app, not hardware. BetaSuite is not a TestFlight or Google Play testing tool. See what a hardware beta testing app needs to do.

Don't need a report? If the manufacturer takes findings through its own portal or form, or you only want stamped photos and video, switch BetaSuite to Basic mode (Settings > App mode). It keeps every capture tool, including dual recording and Instant Capture, and leaves out projects, sessions and reports, so it works as a plain timestamp camera. Attach the files wherever the manufacturer asks, and switch back to Advanced at any time without losing anything.

If you run the programme rather than test in it, see the programme page. For the longer case for the app, see why BetaSuite. Testing something you ride? See the e-bike testing log and the electric scooter testing log.

Frequently asked questions

What is a smartwatch or fitness tracker beta test?: A pre-release or early-access trial where a manufacturer lets real users wear an unfinished watch, tracker, firmware or app and report faults before general release. The tester's job is to find problems in real use and describe them so engineers can reproduce them.
How can I check a smartwatch's heart rate or GPS accuracy?: Compare it with a reference you trust: a chest strap for heart rate at a steady effort, and a route you have measured for GPS distance. Start both together, keep the conditions the same each time and photograph the watch and the reference together. It is a comparison for your own testing, not a clinical or lab result.
Can I use a beta smartwatch to make health decisions?: No. Beta hardware and software can be wrong, so treat every reading as unverified. This guide is not medical advice. Don't change medication or treatment because of a beta device, and talk to a health professional about any concern.
Can I use BetaSuite for a wearable under NDA?: Yes. Everything is stored on your device with no account. Confidential Mode blocks cloud AI and cloud uploads, and warns you before you share or export anything. Check your NDA first for what you may photograph and what you may send, and by what route.
Is BetaSuite a TestFlight alternative?: No. BetaSuite: Tester's Toolkit is not an app-beta tool and has no connection to TestFlight or Google Play testing tracks. It is for people who beta test physical products in the field and need timestamped evidence and a report for the manufacturer.
Is BetaSuite a subscription?: No. It is a one-time purchase from the App Store or Google Play, with no subscription, no ads and no account. Each store sets the price.

Start testing with timestamped evidence

BetaSuite: Tester's Toolkit burns the date and time into every photo and video, then turns your sessions, markers and findings into a PDF or Word report, on iPhone, iPad and Android. Only need a timestamp camera? Use Basic mode.

One-off purchase · No subscription · No ads · No tracking · Yours for life

No account needed. The price is set in each store.

See everything else BetaSuite does →