New release of FitLibrary (20091020)

View: New views
4 Messages — Rating Filter:   Alert me  

New release of FitLibrary (20091020)

by Rick Mugridge :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

There is a new release of FitLibrary available on sourceforge.

See
http://sourceforge.net/apps/mediawiki/fitlibrary/index.php?title=Main_Page

Cheers, Rick


    DoFixture

    * Added infix special actions *contains*, *eventually
      contains*, *does not contain*, *optionally*.

    * Added relationals, <, <=, >, >=, =.

    * Added a /stop watch and /sleep for

    * When longer strings don't match with *is*, etc, a diff is shown.

    * A new action uses pattern matching to extract pieces of text out
      of a string.

    * Fixed auto-wrapping so that it doesn't auto-wrap Boolean, Number,
      Character

    * Added some support for plain text for single-table actions. This
      is still experimental, somewhat incomplete, and will probably
      change. This is not supported within defined actions.


    Defined Actions

    * Sped up loading defined actions by reading them directly from the
      file system. This does mean that FitNesse features such as
      FitNesse variables and includes are not available. For backwards
      compatibility, a variation is available that uses the slow way....
      Now defined action name lookup is case sensitive, while previously
      it was not.

    * Changed the way that defined action calls are shown in the report.

    * Partially implemented a multi-defined action. This may change.
      More details later...


    SuiteFixture

    * Fixed a problem with SuiteFixture so that it now passes a copy of
      its dynamic variables to the fixture in each storytest.

    * Allow for /set stop on error/ to be set at the SuiteFixture level.


    SelectFixture

    * Can now add to the SUT set a fixture that is returned from an action.


    New fixtures

    * Added specialised Map fixtures.

    * Randomly selecting the value of a dynamic variables.


    Implementation Changes

    * Some of the built-in mechanism of FitLibrary are now pluggable.
      Eg, you can alter the way that methods are looked up or the way
      that stack dumps for exceptions are shown in the report.

    * I've also started to get ready to make more parts pluggable:

    * In a later release, I am planning to integrate a ColumnFixture
      look-alike into FitLibrary and then remove all dependency on Fit code.





Re: New release of FitLibrary (20091020)

by Markus Gaertner :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Rick,

can you please elaborate the "eventually contains" a bit? Is this similar to
the Haskell Maybe type?

Kind regards
Markus Gärtner

Rick Mugridge wrote:

> There is a new release of FitLibrary available on sourceforge.
>
> See
> http://sourceforge.net/apps/mediawiki/fitlibrary/index.php?title=Main_Page
>
> Cheers, Rick
>
>
>    DoFixture
>
>    * Added infix special actions *contains*, *eventually
>      contains*, *does not contain*, *optionally*.
>
>    * Added relationals, <, <=, >, >=, =.
>
>    * Added a /stop watch and /sleep for
>
>    * When longer strings don't match with *is*, etc, a diff is shown.
>
>    * A new action uses pattern matching to extract pieces of text out
>      of a string.
>
>    * Fixed auto-wrapping so that it doesn't auto-wrap Boolean, Number,
>      Character
>
>    * Added some support for plain text for single-table actions. This
>      is still experimental, somewhat incomplete, and will probably
>      change. This is not supported within defined actions.
>
>
>    Defined Actions
>
>    * Sped up loading defined actions by reading them directly from the
>      file system. This does mean that FitNesse features such as
>      FitNesse variables and includes are not available. For backwards
>      compatibility, a variation is available that uses the slow way....
>      Now defined action name lookup is case sensitive, while previously
>      it was not.
>
>    * Changed the way that defined action calls are shown in the report.
>
>    * Partially implemented a multi-defined action. This may change.
>      More details later...
>
>
>    SuiteFixture
>
>    * Fixed a problem with SuiteFixture so that it now passes a copy of
>      its dynamic variables to the fixture in each storytest.
>
>    * Allow for /set stop on error/ to be set at the SuiteFixture level.
>
>
>    SelectFixture
>
>    * Can now add to the SUT set a fixture that is returned from an action.
>
>
>    New fixtures
>
>    * Added specialised Map fixtures.
>
>    * Randomly selecting the value of a dynamic variables.
>
>
>    Implementation Changes
>
>    * Some of the built-in mechanism of FitLibrary are now pluggable.
>      Eg, you can alter the way that methods are looked up or the way
>      that stack dumps for exceptions are shown in the report.
>
>    * I've also started to get ready to make more parts pluggable:
>
>    * In a later release, I am planning to integrate a ColumnFixture
>      look-alike into FitLibrary and then remove all dependency on Fit code.
>
>
>
>
>


Re: New release of FitLibrary (20091020)

by Rick Mugridge :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Note that it's essential to have the !path for fitlibrary.jar before
fitnesse.jar in your pages, because there is an old version of
FitLibrary contained within fitnesse.jar and it's inconsistent with the
latest FitNesse and the latest FitLibrary.

The same applies when developing code in an IDE: have the JAR files in
that order to get access to the correct code.

I've requested that FitLibrary code be removed from FitNesse in future
to avoid such problems.

Cheers, Rick

Re: New release of FitLibrary (20091020)

by Rick Mugridge :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Markus,

There are DoFixture special actions *is*, *contains *and *matches* for
testing the result of an action.

There are corresponding ones that poll the action repeatedly until they
succeed or until a timeout period expires. They are:

*becomes*, *eventually contains* and *eventually matches*.

One use of these is with SpiderFixture, when there may be some delay
before some text changes in the browser, for example, with ajax.

Cheers, Rick

> Hi Rick,
>
> can you please elaborate the "eventually contains" a bit? Is this
> similar to
> the Haskell Maybe type?
>
> Kind regards
> Markus Gärtner