Skip to content
This repository has been archived by the owner on Feb 23, 2021. It is now read-only.

Document the purpose of all unti test cases #109

Open
prakhya opened this issue Dec 22, 2016 · 1 comment
Open

Document the purpose of all unti test cases #109

prakhya opened this issue Dec 22, 2016 · 1 comment

Comments

@prakhya
Copy link

prakhya commented Dec 22, 2016

Although we have six test suites (Bits, chipsec, efivarfs, fwts, kernel_efi_warnings, ndctl) in LUV we have an overview of what every test suite does and some knowledge on unit tests that these six test suites launch. But it would always be useful to have a documentation that explains the purpose of each and every unit test case that these six test suites launch and what it means when the test case gets skipped/failed.

This documentation will serve developers as a quick reference to know what every test case does because it's nearly impossible to remember all and will also be very useful for users to understand their results.

@meghadey
Copy link
Contributor

we have a initial draft ready. We will upload this as a wiki soon.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants