ACTION CONTROLLER:Intégration de test pour le contrôleur
def deleteDept = {
def departmentInstance = Department.findByName(params.department.name)
if (!departmentInstance) {
println "no dept instance"
throw new org.codehaus.groovy.grails.exceptions.NewInstanceCreationException ("could not create DeptInstance for ${params.department.name}")
} else if (departmentInstance.paySvcs && !departmentInstance.paySvcs.isEmpty()){
println "instance with paySvcs"
// !!!! do not delete the department if it has payment services !!!!
departmentInstance.errors.reject('department.do.not.delete.message')
// render(view: "editDept", model: [departmentInstance: departmentInstance])
redirect(action: "editDept", id: departmentInstance.id)
} else{
println "proceed to delete"
try {
departmentInstance.delete(flush: true)
flash.message = "${message(code: 'default.deleted.message', args: [message(code: 'department.label', default: 'Department'), departmentInstance.name])}"
redirect(action: "appAdmin", id: departmentInstance.id)
}
catch (org.springframework.dao.DataIntegrityViolationException e) {
println "something went wrong"
flash.message = "${message(code: 'default.not.deleted.message', args: [message(code: 'department.label', default: 'Department'), departmentInstance.name])}"
redirect(action: "editDept", id: departmentInstance.id)
}
}
}
Test d'intégration:
def AppAdminController controller = new AppAdminController() // create the controller
controller.metaClass.message = { Map p -> return "foo" } // message dummy returning garbage - work around the controller message exception
controller.params.department = [name:"dept1", phone:"817-273-3260", g_password:"password", street:"Main St.", g_userID:"user", unitCode:"1234567", email:"[email protected]", zip:"75097", fax:"817-273-2222"]
def dept2 = new Department (name: "Dept2", unitCode: "1234568", street: "Main St.", zip: "75097", fax: "817-273-2222", phone: "817-273 3260", email: "[email protected]", g_userID: "user", g_password: "password")
def dept1 = new Department (name: "Dept1", unitCode: "1234568", street: "Main St.", zip: "75097", fax: "817-273-2222", phone: "817-273 3260", email: "[email protected]", g_userID: "user", g_password: "password")
def math = new PaySvc()
def another = new PaySvc()
dept.paySvcs = []
dept.paySvcs.add(math)
dept.paySvcs.add(another)
mockDomain(Department, [dept1, dept2])
def svcTest = Department.findByName("Dept1")
assertNotNull svcTest // record Dept1 exists
assertEquals 2, svcTest.paySvcs.size() // 2 paySvcs total
controller.deleteDept() // calling the action
svcTest = null
svcTest = Department.findByName("Dept1")
assertNotNull svcTest // record Dept1 still exists, it was not deleted
// can't test render, controller.response.contentAsString is null
// but testing at the UI is OK
// assertEquals "editDept", controller.response.contentAsString // action should render "editDept"
assertEquals "editDept", controller.redirectArgs.action
QUESTION:
render(view: "editDept", model: [departmentInstance: departmentInstance])
travaux lors du test manuellement à l'interface utilisateur. Mais dans le test d'intégration, controller.response est null lors de l'utilisation de render, mais renvoie le redirectArg attendu lors de l'utilisation de la redirection. Des idées pourquoi?
Avez-vous envisagé d'utiliser 'grails.test.ControllerUnitTestCase'? Il économise l'écriture d'une grande partie du code d'installation et simule le rendu et redirige pour un test facile. Check out http://stackoverflow.com/questions/2846177/unit-testing-a-controller-method/2846306 – ataylor
En fait, c'est l'inverse, j'ai essayé grails.test.ControllerUnitTestCase. Avec les tests unitaires, vous devez vous moquer davantage. mockForConstraintsTests est censé ajouter la collection d'erreurs du domaine, mais ne le fait pas. La méthode findByName() n'existait pas dans Unit testing. – Doris
Malgré le nom, vous pouvez également utiliser la classe de base 'grails.test.ControllerUnitTestCase' dans les tests d'intégration. – ataylor