spring-test | 本课程主要是使用 Spring技术栈 dubbo 开发一个类似当当的图书电商后台的实战教程。 | Messaging library

Almost all Wicket dependencies are 8.14.0 but few are 8.13.0 (not really a problem but better keep them in sync):

• org.apache.wicket:wicket-bean-validation:jar:8.13.0:compile
• com.googlecode.wicket-jquery-ui:wicket-jquery-ui:jar:8.13.0:compile
• com.googlecode.wicket-jquery-ui:wicket-jquery-ui-core:jar:8.13.0:compile

The real problem is:

The most recommended solution would be to upgrade the entire project. If not, the easiest solution is to rely on spring-boot-starter-test:

You need to add a public default constructor (one without a parameters) in AuthController.

Then create a method with annotation @PostConstruct to initialize your AuthController with values that it needs to work properly.

I personally prefer dependency injection through setters because it's easier to create test in that way.

Here you have a nice example of how to do dependency injection with setters: https://www.amitph.com/spring-setter-injection-example/

You are casting mockAccount to a list without it actually being a list, that's probably why the mock fails.

Acording to this answer: https://stackoverflow.com/a/51236918/16651073 tomcat falls back to default logging if it can resolve the location

Can you try to save the properties without the spaces.

Like this: logging.file.name=application.logs

Spring 3.2.0.RELEASE uses asm 4.0, which does not support Java 8 or higher.

Since Java 7 is not supported any more, you should upgrade Spring to the latest patch release:

It seems the issue lies in the fact with how you try to access your DB in gitlab.

When you add the mysql service

Consider changing the @DataJpaTest with 2 other annotations the @SpringBootTest with @AutoConfigureTestDatabase.

If you inspect the documentation describing @DataJpaTest you can see that this annotation switches of auto configuration and does not bring the complete application context up as you would normally expect when the application loads.

This annotation is used so that spring creates everything necessary just for JPA layer (meaning your repository), so that the JPA layer can be tested.

Using this annotation will disable full auto-configuration and instead apply only configuration relevant to JPA tests.

It is also adviced from the java doc that

If you are looking to load your full application configuration, but use an embedded database, you should consider @SpringBootTest combined with @AutoConfigureTestDatabase rather than this annotation.

Since you're using an h2 in-memory database to run tests, and you want to actually use that database in your tests, you shouldn't really be mocking anything.

Your mocking doesn't work because the MyRepositoryImpl is typically initialized by Spring, and that process is much more complicated than plugging in an EntityManager.

I think what you want to do is more like what's described here https://www.baeldung.com/spring-testing-separate-data-source

So you would have a src/test/resources/application.properties file that overrides the datasource properties. Then you just @Autowired your repository into your test class like normal.