Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Owner test protocol: in-depth self-testing and dogfooding

Aperta
  • Qualcosa non va?
#91 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
Più di una settimana
Idoneità per principianti
45/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Ambito
documentation, mobile, testing

Direzione di ricerca

Start by reading docs/WORKFLOW.md and the linked design document, then create docs/TEST_PROTOCOL.md with the six personas, 30 scenarios, condition matrix, devices, and reference price lists. Run the scripted scenarios on the Note 9S release APK, record results in docs/test-log/YYYY-MM-DD.md, and ensure every failure is linked to an issue and fixed or documented as a known limitation.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:mobile type:eval

Part of the JobTrail v2 rebuild · design doc · all drafts · draft #30 (revised: outreach → owner test protocol)

Depends on: —

Context. Outreach to tradespeople was dropped (owner can't reliably reach them). Instead the owner tests the app in depth, and the portfolio says so honestly: "built for solo tradespeople, grounded in their documented pain points; tested by the developer through scripted role-play on a 2020 budget phone." This protocol is also the backbone of the per-issue before/after verification in WORKFLOW.md.

Scope

  • docs/TEST_PROTOCOL.md:

    • Personas for 6 trades (plumber, HVAC, electrician, handyman, cleaner, appliance repair), each with 5 scripted end-of-job scenarios covering the hard cases (hours phrasing, negation, self-correction, multiple/no materials, supply-house trips, extra labor, approval absent) plus a reference price list per persona.

    • Condition matrix: quiet room, outdoors/wind, in a car, background noise (TV/tools); airplane mode; low storage; low battery / battery saver; backgrounding and returning mid-inference; app kill and restart; first launch with no model downloaded.

    • Devices: Note 9S (primary), iPhone 16 Pro, laptop browser (web demo).

    • Result log format (docs/test-log/YYYY-MM-DD.md): scenario, condition, device, build/commit, expected vs observed, pass/fail, evidence link.

  • Dogfooding cadence: after every mobile issue merges, run the relevant scenarios on the release APK; every defect found is filed as a GitHub issue before moving on.

  • Pre-launch acceptance session: full scripted run of all 30 scenarios on the Note 9S, recorded.

Acceptance criteria

  • TEST_PROTOCOL.md committed with all 30 scenarios, the condition matrix and reference price lists.

  • ≥ 30 scripted scenarios executed on the Note 9S release APK before launch, results logged.

  • Every failure found is filed as an issue (linked from the log) and either fixed or documented as a known limitation.

Lingua principale
Python
Stelle
0
Fork
0
Merge medio
14h 46m
PR unite (30g)
21

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Taleef7/JobTrail

Tutte le issue di Taleef7/JobTrail

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.