SFDX Deploy-To-All not finding tests to run, only jumps to stub classes

Issue #1280 resolved
Dennis Grzyb created an issue

Running the latest IC version, I have run into troubles when working with an SFDX Deploy-to-all Project. I wanted to run a test class to find out about its coverage, but no tests were reported found. Invalidating Caches / Restarting also did not solve the issue here. I have also made a new Project for the Org, but that also did not solve the issue.

Also, the functionality to jump to a class/method only jumps me to a stub of the class, displaying all available methods but no contents.

My colleague who is also working with an SFDX DtA project, but on another Org, can report the same problem.

Comments (6)

  1. Scott Wells repo owner

    Dennis, there's currently a bug that I hope to fix this week or next where if a stub version of a class is found in the offline symbol table and in the local project source, some navigation will go to the OST stub version. The workaround is to regenerate your OST which will omit generation of stub classes for anything found locally, then the source version of the class will be used for navigation instead. Please let me know if that workaround doesn't give you what you need right now, and I'll try to fix this once and for all ASAP.

  2. Dennis Grzyb reporter

    Regeneration has worked indeed, do you know about what can be done to get Tests back running again though?

  3. Dennis Grzyb reporter

    Strangely enough, it seems like regeneration of the OST has also made this work again (because there was nothing else I did between then and now) and now my tests are found again ... If this comes up again I'll have Debug Logging active, though.

  4. Scott Wells repo owner

    That's not entirely surprising. I bet that IC was looking at the stub classes when scanning for @IsTest and testMethod annotations/modifiers, and the stubs don't include those. As a result, it was thinking that those were not test classes. I'll definitely address the shared underlying issue ASAP so that this problem just goes away.

  5. Scott Wells repo owner

    OST regeneration took care of both issues, and I'll be fixing the underlying problem that required OST regeneration shortly.

  6. Log in to comment