Feature
E-Testing: Debugging Your Projects
You're nearly finished with the code you've been slaving over for hours (or days or weeks, or maybe it was just a few seconds' effort). You're about to turn it loose for your customers to enjoy. The questions are: Is it ready? Do you know it will work? Have you tested it? If so, how? Indeed, should you be turning it over to the users as the next step?
Reader Feedback : Page 1 of 1
#1 |
Charlie Arehart commented on the 25 Oct 2001
I thought I'd mention a couple other tests that I failed to include (we were running short on available space), but are quite important. You should test your app to see how it performs when either JavaScript and/or Cookies are turned off. Many apps can grind to a halt in such cases. For instance, if you're using session variables without passing the URLTOKEN appropriately on every page and a browser doesn't support cookies, that browser user may find it impossible to access some pages on your site, appearing as a strange "bug" that's hard to detect and resolve. Testing on a browser by turning off its support for cookies (and JavaScript) can be very enlightening. I welcome comments from readers if I've missed any other important tests appropriate for CF developers. |