Hello All, I'm slowly attaining a good level of code-coverage for my unit tests on this project, however, one _very_ weak point is unit and integration tests on controllers.
>From my experience on ColdBox projects, this is something which they make relatively simple. They allow MXUnit to create it's own instance of the application, and then execute a full request stack, so you can test the behaviour of your handlers, ensuring users are forwarded to the correct events, the right objects are placed into the event etc etc. http://wiki.coldbox.org/wiki/Testing.cfm They also allow specific targeted controller unit tests which again allow you to mock the behaviour of the rest of the framework just to test the controller methods in isolation. Has anyone put much thought into something like this for ModelGlue? I've been experimenting myself with unit tests of the controller but there is such a large amount of behaviour (the event object, the base controller methods etc) that have to be Mocked it quickly becomes a little fussy. I'd appreciate anyone else's experience. Robert -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/model-glue?hl=en
