[Feature]: Remove dependency on UnitTestFrameworkPkg's IncludePrivate path.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 265
- Forks
- 131
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 6
Description
Feature Overview
DxeMemoryProtectionApp and XmlSupportPkg\Library\UnitTestResultReportJUnitFormatLib\UnitTestResultReportLib.inf are both making use of internal header files from the UnitTestFrameworkPkg.
DxeMemoryProtectionApp is consuming UnitTestFrameworkTypes.h.
UnitTestResultReportLib.inf (XmlSupportPkg\Library\UnitTestResultReportJUnitFormatLib) is using UnitTestResultReportLib.h
These need to be examined and possibly removed.
Solution Overview
Enable tests to run without the need to use internals of the UnitTestFrameworkPkg.
Alternatives Considered
No response
Urgency
Low
Are you going to implement the feature request?
I will 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
Start by inspecting DxeMemoryProtectionApp and XmlSupportPkg\Library\UnitTestResultReportJUnitFormatLib\UnitTestResultReportLib.inf, focusing on their use of UnitTestFrameworkTypes.h and UnitTestResultReportLib.h. Trace the IncludePrivate dependency and identify whether public interfaces can replace those internal headers. Done means the tests run without requiring the UnitTestFrameworkPkg IncludePrivate path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100