我正在从 grails 1.3.6 升级到 2.2.4 并通过我所有的单元测试。我一直在用 @Mock 注释替换 mockDomain 等等。我的一项测试是验证 ID 是否保持唯一,如果 ID 已经存在则失败。这似乎不再像预期的那样失败。测试如下:
import grails.test.*
import grails.test.mixin.TestFor
import grails.test.mixin.Mock
@Mock(SecurityValue)
@TestFor(SecurityValue)
class SecurityValueTests{
void testUniqueId() {
def validEntry = new SecurityValue(id:"id",propertyName:"propertyName",userId:"testUser",componentId:1000)
validEntry.id = "id"
def saved = validEntry.save(flush:true, failOnError:true)
assertNotNull saved
def validEntry2 = new SecurityValue(id:"id",propertyName:"propertyName1",userId:"testUser3")
validEntry2.id = "id"
def saved2 = validEntry2.save(flush:true, failOnError:true)
def all = SecurityValue.findAll()
assertNull saved
}
}
领域:
class SecurityValue {
String id
String propertyName
String userId
//String userName
Long componentId
static constraints =
{
id unique:true, size: 1..100
propertyName nullable: false, size: 1..100
userId nullable: false, size: 1..10
componentId (
nullable: true, size: 1..10
)
}
static mapping =
{
table 'pac_sys.security_value'
id column:'id', type: 'string', generator: 'assigned'
version false;
}
}
我得到的问题是这validEntry2.save
条线没有失败。我添加了该findAll
行以查看正在存储哪些数据,并且似乎validEntry
只是被validEntry2
.
我在这里错过了一个模拟陈述或其他东西吗?
这是应用 jonnybot 的答案后测试的样子。它现在有一个 shouldFail 方法而不是 assertNull 并且可以正常工作。
void testUniqueId() {
def validEntry = new SecurityValue(id:"id",propertyName:"propertyName",userId:"testUser",componentId:1000)
validEntry.id = "id"
mockForConstraintsTests(SecurityValue, [validEntry])
def validEntry2 = new SecurityValue(id:"id",propertyName:"propertyName1",userId:"testUser3")
validEntry2.id = "id"
shouldFail(grails.validation.ValidationException)
{
def saved2 = validEntry2.save(flush:true, failOnError:true)
}
}