3 ms·
That's why they're called unit tests. They are supposed to test precisely one unit of functionality, while assuming everything else works as specified (using mo
by ackalker 12y ago
That's why they're called unit tests. They are supposed to test precisely one unit of functionality, while assuming everything else works as specified (using mocks if necessary).
Taking into account the effects of microcode execution on the test result is in fact a kind of integration testing.
- SilasX 12y agoI think the GP's point was that you can't mock out the computer chip's opcodes.