You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25Lines changed: 25 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2015,3 +2015,28 @@ The workflow supports:
2015
2015
- failure-family grouping
2016
2016
2017
2017
Safe scope: structured diagnostic telemetry simulation, not production firmware telemetry ownership or Splunk deployment.
2018
+
2019
+
---
2020
+
2021
+
## I/O Transport Validation and Core I/O-Style QA Artifacts
2022
+
2023
+
DetTrace includes I/O transport replay workflows under `io_transport_validation/`.
2024
+
2025
+
The workflow validates:
2026
+
2027
+
- USB reconnect recovery
2028
+
- PCIe-style enumeration failure isolation
2029
+
- DisplayPort-style link training recovery
2030
+
- accessory disconnect/reconnect behavior
2031
+
- timeout/retry chains
2032
+
- first-divergence reporting
2033
+
- PASS/FAIL diagnostic status with reason
2034
+
2035
+
Quality artifacts under `quality_artifacts/` include:
2036
+
2037
+
- Core I/O-style test plan
2038
+
- regression matrix
2039
+
- bug reproduction template
2040
+
- failure taxonomy
2041
+
2042
+
Safe scope: replay-based diagnostics and QA workflows. This does not claim USB/PCIe/DisplayPort driver development, kernel engineering, or firmware ownership.
This folder contains replay-based I/O transport validation artifacts for Apple Core I/O-style QA positioning.
4
+
5
+
## Scope
6
+
7
+
These are trace replay and diagnostics workflows. They do not claim USB/PCIe/DisplayPort driver development, kernel engineering, or firmware ownership.
0 commit comments