【发布时间】：2016-08-21 14:50:10
【问题描述】：
我正在尝试为 Spring 4 MVC 项目编写集成测试。在项目中，我使用 Spring Data JPA Repositories 和 Hibernate。
下面是两个文件，集成测试本身和用于设置我的持久性配置的配置。
PersistenceTestConfiguration.java
package <project>.cms.rest.test.configuration;
import <project>.cms.rest.entity.EntityMarker;
import <project>.cms.rest.repository.RepositoryMarker;
import org.jasypt.encryption.pbe.StandardPBEStringEncryptor;
import org.jasypt.hibernate3.encryptor.HibernatePBEEncryptorRegistry;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.data.jpa.repository.config.EnableJpaRepositories;
import org.springframework.jdbc.datasource.embedded.EmbeddedDatabase;
import org.springframework.jdbc.datasource.embedded.EmbeddedDatabaseBuilder;
import org.springframework.jdbc.datasource.embedded.EmbeddedDatabaseType;
import org.springframework.orm.hibernate4.HibernateExceptionTranslator;
import org.springframework.orm.jpa.JpaTransactionManager;
import org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean;
import org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter;
import org.springframework.transaction.PlatformTransactionManager;
import org.springframework.transaction.annotation.EnableTransactionManagement;
import javax.naming.NamingException;
import javax.persistence.EntityManagerFactory;
@Configuration
@EnableTransactionManagement
@EnableJpaRepositories(basePackageClasses = {RepositoryMarker.class})
public class PersistenceTestConfiguration {
@Bean
public EntityManagerFactory entityManagerFactory() throws NamingException {
HibernateJpaVendorAdapter vendorAdapter = new HibernateJpaVendorAdapter();
vendorAdapter.setGenerateDdl(false);
vendorAdapter.setShowSql(true);
LocalContainerEntityManagerFactoryBean factoryBean = new LocalContainerEntityManagerFactoryBean();
factoryBean.setJpaVendorAdapter(vendorAdapter);
factoryBean.setPackagesToScan(EntityMarker.class.getPackage().getName());
factoryBean.setDataSource(dataSource());
factoryBean.afterPropertiesSet();
return factoryBean.getObject();
}
@Bean
public PlatformTransactionManager transactionManager() throws NamingException {
JpaTransactionManager transactionManager = new JpaTransactionManager();
transactionManager.setEntityManagerFactory(entityManagerFactory());
return transactionManager;
}
@Bean
public HibernateExceptionTranslator exceptionTranslator() {
return new HibernateExceptionTranslator();
}
@Bean
public EmbeddedDatabase dataSource() {
EmbeddedDatabaseBuilder builder = new EmbeddedDatabaseBuilder();
return builder.setType(EmbeddedDatabaseType.H2).build();
}
}
我遇到的问题是，虽然我的 PersistenceTestConfiguration 类应该实例化适当的存储库 - 它们作为 null 进入服务类。
如果我手动 @Mock 测试类中的存储库，那么它们在服务中不再为 null，但在调用 .save(entity) 方法时将始终返回 null。
我怀疑我在做一些明显愚蠢但似乎无法弄清楚的事情。
任何正确方向的指针都将不胜感激。
编辑 1：
最简单的测试
package <project>.cms.rest.test.service;
import <project>.cms.rest.resource.PostalAddressResource;
import <project>.cms.rest.service.PostalAddressService;
import <project>.cms.rest.service.impl.PostalAddressServiceImpl;
import <project>.cms.rest.test.configuration.PersistenceTestConfiguration;
import liquibase.Liquibase;
import liquibase.database.jvm.JdbcConnection;
import liquibase.exception.LiquibaseException;
import liquibase.resource.FileSystemResourceAccessor;
import org.junit.After;
import org.junit.Before;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.mockito.InjectMocks;
import org.mockito.MockitoAnnotations;
import org.springframework.jdbc.datasource.embedded.EmbeddedDatabase;
import org.springframework.test.context.ContextConfiguration;
import org.springframework.test.context.TestExecutionListeners;
import org.springframework.test.context.junit4.SpringJUnit4ClassRunner;
import org.springframework.test.context.support.AnnotationConfigContextLoader;
import org.springframework.transaction.annotation.Transactional;
import org.springframework.util.Assert;
import javax.inject.Inject;
import java.sql.Connection;
@Transactional
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(loader = AnnotationConfigContextLoader.class, classes = { PersistenceTestConfiguration.class })
@TestExecutionListeners(mergeMode = TestExecutionListeners.MergeMode.MERGE_WITH_DEFAULTS)
public class PostalAddressServiceIntegrationTest {
@InjectMocks
private PostalAddressService postalAddressService = new PostalAddressServiceImpl();
@Inject
private EmbeddedDatabase database;
@Before
public void setupDatabase() throws java.sql.SQLException, LiquibaseException {
MockitoAnnotations.initMocks(this);
Liquibase liquibase = new Liquibase(
"src/liquibase/liquibase-master.xml",
new FileSystemResourceAccessor(),
new JdbcConnection(database.getConnection())
);
liquibase.update("");
}
@After
public void tearDown() throws java.sql.SQLException, LiquibaseException {
Connection connection = database.getConnection();
JdbcConnection liquibaseConnection = new JdbcConnection(connection);
Liquibase liquibase = new Liquibase(
"src/liquibase/liquibase-master.xml",
new FileSystemResourceAccessor(),
liquibaseConnection
);
liquibase.dropAll();
}
@Test
public void testAddNewPostalAddress() {
PostalAddressResource postalAddressResource = new PostalAddressResource();
postalAddressResource.setBuildingNameOrNumber("1");
postalAddressResource.setFirstLine("Test Lane");
postalAddressResource.setSecondLine("Testville");
postalAddressResource.setCountry("Testshire");
postalAddressResource.setPostCode("TE5 7ER");
postalAddressResource.setCountry("United Kingdom");
PostalAddressResource result = postalAddressService.createPostalAddress(postalAddressResource);
Assert.notNull(result);
}
}
生成的堆栈跟踪
java.lang.NullPointerException
at <project>.cms.rest.service.impl.PostalAddressServiceImpl.createPostalAddress(PostalAddressServiceImpl.java:66)
at <project>.cms.rest.test.service.PostalAddressServiceIntegrationTest.testAddNewPostalAddress(PostalAddressServiceIntegrationTest.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:254)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:89)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:193)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
PostalAddressServiceImpl第66行如下：
} while(repository.countByPublicId(publicId) > 0);
编辑 2：
创建一个直接使用存储库而不是通过服务工作的测试，具有：
@Inject
private PostalAddressRepository repository;
在顶部表现自己。
因此，当@InjectMocks 应该连接 Service 类的依赖项时似乎出现了问题，导致存储库为空。
【问题讨论】：
-
如果没有堆栈跟踪，就很难说出任何事情。有一个方便的吗？此外，它通常有助于更多地分解复制示例，以确保它不是这里正在播放的数十个导致问题的部分之一。一个普通的存储库引导程序（没有所有安全、服务等）是否会导致同样的问题？
-
@OliverGierke 堆栈跟踪只是显示当我在其上调用方法时服务使用的存储库为空。 Spring 代码中根本没有任何内容。我将尝试将其缩小到一个工作示例，但没有什么可以删除的
-
很抱歉，如果没有更多信息或更精简的示例，很难找出问题所在，因为它几乎可能是任何问题。
-
@OliverGierke 用我能想到的最简单的测试类编辑了我的问题 - 并提供了一个示例堆栈跟踪
-
再次抱歉，但仍有大量额外注射。 Liquibase 与此有什么关系？有3个测试用例，没有一个。由于仍然没有堆栈跟踪，我们甚至不会在 NPE 发生的哪一行为空。抱歉，您找不到任何远程可以通过这种方式为您提供帮助的人。
标签： spring testing repository integration spring-data-jpa