tag:blogger.com,1999:blog-1973750947775262558.post5125054625731766576..comments2009-04-21T17:30:45.515-04:00bill sheltonhttp://www.blogger.com/profile/06624894387927690246noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-1973750947775262558.post-47199539450733226422009-04-21T17:30:00.000-04:002009-04-21T17:30:00.000-04:00Yeah it begs that question. <br /><br />My problem comes down to the fact that these objects (called Aspects in my framework) are not in a hierarchy. There are a bunch of objects in application scope that may use each other. Because they are all instantiated at the application start, wherever you are in the app you know you can use any one of them. <br /><br />Let's say you have a Contacts data access object and a Exporter object that writes files with all your contacts. In Exporter.cfc you can have a method writeContactFile() which calls APPLICATION.Contacts.getAll() ...<br /><br />How do you unit test writeContactFile() in Exporter.cfc ?<br /><br />In your unit test CFC you probably have to execute whatever it is that your code does on application start prior to any tests? I think this is where it got messy and I hit a wall.Ben Margolishttp://twitter.com/tangonnoreply@blogger.comtag:blogger.com,1999:blog-1973750947775262558.post-3573404710698047982009-04-21T17:06:00.000-04:002009-04-21T17:06:00.000-04:00Sure! I'm sure Marc will chime in ... maybe send the details to theguys at mxunit.org ?<br /><br />For me, this also begs the question of "How can you test an Application.cfc?"billyhttp://www.blogger.com/profile/06624894387927690246noreply@blogger.comtag:blogger.com,1999:blog-1973750947775262558.post-25831354731547222632009-04-21T16:46:00.000-04:002009-04-21T16:46:00.000-04:00Are you still in need of hard-to-test code? I have code that puts a lot of objects in application scope upon app startup. (They are singletons.)Ben Margolisnoreply@blogger.com