guitester Release Rss Feed

Updated Release: GUITester V2 (Aug 28, 2006)

rfennell — Sat, 20 Sep 2008 13:36:20 GMT

The .NET 2.0 release

In V2.2 I have rebuilt the GUITesting framework using VS.Net 2005 ans 2008. No changes really, the built in converter from VS.Net 2003 to 2005 did the job with no errors. At this time I have not done any work to exploit the new features of .NET 2.0. Equally I have not retarget for the 3.5 framework as it provide no quick benefits.

However, what I have had a look at is integrating the new testing features of VS.Net 2005/8 Team Developer edition. So in this V2.x source release you will find a test project, sorry if you not have Team developer edition of VS.Net, just remove the test project when it fails to load!

So how did the integration with a Microsoft Test Project go? In the past I had my own test run EXE to do the testing, it looks for custom attributes that define the tests then runs them, this still work. However, as I wanted to use VS.NET to run the tests, I needed to run my declared tests via a TestMethod in a test project. I have written a wrapper to do this which can be seen on the test project. Using this wrapper code in the TestMethod the tests run fine, the problem is that all my defined tests appear as a single VS.Net test. Fine if they all pass, but not that helpful debugging. The only other option is to create a TestMethod for each test a have in my application under test, not really an options as these tests are user defined and discovered via reflection.

The ClickTextTest attribute now has an optional extra boolean flag, this allows you to say if the text to match is a fixed string or a regular expression. The usage to check a textbox contains an email address:

[ClickTextTest("email test","textBoxRegularExpression",@"^\w+([-+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*$",true)]
private Button btnRegularExpression;
private TextBox textBoxRegularExpression;

There is also a simple text field test that allow you to validate that a field matches a regular expression, this is used in the form:

[RegularExpressionTest("email test",@"^\w+([-+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*$")]
private TextBox textBoxRegularExpression;

Released: GUITester V2 (Aug 28, 2006)

Sat, 20 Sep 2008 13:36:20 GMT

[ClickTextTest("email test","textBoxRegularExpression",@"^\w+([-+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*$",true)]
private Button btnRegularExpression;
private TextBox textBoxRegularExpression;

There is also a simple text field test that allow you to validate that a field matches a regular expression, this is used in the form:

[RegularExpressionTest("email test",@"^\w+([-+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*$")]
private TextBox textBoxRegularExpression;

Updated Release: GUITester V2 (Aug 28, 2006)

rfennell — Sat, 20 Sep 2008 13:33:51 GMT

The .NET 2.0 release

In V2.2 I have rebuilt the GUITesting framework using VS.Net 2005. No changes really, the built in converter from VS.Net 2003 to 2005 did the job with no errors. At this time I have not done any work to exploit the new features of .NET 2.0.

However, what I have had a look at is integrating the new testing features of VS.Net 2005 Team Developer edition. So in this V2.0 source release you will find a test project, sorry if you not have Team developer edition of VS.Net, just remove the test project when it fails to load!

So how did the integration with a Microsoft Test Project go? In the past I had my own test run EXE to do the testing, it looks for custom attributes that define the tests then runs them, this still work. However, as I wanted to use VS.NET to run the tests, I needed to run my declared tests via a TestMethod in a test project. I have written a wrapper to do this which can be seen on the test project. Using this wrapper code in the TestMethod the tests run fine, the problem is that all my defined tests appear as a single VS.Net test. Fine if they all pass, but not that helpful debugging. The only other option is to create a TestMethod for each test a have in my application under test, not really an options as these tests are user defined and discovered via reflection.

The ClickTextTest attribute now has an optional extra boolean flag, this allows you to say if the text to match is a fixed string or a regular expression. The usage to check a textbox contains an email address:

[ClickTextTest("email test","textBoxRegularExpression",@"^\w+([-+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*$",true)]
private Button btnRegularExpression;
private TextBox textBoxRegularExpression;

There is also a simple text field test that allow you to validate that a field matches a regular expression, this is used in the form:

[RegularExpressionTest("email test",@"^\w+([-+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*$")]
private TextBox textBoxRegularExpression;

UPDATED RELEASE: GUITester V2 (Aug 28, 2006)

Mon, 24 Sep 2007 13:35:15 GMT

The .NET 2.0 release

In V2.2 I have rebuilt the GUITesting framework using VS.Net 2005. No changes really, the built in converter from VS.Net 2003 to 2005 did the job with no errors. At this time I have not done any work to exploit the new features of .NET 2.0.

However, what I have had a look at is integrating the new testing features of VS.Net 2005 Team Developer edition. So in this V2.0 source release you will find a test project, sorry if you not have Team developer edition of VS.Net, just remove the test project when it fails to load!

So how did the integration with a Microsoft Test Project go? In the past I had my own test run EXE to do the testing, it looks for custom attributes that define the tests then runs them, this still work. However, as I wanted to use VS.NET to run the tests, I needed to run my declared tests via a [TestMethod] in a test project. I have written a wrapper to do this which can be seen on the test project. Using this wrapper code in the [TestMethod] the tests run fine, the problem is that all my defined tests appear as a single VS.Net test. Fine if they all pass, but not that helpful debugging. The only other option is to create a [TestMethod] for each test a have in my application under test, not really an options as these tests are user defined and discovered via reflection.

The ClickTextTest attribute now has an optional extra boolean flag, this allows you to say if the text to match is a fixed string or a regular expression. The usage to check a textbox contains an email address:
{{
[ClickTextTest("email test","textBoxRegularExpression",@"^\w+([-+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*$",true)]
private Button btnRegularExpression;
private TextBox textBoxRegularExpression;
}}

There is also a simple text field test that allow you to validate that a field matches a regular expression, this is used in the form:

{{
[RegularExpressionTest("email test",@"^\w+([-+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*$")]
private TextBox textBoxRegularExpression;
}}

UPDATED RELEASE: GUITester V2 (Aug 28, 2006)

Mon, 24 Sep 2007 13:21:47 GMT

The .NET 2.0 release

In V2.2 I have rebuilt the GUITesting framework using VS.Net 2005. No changes really, the built in converter from VS.Net 2003 to 2005 did the job with no errors. At this time I have not done any work to exploit the new features of .NET 2.0.

However, what I have had a look at is integrating the new testing features of VS.Net 2005 Team Developer edition. So in this V2.0 source release you will find a test project, sorry if you not have Team developer edition of VS.Net, just remove the test project when it fails to load!

So how did the integration with a Microsoft Test Project go? In the past I had my own test run EXE to do the testing, it looks for custom attributes that define the tests then runs them, this still work. However, as I wanted to use VS.NET to run the tests, I needed to run my declared tests via a [TestMethod] in a test project. I have written a wrapper to do this which can be seen on the test project. Using this wrapper code in the [TestMethod] the tests run fine, the problem is that all my defined tests appear as a single VS.Net test. Fine if they all pass, but not that helpful debugging. The only other option is to create a [TestMethod] for each test a have in my application under test, not really an options as these tests are user defined and discovered via reflection.

The ClickTextTest attribute now has an optional extra boolean flag, this allows you to say if the text to match is a fixed string or a regular expression. The usage to check a textbox contains an email address:

[ClickTextTest("email test","textBoxRegularExpression",@"^\w+([-+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*$",true)]
private Button btnRegularExpression;
private TextBox textBoxRegularExpression;

There is also a simple text field test that allow you to validate that a field matches a regular expression, this is used in the form:

[RegularExpressionTest("email test",@"^\w+([-+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*$")]
private TextBox textBoxRegularExpression;

UPDATED RELEASE: GUITester V1 (Aug 10, 2006)

Mon, 24 Sep 2007 13:19:53 GMT

These are .NET 1.0 VS2003 projects

V1.0. is the initial version of the project
V1.1 adds a VN.NET demo

To this end I have added a very small VB.NET demo to the show the basic functions. There is a single form with a basic button click event. You then need to add the following attributes

First the flag that says that the class is testable:

_
Public Class Form1

Then the actual test attributes:

_
Friend WithEvents Button1 As System.Windows.Forms.Button

Now be careful with these test attributes, the _ line continuation character is required and they have to be placed in the region marked 'Windows Form Designer generated code'. Mnaually adding them here does work, but I am worried that the Visual Studio Desginer may remove these lines if the GUI is altered, I need to investigate this further, but my initial test seem to show this is not the case.

UPDATED RELEASE: Java (Aug 10, 2007)

Mon, 24 Sep 2007 13:17:24 GMT

The techniques used in my .NET GUITester project, though developed using C#, are applicable to any of the 30+ .NET Framework supported languages.

.NET does provide support for Microsoft's own 'Java like' language J#, but this is not actual Java. So I have done a small trial to see if similar techniques i.e. reflection and annotation (as Java terms attributes) could be applied in a 'pure' Sun Microsoft Systems Java 1.5 reference implementation. The aim of this trial was to try to replicate the first tests I did in .NET:

Discover GUI components in a Swing based application
Add custom annotation to GUI components
Cause a button event to be fired and see its result.
The key changes required in the port from C# were:

Private Members - By default Java reflection does not allow access to private members. This is a major issue for this testing model. It is a key requirement of this project that the developer should not be required to change from 'good software engineering practice' e.g. by making private members public. A solution to this problem was found on OnJava.Com . This allows a backdoor route into the class under test using the getDeclaredField() method.
Event Triggering - In Java, GUI events are callable methods of the GUI control, so triggering events is actually a simpler task that under .NET when the event model has to be invoked.

This trial is a Java Netbeans 4 project

CREATED RELEASE: GUITester V2 (Aug 28, 2006)

Mon, 24 Sep 2007 12:57:45 GMT

The .NET 2.0 release

UPDATED RELEASE: Java (Aug 10, 2007)

Mon, 24 Sep 2007 12:52:26 GMT

A Java proof of concept

UPDATED RELEASE: GUITester V1 (Aug 10, 2006)

Mon, 24 Sep 2007 12:51:45 GMT

The .Net 1.1. version of the project

CREATED RELEASE: Java

Mon, 24 Sep 2007 12:50:06 GMT

A Java proof of concept

UPDATED RELEASE: GUITester V1

Mon, 24 Sep 2007 12:49:08 GMT

The .Net 1.1. version of the project