[FEATURE] Add built-in data logging and plotting utilities to the pytest infra
- Dominant language
- C
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
When debugging a firmware or test issue, it's common to add print statements to the firmware (or in the test code) to observe signal data changing over time.
**Describe the solution you'd like**
I want infrastructure that supports logging any signals (tagged data, C variables, etc) the user selects over time. It could just produce a CSV (and maybe also a plot) for each test run.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by mapping the existing pytest infrastructure and how a test run exposes tagged data or C variables. Define the supported signal-selection interface and CSV or plot output before implementation; done means selected signals are captured over time and artifacts are produced for each test run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- data-visualization, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100