topic Re: ABAP Unit Overview missing in Code Inspector in 7.4 in Application Development and Automation Discussions

ABAP Unit Overview missing in Code Inspector in 7.4

Former Member — Tue, 18 Nov 2014 15:40:36 GMT

Hello everybody,

we are running our unit tests through a code inspector inspection, that gets executed every night in background. Recently we updated our development system to Netweaver 7.40, before we had Netweaver 7.01.

Since the update was installed, the flag "ABAP Unit Overview" is missing in the configuration of the Code Inspector Check for the execution of ABAP Unit Tests. Messages produced by a failing test during the nightly inspection are not saved with the inspection anymore . Understanding the reason of the failure without knowing which test method failed and which error message was produced can be very difficult next day.

Here are the differences we see in our systems in the configuration dialogs in the code inspector:

Configuration in Netweaver 7.01 (Flag "ABAP Unit Overview" can be selected):

Configuration in Netweaver 7.40 (Flag "ABAP Unit Overview" is missing):

How can I save the output of ABAP Unit Tests along with the inspection result as it was possible in Netweaver 7.01 on Netweaver 7.40?

Is there an alternative way of executing ABAP Unit Tests in a nightly job and preserve the messages of failing tests to be able to understand the reason of the failure the next day?

Thank you,

Christian

Re: ABAP Unit Overview missing in Code Inspector in 7.4

former_member183804 — Fri, 09 Jan 2015 13:22:54 GMT

Hello Christian,

you can schedule an EMail notification on failing unit tests by means of report RS_AUCV_RUNNER. Eigther directly in SM37 or in the context menu of SE80s Object Browser "Execute\Unit Tests\Schedule".

Have tried this report already?

Regards

Klaus

Re: ABAP Unit Overview missing in Code Inspector in 7.4

Former Member — Wed, 14 Jan 2015 08:09:17 GMT

Hello Klaus,

many thanks for your reply.

I didn't know this report. After testing a little I think using it would have some advantages over using the Code Inspector in 7.40 for the execution of unit tests:

The mail contains a summary over all executed tests
The mail has ADT-URIs

Compared to the old Code Inspector in 7.01 I'm still missing the detail messages about a failing test.

Example:

The mail generated by report RS_AUCV_RUNNER contains following output for a failing test:

This tells me, that an ASSERT_EQUALS has failed. To understand the reason of the failure, I'm missing the messages that would have been displayed in the analysis section of the ABAP Unit result display:

Meanwhile we have developed a report to send the result of nightly unit tests on our own:

The tests itself are executed through a standard code inspection. Then the result of this code inspection is used to build and send a mail with the test results. As we found out, the detailed messages are still saved along with the inspection, although in transaction SCI there is no way to display them.

We are using the message table returned by CL_CI_INSPECTION->PLAIN_LIST( ). For the items that were generated by CL_SAUNIT_LEGACY_CI_CHECK, the field DETAIL contains the messages from the analysis section serialized as XML.

Regards,

Christian