24Seven.FM PlayerProject portal
GitHub
Tester workspace
Choose a focused session, record the build and device before you begin, and submit a pass, failure, pass-with-notes, or blocked result. Every useful outcome strengthens the Alpha evidence.
Prepare once
Before touching the controls, record the exact build source, app version and version code, device model, Android version, form factor, and connection type. A result without its environment is difficult to compare or repeat.
Install only from the project-approved Play testing track or supplied release channel. Identify local debug or release APKs explicitly; their signatures and behavior can differ from Play delivery.
Pick one route below. Complete it in order, note the first unexpected result, and avoid changing several device conditions at once.
A clean pass on a named device and Android version is useful evidence. Select Pass with notes when behavior works but feels confusing, slow, or inconsistent.
Choose one route
Run the shortest route that covers the behavior you want to evaluate. Repeat on a second station or configuration only after recording the first result.
Evidence contract
Use exact visible text and state changes. “Playback failed” is less useful than the selected station, displayed state, time to failure, whether audio continued, and what happened after one retry.
| Area | Record | Pass boundary |
|---|---|---|
| Playback | Station, visible state, audio, title/artwork, primary or fallback indication | One logical stream; controls and visible state agree |
| Background media | Notification controls, notification-body navigation, lock/headset behavior | Controls affect the existing player and reopen the existing task |
| Station data | Queue, History, search mode/query, sorting, missing or stale fields | Only station-provided values appear; unavailable data stays explicit |
| Account | Station, signed-in/out state, restoration, logout isolation | Only the selected station session changes |
| Adaptive UI | Window size, orientation, hinge state, font/display scale, clipped control | Primary controls remain visible, readable, and operable |
| Recovery | Connection before/after, displayed error, automatic attempt count, manual action | One bounded recovery after validated connectivity returns |
Structured intake
The public form captures environment, station, outcome, affected areas, expected and actual behavior, repeatability, reproduction steps, and redacted evidence. Separate unrelated findings so each can be verified and closed independently.
Credential/session exposure, unintended private content, destructive account behavior, or a repeatable crash that prevents use. Stop testing and report immediately without attaching the sensitive material.
Playback, navigation, account isolation, requests, community safeguards, or an adaptive layout cannot complete its intended job. Record exact steps and repeatability.
The task completes, but wording, spacing, latency, feedback, or consistency should improve. Select Pass with notes when the expected result still occurred.
Public report
GitHub issues are public. Never include passwords, security answers or CAPTCHA images, cookies, session values, email addresses, private messages, abuse-report content, signing material, private endpoints, full network captures, or screenshots containing personal information.
Do not repeatedly submit song requests while investigating an indeterminate response; inspect Queue first. Do not send moderation test reports unless the administrator has explicitly authorized that exact test.
Finished a session?
Passes establish coverage. Failures establish work. Blocked tests identify missing access or setup without being mistaken for product defects.