Debugging of ABAP Unit Test not possible anymore

[eugen_soydas2]

Hi Community,

today i updated my ADT Version (via Check for Updates) to 3.04 (comp.sap.adt.core) on Eclipse Photon Release 4.8.0 with a SAP NW7.50 SP10 as backend.

After i tried to debugg my unit test, i noticed that the debugger doesn't stop anymore. Even i set a hard coded breakpoint (BREAK-POINT) inside the test methode or inside the methode under test, the debugger doesn't stop.

If I execute my application directly, the debugger starts when it reaches the method (which i like to test).

So for me it seems there is an issues with debugging of abap unit tests since my update.

Does anyone else have a problem with debugging abap unit tests?

Cheers

Eugen

[Armin_Beil]

Hi Eugen,

could you please create a customer incident for this issue? Component would be BC-DWB-AIE-TST.

Best regards,
Armin

[eugen_soydas2]

It launches the tests, but i can't stop inside a test mehode if a set a break point.

I get the test result in the ABAP Unit View, but it's not possible to debugg it.

[JeffCarty]

I'm on 7.40 SP13, ADT 3.04 and Eclipse 2018-12 and everything works fine.

[Armin_Beil]

Hi Eugen,

this might be the same issue as in https://answers.sap.com/questions/12688037/did-the-latest-adt-324-break-the-eclipse-debugger.html. Correction for that issue is planned for the next ADT release 3.4, which is planned to become available beginning of August (via update site probably on 01.08).

Best regards,
Armin

[Armin_Beil]

Hello Eugen,

meanwhile also others reported similar issues after updating ADT (https://answers.sap.com/questions/12688037/did-the-latest-adt-324-break-the-eclipse-debugger.html). It seems the issues disappear at a certain point in time (e.g. during a reboot) and do not occur again. I made a couple of tests, including the ADT update, but I was not able to reproduce the issue.

Is the issue still reproducible on your side?

I will make further tests and we are also about to improve our internal tracing in order to catch this issue.

Best regards,
Armin

[bruce_hartley]

I wonder if the system changed the way it executes the tests - try setting an external breakpoint as opposed to a regular one and see what happens. The reason I mention this is that if the test is now being run via something that kicks it off as a separate thread (like how an aRFC works for example), the debugger won't stop unless you have an external break point set.

[eugen_soydas2]

So meanwhile i'm on AiE 2018-12 with ADT 3.04 on 7.50 SP10 and have still the same issue. I guess it has to do something with the backend.

Will continue my investigation and report it.

[Sandra_Rossi]

The version of ABAP kernel may be of some interest too.

[Sandra_Rossi]

I had the same issue (maybe with 7.51, neon). Upgrading everything (7.52, photon) solved the issue, 3 months that I don't have any issue, but I can't say what really solved.

Maybe one solution, without reinstalling anything, is to change the source code of the CUT and the source code of unit tests, activate, set the breakpoint again, and run the tests again.

[former_member249109]

CTRL + SHIFT + F10 does not launch the tests?