Tec*_*nch 5 spring h2 spring-test spring-boot jhipster
我在Spring Web应用程序中使用Liquibase.我有一堆实体,在用户,帐户,发票,许可证等每个实体的集成测试中都有数百个REST API测试.我的所有集成测试在按类运行时都会通过,但是当它们一起运行时很多都会失败gradle test.测试之间很可能存在数据冲突,我现在不想花时间修复清理数据.我更喜欢在每节课后放弃数据库和上下文.我想我可以@DirtiesContext在课堂上使用,所以我用它进行了测试注释.
@RunWith(SpringRunner.class)
@SpringBootTest(classes = {Application.class, SecurityConfiguration.class},
webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
@DirtiesContext
public class InvoiceResourceIntTest {
Run Code Online (Sandbox Code Playgroud)
我看到在添加注释之后,Web应用程序上下文会针对每个类启动,但是当Liquibase初始化发生时,查询不会运行,因为校验和匹配.由于这是一个内存中的数据库,我期望数据库与spring上下文一起被销毁,但它没有发生.
我也设置了jpa hibernate ddl-auto,create-drop但这没有帮助.我正在考虑的下一个选项是,而不是mem将h2db写入文件,并在我的集成测试类文件的@BeforeClass中删除该文件.我更喜欢在内存中自动删除db而不是在测试中管理它,但是想在这里尝试作为最后一个选项.谢谢您的帮助.
更新:
我更新了测试如下.
@RunWith(SpringRunner.class)
@SpringBootTest(classes = {Application.class, SecurityConfiguration.class},
webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT,
properties = "spring.datasource.name=AccountResource")
@DirtiesContext
public class AccountResourceIntTest {
Run Code Online (Sandbox Code Playgroud)
我为每个集成测试设置了唯一的名称.我仍然没有看到数据库是新的,因为我只能在日志中看到Liquibase校验和.
这是app.yml的app配置
spring:
datasource:
driver-class-name: org.h2.Driver
url: jdbc:h2:mem:myApp;DB_CLOSE_DELAY=-1
name:
username:
password:
jpa:
database-platform: com.neustar.registry.le.domain.util.FixedH2Dialect
database: H2
open-in-view: false
show_sql: true
hibernate:
ddl-auto: create-drop
naming-strategy: org.springframework.boot.orm.jpa.hibernate.SpringNamingStrategy
properties:
hibernate.cache.use_second_level_cache: false
hibernate.cache.use_query_cache: false
hibernate.generate_statistics: true
hibernate.hbm2ddl.auto: validate
Run Code Online (Sandbox Code Playgroud)
如果重要的话,我的项目是从JHipster 2.x版本生成的.请参阅下面的我的数据库配置类.AppProperties是特定于应用程序的属性(与Spring不同).
@Configuration
public class DatabaseConfiguration {
private static final int LIQUIBASE_POOL_INIT_SIZE = 1;
private static final int LIQUIBASE_POOL_MAX_ACTIVE = 1;
private static final int LIQUIBASE_POOL_MAX_IDLE = 0;
private static final int LIQUIBASE_POOL_MIN_IDLE = 0;
private static final Logger LOG = LoggerFactory.getLogger(DatabaseConfiguration.class);
/**
* Creates data source.
*
* @param dataSourceProperties Data source properties configured.
* @param appProperties the app properties
* @return Data source.
*/
@Bean(destroyMethod = "close")
@ConditionalOnClass(org.apache.tomcat.jdbc.pool.DataSource.class)
@Primary
public DataSource dataSource(final DataSourceProperties dataSourceProperties,
final AppProperties appProperties) {
LOG.info("Configuring Datasource with url: {}, user: {}",
dataSourceProperties.getUrl(), dataSourceProperties.getUsername());
if (dataSourceProperties.getUrl() == null) {
LOG.error("Your Liquibase configuration is incorrect, please specify database URL!");
throw new ApplicationContextException("Data source is not configured correctly, please specify URL");
}
if (dataSourceProperties.getUsername() == null) {
LOG.error("Your Liquibase configuration is incorrect, please specify database user!");
throw new ApplicationContextException(
"Data source is not configured correctly, please specify database user");
}
if (dataSourceProperties.getPassword() == null) {
LOG.error("Your Liquibase configuration is incorrect, please specify database password!");
throw new ApplicationContextException(
"Data source is not configured correctly, "
+ "please specify database password");
}
PoolProperties config = new PoolProperties();
config.setDriverClassName(dataSourceProperties.getDriverClassName());
config.setUrl(dataSourceProperties.getUrl());
config.setUsername(dataSourceProperties.getUsername());
config.setPassword(dataSourceProperties.getPassword());
config.setInitialSize(appProperties.getDatasource().getInitialSize());
config.setMaxActive(appProperties.getDatasource().getMaxActive());
config.setTestOnBorrow(appProperties.getDatasource().isTestOnBorrow());
config.setValidationQuery(appProperties.getDatasource().getValidationQuery());
org.apache.tomcat.jdbc.pool.DataSource dataSource = new org.apache.tomcat.jdbc.pool.DataSource(config);
LOG.info("Data source is created: {}", dataSource);
return dataSource;
}
/**
* Create data source for Liquibase using dba user and password provided for "liquibase"
* in application.yml.
*
* @param dataSourceProperties Data source properties
* @param liquibaseProperties Liquibase properties.
* @param appProperties the app properties
* @return Data source for liquibase.
*/
@Bean(destroyMethod = "close")
@ConditionalOnClass(org.apache.tomcat.jdbc.pool.DataSource.class)
public DataSource liquibaseDataSource(final DataSourceProperties dataSourceProperties,
final LiquibaseProperties liquibaseProperties, final AppProperties appProperties) {
LOG.info("Configuring Liquibase Datasource with url: {}, user: {}",
dataSourceProperties.getUrl(), liquibaseProperties.getUser());
/*
* This is needed for integration testing. When we run integration tests using SpringJUnit4ClassRunner, Spring
* uses
* H2DB if it is in the class path. In that case, we have to create pool for H2DB.
* Need to find a better solution for this.
*/
if (dataSourceProperties.getDriverClassName() != null
&& dataSourceProperties.getDriverClassName().startsWith("org.h2.")) {
return dataSource(dataSourceProperties, appProperties);
}
if (dataSourceProperties.getUrl() == null) {
LOG.error("Your Liquibase configuration is incorrect, please specify database URL!");
throw new ApplicationContextException("Liquibase is not configured correctly, please specify URL");
}
if (liquibaseProperties.getUser() == null) {
LOG.error("Your Liquibase configuration is incorrect, please specify database user!");
throw new ApplicationContextException(
"Liquibase is not configured correctly, please specify database user");
}
if (liquibaseProperties.getPassword() == null) {
LOG.error("Your Liquibase configuration is incorrect, please specify database password!");
throw new ApplicationContextException(
"Liquibase is not configured correctly, please specify database password");
}
PoolProperties config = new PoolProperties();
config.setDriverClassName(dataSourceProperties.getDriverClassName());
config.setUrl(dataSourceProperties.getUrl());
config.setUsername(liquibaseProperties.getUser());
config.setPassword(liquibaseProperties.getPassword());
// for liquibase pool, we dont need more than 1 connection
config.setInitialSize(LIQUIBASE_POOL_INIT_SIZE);
config.setMaxActive(LIQUIBASE_POOL_MAX_ACTIVE);
// for liquibase pool, we dont want any connections to linger around
config.setMaxIdle(LIQUIBASE_POOL_MAX_IDLE);
config.setMinIdle(LIQUIBASE_POOL_MIN_IDLE);
org.apache.tomcat.jdbc.pool.DataSource dataSource = new org.apache.tomcat.jdbc.pool.DataSource(config);
LOG.info("Liquibase data source is created: {}", dataSource);
return dataSource;
}
/**
* Creates a liquibase instance.
*
* @param dataSource Data source to use for liquibase.
* @param dataSourceProperties Datasource properties.
* @param liquibaseProperties Liquibase properties.
* @return Liquibase instance to be used in spring.
*/
@Bean
public SpringLiquibase liquibase(@Qualifier("liquibaseDataSource") final DataSource dataSource,
final DataSourceProperties dataSourceProperties, final LiquibaseProperties liquibaseProperties) {
// Use liquibase.integration.spring.SpringLiquibase if you don't want Liquibase to start asynchronously
SpringLiquibase liquibase = new AsyncSpringLiquibase();
liquibase.setDataSource(dataSource);
liquibase.setChangeLog("classpath:config/liquibase/master.xml");
liquibase.setContexts(liquibaseProperties.getContexts());
liquibase.setDefaultSchema(liquibaseProperties.getDefaultSchema());
liquibase.setDropFirst(liquibaseProperties.isDropFirst());
liquibase.setShouldRun(liquibaseProperties.isEnabled());
return liquibase;
}
}
Run Code Online (Sandbox Code Playgroud)
这是因为每个测试共享相同的数据库,并且H2的生命周期不在我们的控制之下.如果您启动进程(VM)并需要一个名为的数据库foo,请关闭应用程序上下文,启动一个新的并foo再次要求您将获得相同的实例.
在即将1.4.2发布的版本中,我们添加了一个属性,用于在启动时为数据库生成唯一名称(请参阅参考资料spring.datasource.generate-unique-name),默认情况下该值将设置为1.5.
在此期间,您可以标注每个测试@SpringBootTest(properties="spring.datasource.name=xyz"),其中xyz是需要单独的DB测试不同.
如果我理解正确的话,liquibase 会处理数据库状态。对于每个文件以及测试数据,liquibase 都会在表中创建一个校验和,以检查某些内容是否已更改。h2 实例在 @DirtiesContext 之后仍然存在,因此校验和仍然存在于数据库中。Liquibase 认为一切都是正确的,但测试数据可能已经改变。
要强制 liquibase 删除数据库并重新创建一个全新的数据库,您必须在 application.yml 中设置属性(用于测试的属性):
liquibase:
contexts: test
drop-first: true
Run Code Online (Sandbox Code Playgroud)
或者作为替代方案,您可以对其进行硬编码:
liquibase.setDropFirst(true);
Run Code Online (Sandbox Code Playgroud)
您可以使用 @DirtiesContext 注释您的测试,这会减慢测试速度,因为整个应用程序上下文都会重建。
或者您可以创建一个自定义的 TestExecutionListener,这要快得多。我创建了一个自定义 TestExecutionListener,它重新创建数据库并保留上下文。
public class CleanUpDatabaseTestExecutionListener
extends AbstractTestExecutionListener {
@Inject
SpringLiquibase liquibase;
@Override
public int getOrder() {
return Ordered.HIGHEST_PRECEDENCE;
}
@Override
public void afterTestClass(TestContext testContext) throws Exception {
//This is a bit dirty but it works well
testContext.getApplicationContext()
.getAutowireCapableBeanFactory()
.autowireBean(this);
liquibase.afterPropertiesSet();
}
Run Code Online (Sandbox Code Playgroud)
如果您使用 TestExecutionListener,则必须将此侦听器添加到您的测试中:
@RunWith(SpringJUnit4ClassRunner.class)
@SpringApplicationConfiguration(classes = Application.class)
@WebAppConfiguration
@IntegrationTest
@TestExecutionListeners(listeners = {
DependencyInjectionTestExecutionListener.class,
TransactionalTestExecutionListener.class,
CleanUpDatabaseTestExecutionListener.class,
})
public class Test {
//your tests
}
Run Code Online (Sandbox Code Playgroud)
注意:请勿将@DirtiesContext和TestExecutionListener一起使用,这会导致错误。
| 归档时间: |
|
| 查看次数: |
3182 次 |
| 最近记录: |