mirror of
https://github.com/PR0M3TH3AN/bitvid.git
synced 2026-03-08 03:47:14 +00:00
1.9 KiB
1.9 KiB
Bitvid Manual QA Script
Run this checklist before publishing releases or merging changes that touch upload or playback flows. Copy/paste the steps into QA tickets when requesting validation.
- Upload Modal Smoke Test
- Open the Upload modal, verify title is required, and ensure either a hosted URL or a magnet (or both) must be supplied.
- Submit three variants: URL-only, magnet-only, and both URL + magnet. Confirm success messaging or event publication in each case.
- URL-First Playback
- For a post with both URL and magnet, play the video and confirm the hosted URL loads first (inspect network requests or logs).
- Simulate a dead URL (offline mode or request blocker) and confirm playback falls back to WebTorrent without breaking the UI.
- Magnet Safety
- Paste an encoded magnet and confirm
safeDecodeMagnet()outputs the raw string before playback. - Ensure
normalizeAndAugmentMagnet()adds providedws=/xs=hints while keeping the originalxthash intact.
- Paste an encoded magnet and confirm
- P2P Hints & Trackers
- Confirm magnets generated through the modal include HTTPS
ws=seeds and optional HTTPSxs=torrent URLs when supplied. - Check that tracker arrays originate from
js/constants.jsand only include WSS endpoints.
- Confirm magnets generated through the modal include HTTPS
- Cross-Browser Verification
- Spot-check Chromium and Firefox (desktop) for console warnings about CORS, Range requests, or tracker connectivity.
- Optionally validate on mobile Safari/Chrome if the change targets mobile UX.
- Saved Profile Metadata Refresh
- In the browser devtools console/storage panel, delete
bitvid:profileCache:v1but keepbitvid:savedProfiles:v1populated with Nostr pubkeys that lack stored names/avatars. - Reload the page and open the profile switcher; confirm avatars and display names populate automatically without manual refresh.
- In the browser devtools console/storage panel, delete
Document findings (pass/fail notes plus relevant screenshots or logs) so they can be attached to release or PR notes.