Grails 2.0集成测试污染? [英] Grails 2.0 integration test pollution?
问题描述
我刚刚从1.3.7升级到grails-2.0,我从hsqldb切换到h2。
有没有人指出我应该寻找哪个方向来解决这个(测试污染)问题?
域模型
整合测试:
class SeriesIntegrationTests扩展GrailsUnitTestCase {
系列系列
插曲插曲
保护无效setUp(){
super.setUp()
系列=新系列(ttdbId:2348);
episode = new Episode(ttdbId:2983,season:0,episodeNumber:0,series:series);
}
protected void tearDown(){
super.tearDown()
}
void testCreateSeries(){
series.save()
assertFalse(不应该有验证错误:$ series.errors,series.hasErrors())
assertEquals(应该是存储在数据库中的一个系列,1,Series。 count())
}
void testCreateEpisode(){
series.save()
episode.save()
assertFalse(should not have验证错误:$ episode.errors,episode.hasErrors())
assertEquals(应该是存储在数据库中的一集,1,Episode.count())
}
void testCreateSeriesAndAddEpisode(){
series.addToEpisodes(episode)
series.save(flush:true)
series.refresh()
assertEquals(series should contain one episode ,1,series.episodes.size())
}
void testDeleteSeriesAndCascadeToEpisode(){
series.addToE
series.save(flush:true)
series.delete(flush:true)
assertEquals(0,Episode.count())
assertEquals(0, Series.count())
}
void testDeleteSeriesAndCascadeToBackdropImage(){
series.backdrop = new Image();
series.backdrop.binaryData = new byte [0]
series.save(flush:true)
assertFalse(series.hasErrors())
assertEquals(1 ,Image.count())
series.delete(flush:true)
assertEquals(0,Image.count())
}
}
我的解决方案将所有单元测试升级到grails 2.0方法做测试。完成后,每个测试都会通过。所以看起来单元测试不知何故污染了集成测试。但只限于某些硬件配置。
So i have a small integration test that houses 5 tests in total. Running that test exclusively results in all tests passed. However running my entire test suite results in 4 test failures of the 5.
I've just recently upgraded to grails-2.0 from 1.3.7 and i switched from hsqldb to h2.
Has anyone any pointers in which direction i should be looking in order to fix this (test-pollution) problem?
Domain model
Integration test:
class SeriesIntegrationTests extends GrailsUnitTestCase {
Series series
Episode episode
protected void setUp() {
super.setUp()
series = new Series(ttdbId: 2348);
episode = new Episode(ttdbId: 2983, season: 0, episodeNumber: 0, series: series);
}
protected void tearDown() {
super.tearDown()
}
void testCreateSeries() {
series.save()
assertFalse("should not have validation errors : $series.errors", series.hasErrors())
assertEquals("should be one series stored in db", 1, Series.count())
}
void testCreateEpisode() {
series.save()
episode.save()
assertFalse("should not have validation errors : $episode.errors", episode.hasErrors())
assertEquals("should be one episode stored in db", 1, Episode.count())
}
void testCreateSeriesAndAddEpisode() {
series.addToEpisodes(episode)
series.save(flush: true)
series.refresh()
assertEquals("series should contain one episode", 1, series.episodes.size())
}
void testDeleteSeriesAndCascadeToEpisode() {
series.addToEpisodes(episode)
series.save(flush: true)
series.delete(flush: true)
assertEquals(0, Episode.count())
assertEquals(0, Series.count())
}
void testDeleteSeriesAndCascadeToBackdropImage() {
series.backdrop = new Image();
series.backdrop.binaryData = new byte[0]
series.save(flush: true)
assertFalse(series.hasErrors())
assertEquals(1, Image.count())
series.delete(flush: true)
assertEquals(0, Image.count())
}
}
My solution as to upgrade all the unit tests to grails 2.0 method of doing tests. When this was done, every test passed. So it seem's that unit tests somehow polluted integration tests. But only on certain hardware configurations.
这篇关于Grails 2.0集成测试污染?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!