Reporting unit test results

Question

I am writing a document for a scientific conference. To be thorough, in this article I said that I did unit tests for the components in the system among all the other tests (system testing, usability, etc.) that I did.

In the results section for unit tests, I simply said that all tests passed. I transferred the project to my adviser, and now he tells me that I need to give a more detailed presentation of the unit tests.

I have never heard of writing a summary of the results for unit testing. Does something like this exist?

Answer 1

A detailed summary of unit tests may include, perhaps, a measure of code coverage or a diagram showing where you reached code coverage. But even this is not particularly valuable. This is part of the unit test problem - it's easy to add unit test to add extra code coverage without adding confidence in your code.

If you have some specific tests that, for example, check which known I / O combinations worked or check the processing of certain cases of edges or exceptions, then you can document them. If you used test development, where the test proceeds from the problem and its analysis, and not from the code in a "modified" manner, then also say so.

In any case, we’ll put some simple metrics there, but you should always take them with lots of salt ...

Answer 2

, :

, , (Test-Driven Development Test-After).

Answer 3

( , - ?).

, , :

• ( )
• ( )
• .

Answer 4

If unit tests are a la jUnit unit tests , then you can customize your structure to display the name of the tests (TestCase method names) and approval messages, if any, to generate an unprocessed description of unit tests. I had to do this once to satisfy the request of the QA guy.

Perhaps he believed that the unit tests were performed manually, and simply asked for details about them, does the document make it clear that the unit tests are automatic?