microsoft / microsoft/mu_basecore
[Feature]: Verify FTW Test Results
Open
Nobody has claimed this yet.
state:backlog
state:needs-owner
state:needs-triage
type:feature-request
urgency:low
- Dominant language
- C
- Stars
- 290
- Forks
- 187
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 37
Description
Feature Overview
Run tests to perform the following scenarios are handled correctly:
- Corrupt NVStore FV Header Zero Vector and Verify Recovery and Reboot
- Corrupt NVStore FV Header FS GUID and Verify Recovery and Reboot
- Corrupt NVStore FV Header FV Length and Verify Recovery and Reboot
- Corrupt NVStore FV Header Signature and Verify Recovery and Reboot
- Corrupt NVStore FV Header Checksum and Verify Recovery and Reboot
- Corrupt NVStore FV Header Blockmap0 and Verify Recovery and Reboot
- Corrupt NVStore FV Header Blockmap1 and Verify Recovery and Reboot
- Corrupt NVStore Varstore Header Signature Guid and Verify Recovery and Reboot
- Corrupt NVStore Varstore Header Size Field and Verify Recovery and Reboot
- Corrupt NVStore Varstore Header Format Field and Verify Recovery and Reboot
- Corrupt NVStore Varstore Header Health Field and Verify Recovery and Reboot
Solution Overview
Verify via unit tests and/or a virtual platform like Q35.
Alternatives Considered
No response
Urgency
Low
Are you going to implement the feature request?
Someone else needs to implement the feature
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating existing FTW and NVStore test coverage and the Q35 virtual-platform support, then determine how unit tests can corrupt each listed header field. Done means every corruption scenario verifies recovery and reboot behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100