Testing evidence, October 6, 2026.

Results on main, five runs.

"Files" means a whole test file. Each run was done on one Windows PC by the person merging that batch of work. A blank "not run" means the batch did not touch that part, so it was not run. The source of every number is listed in the page source, at the bottom.

• Batch 14: one Windows-app test file (the walkie-talkie browser test) passed only on its automatic second try.
• Batch 19 first went to a branch only, because the three Android runs each failed one test (a rule that stops new English-only text in the Android app). The photo-backup change that caused it was taken back out, and the Android runs then passed. That change came back in batch 22 after it was fixed.
• Batch 20: three test files failed on the first run. Two belonged to merged work that broke existing tests; that work was taken back out and re-run, and the files passed again. The third (a school-permissions file) timed out while the PC was busy and passed on its own. Smart TV and Roku were not run.
• Batch 21: one photo-privacy test file failed on a Windows temporary-folder clean-up error under load; it passed 28 of 28, three times, when run alone. Five branches without a review verdict were left out.
• Batch 22: the first run had 8 failing files. After fixes, all passed when re-run. Two other files (headless-boot and music-library-edge) failed only because the real video converter had been copied into that folder; both passed 38 of 38 without it. One file (api-routes-13) passed on the automatic second try. One worker test failed once under load and passed 17 of 17 twice alone. The batch also changed some tests so they match behaviour changes made on purpose.
• Batches 15 to 18 (smaller merges between these) are not shown in the table; their notes did not record counts we can cite here.

Linux test runs.

We also run the same suites on Ubuntu 24.04, in WSL2 on the Windows PC or in a cloud container. This is not a Linux desktop release, and none of it is a test on a separate Linux computer or a NAS. Each run tested a different commit, so the numbers are not a trend.

• Run 5: four Windows-app test files failed. The report says all four were problems in the tests themselves (for example a test that called a program by a name Ubuntu does not use). Fixes were merged, but we have not repeated that whole Linux run since, so we do not claim they pass on Linux.
• L1: most of the 18 files failed because the container's video converter was not the one the app ships. Re-run alone with the right converter, they passed. One test had a real timing bug in the test itself, fixed on main; one failed only when run as the system administrator account; two failed only under load and passed alone, and the report says the cause was not found. The report found no failure in the app itself, and only the 14 converter-related files were repeated with the correct converter.
• The Smart TV and Roku runs were tests and builds in a container. They are not runs on a TV or a Roku.

Real bugs found and fixed since 0.1.80.

Since desktop 0.1.80 was cut (code tag release-2026-10-06a), our helpers wrote tests that feed each part of the app broken, huge, repeated or out-of-order input, and our reviewers read the results. Each fix below is on main as of 7df632628. Fixed on main does not mean released: none of the Windows app or Android items is in a download yet. Many hunts found nothing and changed no code. Some other fixes were still waiting on helper branches when that commit was made, and are not listed.

Windows app

• Posters, backdrops and actor photos went blank if you had chosen a different port in Settings.
• Photos: location details inside a video file could be shown to a household member who should not see them. They are now blanked for everyone but the owner.
• Streaming a video or a shared trip link: a viewer who hung up could leave a file open on the PC.
• Parental controls: changing, resetting or removing the PIN now ends every unlocked session at once. Daily watch limits and bedtime are now counted by real minute, so the repeated hour when the clocks go back is no longer free.
• Safety copies (backups of settings): only a file from the app's own safety-copy folder is accepted as one, sign-in state is kept out of them, and "restore without passwords" is honoured.
• An approved computer that was wiped or replaced no longer locks the household out.
• Recordings: file names that Windows reserves (such as a name starting with CON or NUL) are handled, and a guide time of 30 February is refused.
• Update check: a pre-release version number was not placed correctly against a final release.
• Skip-intro and credits detection: odd or empty results could produce an invalid confidence figure.
• Jellyfin-compatible mode: seven bugs found and fixed by 38 new adversarial tests.
• Importing from another server (migration): a spreadsheet with too many columns, an empty folder, unknown source names and over-long ids are now handled.
• Playlists, podcast and radio feeds: bad rule field names, invisible start-of-file marks, control characters in subscription lists, feeds with more than 2000 items and a bare-number date are now handled.
• Headless (no-window) server: it now exits with a clear code when its port cannot be used, handles blank folder lists, and its Docker health check uses the right port.
• Names: a name made only of look-alike blank characters is now refused.
• Campsite: War, Go Fish and Dominoes refuse an invalid number of players, long tournament heats stay alive, and Sea Battle no longer loses a keyboard click after a cancelled drag. The Family Timeline beta gaps in shared photos were fixed.

Android phone app

• Downloads list: one unreadable saved download could wipe the whole list. Each saved row is now read on its own.
• Pairing links: a link could name a different house than its address, skipping the "Use this Beebo?" question, and two kinds of malformed home addresses were accepted. All three are refused. Extra checks were added for numbers written as words and odd IPv6 addresses.
• Photo backup: a PC that kept stalling an upload could keep the phone retrying, and a very large file could overflow a counter. Both fixed.
• Connection problems: timeouts, refused connections and secure-connection failures are now told apart, and the reconnect counter cannot overflow.
• Synced music: a phone reporting a non-number error was shown as perfectly in sync.
• Audiobooks and Lookup Sites screens: a late reply could change a different book's session or erase a newer draft.
• Batch downloads announce the chosen size before queueing, the Audiobooks Back button stays inside the app after a restore, and duplicate text entries were removed.

Server (cloud account service)

Items marked "deployed Oct 6, 8:11 PM Eastern" were part of the server deploy of 7df632628.

• Deployed Oct 6, 8:11 PM Eastern: Stripe payment events are read in the right order, a repeat of an event is safe, and in-progress claims no longer collide.
• Deployed Oct 6, 8:11 PM Eastern: a Google Play cancellation sent during a Google outage is retried, within a time limit, instead of being lost.
• Deployed Oct 6, 8:11 PM Eastern: share guests can never be given the owner's rights, a guest's password is checked at sign-in, and a takeover removes the guest's tokens.
• Deployed Oct 6, 8:11 PM Eastern: usage limits that count per hour keep their counters for the full hour, and hold under many requests at once.
• Deployed Oct 6, 8:11 PM Eastern: e-mail sending refuses bad recipients and subjects; a failed send no longer kills a link that is already in the inbox.
• Deployed Oct 6, 8:11 PM Eastern: tester uploads are limited to one per address, six an hour per address, and bounded in memory and time.
• Deployed Oct 6, 8:11 PM Eastern: the server's setup scripts refuse wildcard or injected characters, and its scheduled jobs finish waiting work after a failure.
• Deployed Oct 6, 8:11 PM Eastern: the name rules (see the Windows app list above) also apply on the server.

Smart TV and Roku apps

• Smart TV app: opening a screen that failed left a blank screen, and a saved-position lookup could match built-in object names. Both fixed on main.
• Roku app: a page size of zero and a non-text address could stall or crash the app logic. Both fixed on main.

Security review 6 (a written report) was merged in batch 19. The reviews found nothing that lets a stranger into a library or account, and we do not publish technical detail of weaknesses here.

What is what, in our own labels.

The labels are Available, Beta, In development and Planned. A label describes how far a feature has got. It is not a test result.

What nobody has tested yet.

• No real Roku, Samsung TV, LG TV, Xbox, Apple TV, iPhone, iPad or Mac has ever run Beebo. Those apps have only been run in simulators, browsers, containers or build servers.
• Beebo Auto has never been tested in a real car.
• Campsite games have not been played by real groups of several phones. Only one phone, a Samsung S9+, has been used as a second device.
• Remote Desktop, Portrait Party, Household Library (library sharing), Story Studio, walkie-talkie from anywhere and the online games are built but switched off or owner-only, and none has been tested on real devices.
• Fire TV and Fire tablets have had no device test. Android TV has no recorded run on a real Android TV device.
• The Linux and Docker server builds have not been tested on any NAS model or real Raspberry Pi.
• Hardware video conversion has been checked on one Intel graphics chip. NVIDIA, AMD and Mac hardware are untested.
• The translations were made with a machine's help and no native speaker has read them.
• The Windows installer is not code-signed, so Windows may show a warning.
• A passing automatic test does not show that a feature works on a real device. Real-device results are on What's tested and Tester results.

We never claim that every feature works. If a feature is not listed with a result above, treat it as unknown.