In my project, after importing maven dependencies or after clean command, maven refuses to see tests. Why is that?

Question

Java

I write tests using Cucumber+Java
Project structure

In general, the essence is this. I have Allure screwed on, with its wonderful reports. We launch it with the following commands:
mvn clean test
mvn sit
mvn jetty:run
So, everything fails at the initial stage, with the Maven clean command. Details.

[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ b2b-web-test ---
[INFO] No sources to compile

These are the lines that appear when we test after cleaning. If you run the tests separately, using the IDE (and I use IDEA), and then just mvn test, and everything else to generate a report, then everything is fine - the report is formed, and pleases the eye. But clean leads to the fact that Maven does not seem to see the tests.
There is another feature, when I import changes to pom.xml, then IDEA stops seeing the src/test folder, JUnit refuses to run tests until I mark the test folder as a test folder.
Comrades! Lord! Friends!!! Colleagues... There is no urine, I don’t understand what to do! Will the hand and mouth of reason shed light on the darkness of this hopelessness?

Answer 1

Adjust the directory structure to match: https://maven.apache.org/guides/introduction/intro...