dtourolle
40d358ab52
Not a generic smoke test. Every case exists because something specific went wrong, and most were found on hardware after the suites were already green. The sequences are load-bearing. Two defects this cycle only appeared in a particular order of actions — play, enable background audio, background, foreground, exit — and testing the same features in any other order found neither. So the plan asks for that order explicitly rather than listing "background audio" as a feature to try. It also states plainly that a green conformance run is not sufficient evidence to ship, because both regressions introduced during this work passed conformance and were caught by a person using the app. Includes a symptom-to-cause table, because none of these presented as their cause: a dead play/pause button was an unobserved property, a black screen was a float that could not become a Duration, and a scrub bar with no scale was a duration of zero being believed. "Known open" lists what is deliberately unfixed so each gets a decision rather than a surprise — device-local resume, the unconfirmed handoff swap, and the broken side-by-side debug install whose own error message advises an uninstall that would destroy the real app's data.
JellyTau
A cross-platform Jellyfin client built with Tauri, SvelteKit, and TypeScript.
Business logic lives in a Rust backend; a UI-rich Svelte frontend handles presentation and talks to it over Tauri's IPC. Targets Linux (libmpv) and Android (ExoPlayer).
Getting Started
This project uses bun as its package manager.
# Activate the Rust environment (fish shell)
source "$HOME/.cargo/env.fish"
# Install dependencies
bun install
# Run in development
bun run tauri dev
# Type-check the frontend
bun run check
# Build for Linux
bun run tauri build
# Build for Android
bun run tauri android build
For the full set of build, test, and Android helper scripts, see scripts/README.md.
Documentation
| Topic | Location |
|---|---|
| Architecture overview & subsystem docs | docs/architecture/ |
| Requirements, traceability & technical debt | docs/requirements.md |
| Build & release process | docs/build/build-release.md |
| Docker builds | docs/build/docker.md |
| Traceability tooling & CI | docs/traceability.md, docs/traceability-ci.md |
| Release checklist | docs/release-checklist.md |
| UX flows | docs/ux-flows.md |
| CI operations (builder image, secrets, runner) | docs/build/ci-operations.md |
Contributing
CONTRIBUTING.md covers the setup, the gates a change has to pass, and the two rules that catch people out (bug fixes start with a failing test; Jellyfin's taxonomy stays in Rust). Please also read the Code of Conduct.
Found a security problem? Do not open an issue — see SECURITY.md.
Verifying a download
Every release publishes SHA256SUMS covering all of its artifacts, plus an SBOM
of what went into the build:
sha256sum -c SHA256SUMS
Desktop builds update themselves from Settings → Updates, verifying each payload against JellyTau's signing key before installing. Android installs are handled by the system installer, so the app links to the releases page instead.
Recommended IDE Setup
VS Code + Svelte + Tauri + rust-analyzer.
License
MIT