QA

The following class can be used to override the standard IE object in WatiN to run specific tests after every page load.  For example, in Drupal this class can be used to make sure that no error messages appear on any page during the test run.
 

In my previous post, I discussed the basics of using Gallio, MbUnit, and WatiN to test web applications.  In the previous example you could continue to add tests to the class by creating additional test methods and marking them with the test attribute.  However, you could not guarantee what kind of order those tests would run in.  Fortunately, MbUnit/Gallio is a flexible enough framework to allow you to create orderd test suites which is a common need for functional testing.
 

This post is about three remarkable open source testing tools.  WatiN, a .NET based web application testing framework can be used to drive the Internet Explorer, Firefox, and even Chrome web browsers.

 I recently needed to create a test case for selenium that required a user to have just logged in to a Drupal website.  Often when running selenium tests, the browser may already have an authenticated session, so the test will need to detect this and then logout.  Of course with Drupal you can always just go to the url ?q=logout to make sure you are logged out, but this way is more fun and makes a good example for using logic in Selenium tests!

No, this entry has nothing to do with strange food.  I am doing some experimenting today with the Dogtail GUI test tool in order to evaluate its capablities for testing apps on Linux.  First off, documentation on dogtail is very hard to come by.  The API docs on the dogtail site are very old so avoid using them if you can.  I recommend the following series of articles instead: