Hi there Scott - first THANK YOU for a superb product that has saved myself and my colleagues man-months of work.
I am not sure if my issue is pilot error, hopefully it is. I have a managed package project that has been running great under Illuminated Cloud for over a year. Recently (in the last few days, hard to pinpoint exactly when) I have started having trouble getting apex tests to run on a Developer org that I have been using since I started using Illuminated Cloud. It is a standard developer org, not set up with any namespaces or packages. The error is
Error 403/Forbidden - INVALID_INPUT: This class name's value is invalid: nbavs.TestAPI. Provide the name of an Apex class that has test methods.
The problem appears to be the Organization Namespace setting in this org's connection - the namespace should be <unassigned> (other Developer org connections that work have an <unassigned> org namespace) but this connection uses the managed package’s namespace. If I create a new Oauth connection for this org, it starts off <unassigned> and the tests work, but at some point (not sure what triggers it) the namespace is no longer unassigned, and the tests start failing.
I cannot see a way to modify this setting.
Have you come across this issue? Have you any suggestions to try?
I have tried creating a new Developer org and connecting to that and deploying source, and it shows the same issue.
My IC build: 184.108.40.206 202000723122844
My IntelliJ IDEA build: 2020.1.3 (ultimate)