Failed to start: 0 passed, 1 not started

[Jaap Branderhorst]

I am using a new setup with the following IntelliJ environment:

IntelliJ IDEA 2016.3.4 Build #IU-163.12024.16, built on January 31, 2017 Licensed to Appsolutely / Jaap Branderhorst You have a perpetual fallback license for this version Subscription is active until February 9, 2018 JRE: 1.8.0_112-release-408-b6 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

I use the following Illuminated Cloud setup: Version 1.7.8.5 Build 20170221102025

When trying to run an Apex unit test I get the following error: Failed to start: 0 passed, 1 not started

Trying to run the same test from within my org, everything works.

I attached my idea.log and I see that the log has a detected an issue with the Tooling API:

2017-03-05 17:08:36,928 [ 163331] WARN - cloud.client.ForceComApiClient - Status code 404 returned trying to retrieve 'https://cs88.salesforce.com/services/data/v39.0/tooling/sobjects/ApexLog/null/Body/': Not Found 2017-03-05 17:08:36,928 [ 163331] WARN - inatedcloud.client.ApexLogUtil - Empty log body returned for Apex log ID null 2017-03-05 17:08:36,930 [ 163333] WARN - ner.GeneralTestEventsProcessor - [Apex]: Trying to finish nonexistent node: TestFailedEvent{name='<unknown>', id='4', localizedFailureMessage='line 1, column 64: trigger body is invalid and failed recompilation: Entity is not org-accessible entity name: Question', stacktrace='null', isTestError=false} 2017-03-05 17:08:36,931 [ 163334] WARN - ner.GeneralTestEventsProcessor - [Apex]: Trying to finish nonexistent node: TestFinishedEvent{name='<unknown>', id='4', duration=-1} 2017-03-05 17:08:36,932 [ 163335] WARN - ner.GeneralTestEventsProcessor - [Apex]: Trying to finish nonexistent node: TestSuiteFinishedEvent{name='chatter_answers_question_escalation_to_case_trigger', id='3'} 2017-03-05 17:08:36,933 [ 163336] WARN - ner.GeneralTestEventsProcessor - [Apex]: Unexpected running nodes: [{id=2, parentId=1, name='testBehavior', isSuite=false, state=RUNNING}]

I suspect something is wrong with the Tooling API or with the integration. Could you please have a look into this since this removes a very critical function of your great tool.

[Scott Wells]

Duplicate of #404.

[Scott Wells]

I'm 99% sure that this is the same issue logged in issue #404. If this isn't resolved when I resolve that issue, I'll reopen this one.

[Jaap Branderhorst]

Just checked and indeed when all code compiles (including code not related to the test class), it works. Thanks! As always a REALLY fast response.