mirror of
https://github.com/anomalyco/opencode.git
synced 2026-07-24 12:15:51 -04:00
Luke Parker
14 lines
813 B
Markdown
14 lines
813 B
Markdown
- Prioritize stability, then simplicity, then measurement overhead.
|
|
- Use Playwright for scenario control, isolation, and completion checks.
|
|
- Use Chrome Performance traces for generic browser profiling.
|
|
- Use Electron `contentTracing` for packaged multi-process profiling.
|
|
- Keep custom probes only for product-specific measurements.
|
|
- Do not duplicate measurements across the harness, probes, and traces.
|
|
- Run benchmarks serially to avoid cross-test contention.
|
|
- Run benchmarks against production builds.
|
|
- Keep detailed profiling opt-in when it changes workload behavior.
|
|
- Preserve raw diagnostic data or use lossless representations.
|
|
- Do not enforce machine-dependent performance thresholds.
|
|
- Assert scenario completion and metric collection only.
|
|
- Keep normal test discovery free of manual benchmarks.
|