No tests found?

[alcatrazescapee]

No tests found?

[alcatrazEscapee]

Interesting. Two things come of note:

• Change the logging level from unittest to debug (helpful if you're doing any debugging as the unittest log level can hide some actual errors).
• What is the log output (at debug level) for this line?

Found supplied mod coordinates [some stuff should be here]

That should match the classpath roots that are being passed into the JUnit test discover-er, that's my first place I'd check.

[robotgryphon]

Tried doing just that while troubleshooting, actually. I didn't see anything particularly obvious in the log, it just completed with nothing found.. also, the coords did look correct (paths were fine, classes were built there).

I'll try poking at it a bit more, see if I can't get a log to attach here shortly. Thanks.

[robotgryphon]

Here are the debug and latest log files from the unit test run.

Updated to 1.4.3 and regenerated everything before the run, just to make sure it was the latest version. The most interesting thing I notice is the modlauncher "Current naming domain is 'mcp'" line.

Much further down (formatted with extra lines for easy reading):

[02Sep2021 14:53:19.145] [Server thread/DEBUG] [UnitTests/]: Found supplied mod coordinates [[
  D:\compact-crafting\build\resources\main, 
  D:\compact-crafting\build\classes\java\test, 
  D:\compact-crafting\build\resources\api, 
  D:\compact-crafting\build\resources\test, 
  D:\compact-crafting\build\classes\java\api, 
  D:\compact-crafting\build\classes\java\main
]]
[02Sep2021 14:53:19.743] [Server thread/UNITTEST] [UnitTests/]: Did not discover any tests to run.

So it definitely looks like it's picking up all three modules (api, main, and test) as well.