Can't run tests in scratch org with namespace.

[Justin Julicher]

Hi Scott

I have a namespace ‘c_fflib’ and I can’t run tests in this namespace for some strange reason…

I get this error:

Using connection 'fflib2'.
Error 403/Forbidden - INVALID_INPUT: This class name's value is invalid: c_fflib.AnswerTest. Provide the name of an Apex class that has test methods.

Test ignored.

Any Idea?

[Justin Julicher]

Here is my output from running via the CLI:

=== Test Summary
NAME VALUE
─────────────────── ─────────────────────────────────────────────────────────────────
Outcome Passed
Tests Ran 414
Passing 414
Failing 0
Skipped 0
Pass Rate 100%
Fail Rate 0%
Test Start Time May 27, 2019 12:42 PM
Test Execution Time 17745 ms
Test Total Time 16374 ms
Command Time 21771 ms
Hostname redacted
Org Id redacted
Username redacted
Test Run Id 7076D000001tZH0
User Id redacted

[Scott Wells]

Justin, can you enable debug logging for unit test execution as documented here:

http://www.illuminatedcloud.com/support/debuglogging

then reproduce the issue and email me the resulting idea.log for review?

[Justin Julicher]

Hi @Scott Wells

I’ve attached the log - but I created another scratch org which could then run the tests successfully (Same scratch org def so not sure what’s going on there).

You can close this for now as I can get around the issue.

[Scott Wells]

Justin, it looks like it's likely this:

2019-05-29 14:05:13,782 [7276216]  ERROR - enapi.editor.impl.DocumentImpl - Argument for @NotNull parameter 'module' of com/illuminatedcloud/intellij/builder/ForceComBuilderManager.getForceComBuilder must not be null 
java.lang.IllegalArgumentException: Argument for @NotNull parameter 'module' of com/illuminatedcloud/intellij/builder/ForceComBuilderManager.getForceComBuilder must not be null
    at com.illuminatedcloud.intellij.builder.ForceComBuilderManager.$$$reportNull$$$0(SourceFile)
    at com.illuminatedcloud.intellij.builder.ForceComBuilderManager.getForceComBuilder(SourceFile)
    at com.illuminatedcloud.intellij.builder.AsYouTypeEventProcessor$1.documentChanged(SourceFile:127)

which I've fixed for the next build when it's released...which, based on the fact that I've heard about this from at least two people now, might be sooner rather than later. I'll leave this open until I release that build so that we can verify that it's addressed.

[Justin Julicher]

Ok great thanks.

[Justin Julicher]

Ok I’m going to resolve this as I haven’t experienced the issue again…. thanks

[Justin Julicher]

Haven't experienced the issue again after update.

[Scott Wells]

Sounds good. Thanks!