watinfixture-development — Development information for WatiNFixture - code changes, fixes, future updates.

[Watinfixture-development] WatiNFixture 0.3 Released

[Jeff P. <ka...@iw...>]

Good evening, everyone.

 

WatiNFixture 0.3 has been released for download.  In this release:

*	New searches for each command.  In addition to ID, searches can be
performed by index, text, and attribute name-value pair.  Searches by index
can be tricky, and notes have been added to the documentation to help guide
the user.
*	CheckTableContents has been updated to handle variable numbers of
rows and columns, and missing and extra rows now display correctly.  In
addition, control checks for button, checkbox, hyperlink, image button, and
radio button controls have been added.  Also, control mismatches will be
displayed.
*	Methods declared obsolete in WatiNFixture 0.2 have been removed
*	Input parameters in CheckPageContents are being consolidated.  id
can be used to in place of control-specific ID parameters.  In addition,
pageText is being replaced with text.  This is to help standardize the input
parameters used for searching.  The control-specific parameters will be
removed in Release 0.4.
*	Searches by ID, text, and the value of the attribute name-value pair
have been set up to use regular expressions.  Because ASP.NET tends to
create long, complex control names based on the embedding levels of controls
within controls and master pages, regular expressions can be used to search
for abbreviated versions of control names and attribute values, rather than
having to use the full ID.
*	New commands for checking the titles and styles of controls have
been added.  These checks can be used to validate the operation of ASP.NET
validator controls.  These controls are always present on the page, but
their visibility styles are set to hidden until a validation check fails.
When a validation check fails, the visibility style is changed from hidden
to visible by the javascript.
*	Text checks have been modified to remove trailing spaces when
performing comparisons.  When binding data to a DataGrid, GridView,
DropDownList or other ASP.NET control, the data bindings can sometimes leave
trailing spaces that are not necessarily considered a valid part of the
data.  However, leading spaces may be a valid part of the data and have been
left alone.

 

The following are known bugs in WatiNFixture 0.3 and are scheduled to be
fixed:

*	CheckTableContents

*	Header cells in tables - <TH> tags - are not being handled correctly
and show up as errors.
*	Span and Label controls are currently detected as Unknown controls.
These need to be added to the control checks.
*	Pagination controls are not being handled correctly and show up as
errors.

*	Empty parameters are causing methods to abort.  Tests need to be
added to check the parameters for empty values, and the code needs to be
fixed to handle empty parameters correctly.

 

The following release files are available.
*         WatiN.Contrib.WatiNFixture_0.3_20060719_1.1.zip - Binary release
of WatiNFixture, compiled using WatiN 1.0 and the FitServer.NET release for
.NET Framework 1.1 that comes with the 7/19/2006 download of FitNesse
*         WatiN.Contrib.WatiNFixture_0.3_20070128_1.1.zip - Binary release
of WatiNFixture, compiled using WatiN 1.0 and the FitServer.NET release from
1/28/2007 for .NET Framework 1.1
*         WatiN.Contrib.WatiNFixture_0.3_20070128_2.0.zip - Binary release
of WatiNFixture, compiled using WatiN 1.0 and the FitServer.NET release from
1/28/2007 for .NET Framework 2.0
*         WatiN.Contrib.WatiNFixture.src_0.3.zip - Source code release for
WatiNFixture 0.3

Also included in the binary release zip files are WatiN 1.0 and the single
threaded apartment (STA) recompiles of FitServer.NET that are required for
WatiN and WatiNFixture to work correctly with FitNesse.  These files have
been included to help make the installation of WatiNFixture easier for the
user.

 

Enjoy!

 

Jeff

Re: [Watinfixture-development] Test

[Jeff P. <ka...@iw...>]

Test 2

 

  _____  

From: Jeff Parker [mailto:ka...@iw...] 
Sent: Thursday, January 18, 2007 6:41 PM
To: 'wat...@li...'
Subject: Test

 

Test

[Watinfixture-development] Test

[Jeff P. <ka...@iw...>]

Test

[Watinfixture-development] WatiNFixture 0.2 Released

[Jeff P. <ka...@iw...>]

WatiNFixture 0.2 has been released.  The complete release notes can be found
at http://sourceforge.net/project/shownotes.php?group_id=181273
<http://sourceforge.net/project/shownotes.php?group_id=181273&release_id=475
975> &release_id=475975

 

The following are highlights for this release:

*	Renamed FindXXX methods to XXXExists - example, FindLabel to
LabelExists
*	Renamed public variables to more accurate and standardized names -
example, searchForTextbox to textboxID
*	Rename CheckXXX methods to VerifyXXX - example,
CheckCheckboxIsChecked to VerifyCheckboxIsChecked
*	Added tests for the new methods so the old versions can be removed
in Release 0.3.  The old methods still exist in Release 0.2, to help ease
the transition between versions.
*	Included WatiN 0.9.5 DLL and the Internet Explore interop DLL in the
release files, to help with installation without having to download the
source code.
*	Encapsulated public variables into properties (refactoring)
*	Moved logic for each control type into its own handler, so that
common logic used across fixtures occurs in only one location (refactoring)

 

In addition, new functionality has been added:

*	UserActions

*	Compared and rounded out the methods available for each control
*	Added logic to click an image button that has a specified image
source
*	Added logic for workflow testing of a page

*	Pressing of the tab key, one or more times
*	Setting the focus to a control based on its ID
*	Entering text at the point of the current cursor location
*	Selecting items from a select list at the point of the current
cursor location
*	Clicking of the control at the current cursor location
*	Sleeping for a given number of milliseconds, to simulate a user
pause or wait for a long page load to complete

*	CheckPageContents

*	Check for the existence of image buttons according to the image
source graphic

 

Also, new fixtures have been added to this release:

*	CheckPageHyperlinksRead - validates the list of hyperlinks that
should be displayed on the page
*	CheckTableContents - validates tables of data on a web page,
including textbox and dropdown list controls

 

Certain methods also support regular expressions.  

*	UserActions

*	VerifyLinkWithTextHasAddress - text of the hyperlink
*	ClickLinkWithText - text of the hyperlink
*	ClickImageButtonWithImage - image source of the image

*	CheckPageContents

*	VerifyLinkWithTextHasAddress - imageSource property

Future releases will likely include adjustments to use regular expressions,
so that complete IDs, exact labels and exact paths do not have to be entered
to find the correct control on the page.

 

Currently, WatiN has problems with the PressTab method.  The best way I have
found to resolve this issue is to set the focus to a specific control on the
web page prior to any press tab commands.  This seems to stabilize the
behavior.  Also, pressing tabs will not work if the tests are run from a
Continuous Integration environment, such as CruiseControl.NET.

 

This will hopefully be fixed in future releases of WatiN.  I have included
the press tab functionality in this release, because even with the current
problems I have found this to still be useful for testing web applications.

 

Enjoy!

 

Jeff

[Watinfixture-development] Email test

[Jeff P. <ka...@iw...>]