On 6/26/07, Claude Schneegans <[EMAIL PROTECTED]> wrote: > > >>Sure you can open a file anywhere on your machine, and edit it in > Dreamweaver, but how will you test the file? > > But who needs to test a file directly from the editor ? > I develop from my work station on which I have CF (3 different versions) > and IIS installed. > For testing I just use MSIE and Firefox on localhost, and I'm sure the > application works > with these 2 browsers. > When you modify a file, just save it, and just refresh the browser > window on the application, period.
Utterly incorrect. So your idea of "testing" is "running the app in your browser"? This is just so wrong on so many levels that I don't know where to start. How do you test for edge cases, bad data, or any other actual bug that you discover? This is exactly what unit tests are for. And CFEclipse has a tab right there to run any unit test you open, automatically. You can also set up an ANT task to run some or all of your tests at once. Or even to automatically run your whole test suite every time you save a file. Further more, most CF files do not run independently, but from within an > application, > so no one would actually "test a file", the application must be tested. Most CF files don't run independently in a live app, but the unit tests should. The entire point of a unit test is to test the file in isolation from the rest of the system, so you are totally sure what you are testing. They are also for ensuring that new bugs can never happen again by being added to the unit test. If I find a problem, the first thing I do is add that situation to the unit test. Then I fix the problem. And then I know that no matter what happens my test will always check that condition going forward. I think you're getting unit testing confused with integration or regression testing. And for those, I still would never just open a browser and click around the app. Sorry but that's just crazy. I use Selenium to let me run a full regression test on my application at the click of a button. If you want to have a discussion about how to test properly please start another thread and I'll be happy to go back and forth with you. But back to the point of this thread (and to CFEclipse in particular) is that anyone who takes testing seriously wants to test directly in the IDE (Eclipse is an IDE not an editor). -- > _______________________________________ > REUSE CODE! Use custom tags; > See http://www.contentbox.com/claude/customtags/tagstore.cfm > (Please send any spam to this address: [EMAIL PROTECTED]) > Thanks. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJQ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:282217 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
