debugging tests can't find any source code, even the test that's running

[dabraham02124]

Problem Statement

When I debug a test, it can't find the code for the project, even the code that is the test that I'm running.

This happened when I updated my testng plugin recently (I don't know what I had before I updated, but several months old). Since then I've tried updating to the latest beta of the plugin (BTW, the run/debug buttons in the code are neat, thank you). Still there.

Then I tried uninstalling, then reinstalling the latest release, still there.

I can get around it for a specific debug target, by clicking on the "Edit Source Lookup Path..." button, then "Add...", then "Java Project", click the box next to the name of the project that my test is in, then "OK", then "OK".

It continues to work if I debug that specific target again. But if I debug anything else, even another test in the same file, I have to go through the rigamarole again.

Any relate message in "Error Log" view

"Windows -> Show View -> Others -> Error Log"

Since I reinstalled the last time, when I filter on "test" the only thing that I see is "[TestNGLaunchConfigurationDelegate] Launching:"

The Dependency Management tool for your project

• Maven

Operating System

• OSX

Eclipse

Version: 2020-03 (4.15.0)
Build id: 20200313-1211

[missedone]

thanks @dabraham02124 for reporting this, i can reproduce this on Eclipse 2020-03 as well. probably this new Eclipse version changed something internally.
haven't look in depth yet.

@gayanper, could you like to have a try to fix this issue?

Thanks
Nick

[gayanper]

Please switch the m2e snapshots this should be fixed there. This is a m2e bug.

[dabraham02124]

@gayanper thank you very much, yes, that did it.

For the next person who bumps into this, I updated m2e from 1.15.0.20200310-1832 to 1.16.0.20200416-1943 by installing from here.

What I did (which may be overly paranoid, but worked) was:

1. uninstall the testng plugin & restart eclipse
2. update m2e with the link above & restart eclipse
3. install the testng plugin & restart eclipse

[gayanper]

@dabraham02124 simply upgrading the m2e will be sufficient as well 🙂

[missedone]

Thank you @gayanper