Display Wave JSON regression reports with failure navigation

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

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java, json
Ambito
developer-experience, testing

Direzione di ricerca

Start from the linked runners, Wave/tools/run_tests.py and Wave/tools/run_runtime_cases.py, and capture small success/failure/interruption reports to pin down the report versions and shapes you must parse. Then locate the WfP code that builds a test-results tree (coordinate with issue #34) and map pass/fail/skip/not-run/interrupted onto it, linking each case to source and diagnostics plus target/compiler provenance. Note the hard dependency on #91 before starting. Done looks like the captured fixtures rendering as a navigable tree, with tests covering malformed and large reports without UI stalls.

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

Descrizione

enhancement help wanted priority medium testing wave

Problem / current evidence

The existing Wave runners can write JSON reports, but WfP has no test tree consuming them. A nonzero process code alone does not tell which cases failed, were skipped, or never ran.

Code and contract references

Scope / proposed contract

Map supported report versions/shapes into an IDE test-results tree with source/log navigation. Keep test discovery/execution in the runner adapter.

Completion criteria

  • Represent pass/fail/skip/not-run/interrupted states from actual report semantics rather than treating absent cases as pass.
  • Link each case to its source and relevant diagnostics/output when supplied.
  • Record target, compiler identity and report provenance; label imported old reports clearly.
  • Handle malformed, partial and large reports without freezing the UI.
  • Test captured small success/failure/interruption reports from the supported runner contract.

Dependencies and boundaries

  • Depends on #91.
  • Reuse/coordinate with existing WfP work: #34.
  • Ecosystem index: #49; existing foundations: #8.

Difficulty

Medium — requires understanding the affected tool or platform integration.

Audit baseline: Wave 509a1e46; Whale e3a12d08; Vex 71f29daa; WfP 2804fc02. This issue records source-audit findings and proposed work; no implementation or new execution is claimed. The checks above are future acceptance criteria. Prefer small fixtures and targeted validation; full builds or real debugger/IDE sessions should be explicit and necessary.

Lingua principale
Java
Stelle
0
Fork
3
Merge medio
8h 8m
PR unite (30g)
1

Preparare l'ambiente

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 wavefnd/wave-for-platform

Tutte le issue di wavefnd/wave-for-platform

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.