TickSpec: An F# BDD Framework

Source code checked in, #08b686485784

ptrelford — Tue, 30 Apr 2013 09:13:22 GMT

valet parking and implied price examples

Updated Wiki: Documentation

ptrelford — Mon, 29 Apr 2013 08:37:33 GMT

Behaviour Driven Development (BDD) is an Agile software development approach that focuses on clear communication. It encourages collaboration between developers, QA and business people. Via collaboration key behaviours of a system are specified by example. These examples provide living documentation to drive product development.

TickSpec is a lightweight BDD library and framework for .Net, with first class support for C# and F#. Use TickSpec to automate your examples.

Articles:

Videos:

Slides:

Nuget packages:

See also:

Cellz an open source Spreadsheet with examples automated with TickSpec

Source code checked in, #4bd76fd10a47

ptrelford — Fri, 26 Apr 2013 20:17:16 GMT

doc string support (triple quoted string blocks)

Source code checked in, #0c24cbe5782a

ptrelford — Fri, 26 Apr 2013 18:55:23 GMT

code gen converter from table to object array

Source code checked in, #203b232b04b1

ptrelford — Fri, 26 Apr 2013 17:34:05 GMT

code gen for arrays of objects as table arguments to step methods

Source code checked in, #21537348f904

ptrelford — Fri, 26 Apr 2013 15:18:22 GMT

split scrabble logic to separate module

Source code checked in, #9ae865888e9a

ptrelford — Fri, 26 Apr 2013 15:11:09 GMT

another scrabble scenario example

Source code checked in, #6b3718dfd53b

ptrelford — Fri, 26 Apr 2013 14:47:46 GMT

extended scrabble example

Source code checked in, #04f449652476

ptrelford — Sat, 20 Apr 2013 09:50:29 GMT

Updated reference XUnit project to skip to step definition exception

New Post: xUnit Assert in Step Definitions vs. TargetInvocationException

BenTaylor — Thu, 18 Apr 2013 16:48:57 GMT

Thank you Phil. Worked like a boss with ReSharper too. Easy and simple to boot!

Loving the TickSpec.

New Post: xUnit Assert in Step Definitions vs. TargetInvocationException

ptrelford — Thu, 18 Apr 2013 08:48:38 GMT

I have a simple workaround for this which works with TestDriven.Net and so may well work on ReSharper (please let me know).

In the reference implementation of TickCommand when an exception is caught in a step method it creates a FailedResult with the root exception and stack:

FailedResult(info, ex, scenario.ToString()) :> MethodResult

Changing it to report the inner exception should give the stack trace starting at the step method:

let ex = if ex.InnerException <> null then ex.InnerException else ex
FailedResult(info, ex, scenario.ToString()) :> MethodResult

Thanks for the feedback :)

Phil

New Post: xUnit Assert in Step Definitions vs. TargetInvocationException

BenTaylor — Wed, 17 Apr 2013 23:31:12 GMT

Hi TickSpecers,

I'm calling xUnit Assert methods in my step definitions. For example Assert.Equals(1, valueThatShouldBeOne). This all works well. However, when they fail, the Exception details I see in the ReSharper unit test runner Output window is the TargetInvocationException from the reflection Invoke, rather than the Assert details.

Is there a way I can configure TickSpec to show me the underlying Assert exception and stack trace details (so I can know what is failing)?

I've built a modified version locally that gives some basics on the InnerException, but I thought I would ask what your thoughts/advice is on this before working on a full change.

Thanks for building TickSpec. I like using it!

Ben

Source code checked in, #d7675576ed28

ptrelford — Mon, 08 Apr 2013 08:07:21 GMT

Added Readme.txt

Source code checked in, #e71ead3bdea6

ptrelford — Sun, 07 Apr 2013 17:15:45 GMT

Added Examples\Scenarios project with many implemented examples

Source code checked in, #23390718c9fe

ptrelford — Sat, 06 Apr 2013 21:41:54 GMT

Added C# NUnit example

Updated Wiki: Documentation

ptrelford — Sat, 06 Apr 2013 21:30:25 GMT

Videos:

Slides:

Nuget packages:

See also:

Cellz an open source Spreadsheet with examples automated with TickSpec

Updated Wiki: Documentation

ptrelford — Sat, 06 Apr 2013 19:16:13 GMT

Behaviour Driven Development (BDD) is an Agile software development approach that focuses on clear communication. It encourages collaboration between developers, QA and business people. Via collaboration key behaviours of a system are specified by example. These examples provide concise documentation to drive product development.

TickSpec is a lightweight BDD library and framework for .Net, with first class support for C# and F#. Use TickSpec to automate your examples.

Articles:

Videos:

Nuget packages:

See also:

Cellz an open source Spreadsheet with examples automated with TickSpec

Updated Wiki: Documentation

ptrelford — Sat, 06 Apr 2013 19:04:25 GMT

Behaviour Driven Development (BDD) is an Agile software development approach that focuses on clear communication. It encourages collaboration between developers, QA and business people. Via collaboration key behaviours of a system are specified by example. These examples provide concise documentation to drive product development.

TickSpec is a lightweight BDD library and framework for .Net, with first class support for C# and F#. Use TickSpec to automate your examples.

Articles:

Videos:

See also:

Cellz an open source Spreadsheet with examples automated with TickSpec

Source code checked in, #8c284face6c1

ptrelford — Fri, 29 Mar 2013 15:50:13 GMT

Updated solutions to VS2012

Commented Issue: AfterScenario not activated when test fails [1]

psfblair — Sat, 15 Dec 2012 20:30:02 GMT

I have an integration test that starts listening on a network socket at the beginning of a scenario and stops at the end of the scenario, using [<BeforeScenario>] and [<AfterScenario>] attributes on functions in my step definitions file. If the test passes, the before and after scenarios work fine. However, with my test that fails (i.e, throws an AssertionException from an Assert.That assertion inside FsUnit's should function), the AfterScenario function never gets hit. The following sample step definitions should reproduce the failure (at least they do for me): let [<BeforeScenario>] SetUp () = printfn "Starting..." let [<AfterScenario>] TearDown () = printfn "Stopping" let [<Then>] ``Something to assert`` () = Assert.Fail()
Comments: Thanks, Phil!