I really need help. We are doing some interface files, something like C header files and configurations.

Management is aware of the "unittesting" buzz words and expects me to write unit tests on "header" and configuration files....

I tried to explain that there are no units to be tested, asked which units should be tested but in the end....

What does it actually mean to test definitions of structures, classes and methods?!

  • 0
    You can test that linked definitions aren’t circular
  • 3
    testsomething() { assertTrue(True)}

    there. Done.
  • 0
    This makes me glad my mechanical coverage tool is able to detect the full path of symbolic reference exercised by the public interface.
Add Comment