Preparing for club testing
TestFlight invitations will be sent by the organizer when an
approved beta build is ready. There is currently no public download
link on this site.
Four time classes. One lap line.
For this Saturday’s test, focus on the 2-, 4-, 6-, and 8-hour races. Each class has its own race start, cutoff, counted full laps, and men’s and women’s standings.
Check independent starts, lap counts and splits, repeat-entry confirmation, Undo across races, cutoff review, backup and recovery, and the results CSV.
This page describes the current development workflow. Check the build notes in TestFlight for the features included in your installed version.
Install through TestFlight
- Download TestFlight by Apple on your iPhone or iPad.
- Give the test organizer the email address where you want to receive your invitation.
- When Apple’s invitation arrives, open it on your device, choose View in TestFlight , accept, and install DB Timer.
- Read What to Test before starting. You can enable automatic updates for new beta builds.
If the invitation has not arrived, check your spam folder and ask the organizer whether the build has been approved and invitations sent.
Set up Saturday’s races
- Create four timed races with 2-, 4-, 6-, and 8-hour limits . In Race Details, enter 120, 240, 360, and 480 minutes , respectively. Add runners to the correct time class, use unique bibs across the event, and confirm genders for standings.
- Follow the organizer’s actual start schedule. Start each race with its group, and record a bib only after a completed one-mile lap. Use the Timer keypad for runners from all four races.
- Keep an independent crossing log with bibs, observed times, and expected lap totals. An entry’s submission time is the time DB Timer records.
- Review pending cutoff entries before results. Each time class should have its own top-three men’s and women’s standings. Export the CSV and retain a meet backup.
Rehearse the recovery tools before race day
Use a disposable test meet for deliberate mistakes and recovery checks.
- Enter the same bib within 60 seconds and try both confirmation choices.
- Record entries in two races, then confirm that Undo Last reverses the latest action.
- Test crossings at a cutoff and after it. Accept a pending entry using a valid observed time, and reject another.
- Background and reopen the app. Force-quit after a saved crossing, relaunch, and reconcile it with your log.
- Export and restore a test backup. Compare the recovered race setup, timing history, and results.
Known testing considerations
- Submission time is used for bib crossings. Use your line log to review late submissions.
- Each phone has independent race data. Shared live timing across phones is not implemented.
- The app is a beta. Verify your complete workflow on the device you will use.
Tell us what happened
Use Send Beta Feedback in TestFlight or email support@wolfsraven.com .
Include device model, iOS version, app build, the steps you took, expected behavior, and observed behavior. Use sample participant data when possible and remove unnecessary personal details from screenshots.