2 comments:
File Documentation/technotes/2020-03-unit-testing-coreboot.md:
This dependencies
may be broken using mocking concept, to some degree. However when mocks need to
be too complex, then such a unit test cannot address an idea of being quick and
simple.
Makes sense, wasn't clear enough here. […]
I like the simple version you propose.
My statement about "unrelated changes" has to do with a unit test that is too closely tied to the implementation of the module under test. I've seen it happen mainly when testing a state machine; the unit test checks the state, instead of checking the outputs. So it's just something to be aware of when writing tests, to avoid testing internals of the code.
Patch Set #1, Line 94: Assumption that all firmware devs know C
My point is - ideally tests should be written in C, since this is the language which all coreboot de […]
OK, then state that instead, that unit tests will be written in C because the code being tested is also written in C.
To view, visit change 39893. To unsubscribe, or for help writing mail filters, visit settings.