C#

I recently encountered one of those nasty web applications that can only be created with ColdFusion by ColdFusion developers.  Yikes!  Anyways, the only real way to be able to create web tests for this particular app turned out to be the following steps:
1) Record the test steps with fiddler
2) Re-record the exact same steps with fiddler
3) Use the differences between the two recordings to determine what data to parameterize and what data to get from extraction rules.
 

In doing performance testing it is extremely common to encounter situations where your test scripts need to choose a specific link on the page based on some condition.  For example, consider the following table:

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.

This article applies directly to FitNesse .NET’s DoFixture, but can be adapted for use in other fixtures. One of FitNesse’s greatest weaknesses is the lack of flow control within tests. In everyday real world automated testing there are plenty of times where you will want a test to stop executing so that it does not waste time or cause damage. First create some variables to use to control test flow. 
 

I recently found a really neat way to create lParam parameters for the Window’s API SendMessage and PostMessage functions. This specifically applies to messages like WM_MOUSEMOVE that require both an x and a y coordinate to be encoded into that single parameter. I had been using code like this :