Robert Douglass wrote:
I make sure to write tests that break the code too. So the first test I run is said action without any input parameters, for example. Then with bad parameters. The bad tests have to all fail before I test the correct case. And, by the way, make sure you have worked out whether you're going change state in your database (or whatever persistence mechanism you use). Always write your tests so that you can run them on a live application, if you can, without risking data loss etc.
-RD
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Francisco Hernandez Sent: Monday, October 06, 2003 6:16 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] testing web applications
hey guys, im new to unit testing and am wondering what kind of tests you guys do you your apps
for example I have an action that creates a user, do you guys simply populate the parameters and execute the action and then check to see if the user exists with the correct data in the datastore?
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
