-
Notifications
You must be signed in to change notification settings - Fork 637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No way to continue without a test suite #270
Comments
This image has a treasure trove of Phoenix NVRAM things, can be used to test that part of NVRAM parser later. |
Would it be possible to have a list of these edge cases that are historically supported so that anyone who has or knows how to re-find such samples can do so? |
Let's make such a list by reading parser sources:
|
Intel regions:
|
Raw Areas:
|
Volumes:
|
FFS Files:
|
FFS Sections:
|
Still a ton of stuff remain for variations of NVRAM, ME, BPDT, BootGuard and other smaller parsers, but let's collect the above first and see how it goes. |
Yet another breakage that could have been caught by a test: 19ab607 |
Mentioning #219 here, have some images attached there. |
Mentioning #234, which has a false positive "Intel" Flash Descriptor detection sample. |
Mentioning #368, regression in A66 and A67 that could be caught by adding Apple SCAP files to a test suite. |
Long ago, when trees were big and bits were played live, I've developed those parsers in Qt-flavored C++, using lots and lots of different EFI and UEFI images as possible input, and adding a lot of really strange code to make most of them parsing into something resembling a valid tree structure.
Sadly, today in 2022 almost none of those original images are available to re-test that old code, so refactoring it got unnecessary complex, enough to discourage any new people to ever touch anything here. I myself was discouraged enough for many years.
To make this pain a lot easier, we seriously need to:
The text was updated successfully, but these errors were encountered: