{"id":705,"date":"2009-11-08T10:48:00","date_gmt":"2009-11-08T09:48:00","guid":{"rendered":"http:\/\/www.navision-blog.de\/2009\/02\/23\/getting-started-with-naturalspec\/"},"modified":"2009-11-08T10:53:06","modified_gmt":"2009-11-08T09:53:06","slug":"getting-started-with-naturalspec","status":"publish","type":"post","link":"http:\/\/www.navision-blog.de\/blog\/2009\/11\/08\/getting-started-with-naturalspec\/","title":{"rendered":""Getting started" with NaturalSpec – (Updated 08.11.2009)"},"content":{"rendered":"

In my last article (Introducing NaturalSpec \u2013 A Domain-specific language (DSL) for testing<\/a>) I used NaturalSpec in two small samples. This time I will show how we can set up a NaturalSpec<\/a> environment to write our first automatically testable scenarios.<\/p>\n

1. Choosing an IDE<\/h5>\n

The first step is to choose an integrated development environment for NaturalSpec. At the current project status you should be able to use NaturalSpec with Visual Studio 2008, Visual Studio 2010 beta 2, the freely available Visual Studio 2008 Shell<\/a> or the free IDE SharpDevelop 3.0<\/a>.<\/p>\n

2. Installing the testing framework<\/h5>\n

As NaturalSpec uses NUnit<\/a> as the underlying testing framework we have to install NUnit 2.5. I also recommend installing TestDriven.Net<\/a> in order to get a Unit Test runner within Visual Studio.<\/p>\n

3. Installing F#<\/h5>\n

NaturalSpec is completely written in F#<\/a> and all specs will also be written in F#. This doesn\u2019t imply you have to learn programming in F# but we need the F# compiler to get things working. You can download the F# October 2009 CTP<\/a> from the Microsoft F# Developer Center<\/a>.<\/p>\n

4. Downloading the latest version of NaturalSpec<\/h5>\n

You can download a .zip with the latest NaturalSpec libraries from GoogleCode<\/a>.<\/p>\n

5. Creating a spec<\/h5>\n

This part is written for using Visual Studio 2008. If you use SharpDevelop or Visual Studio 2008 Shell this might differ in some detail.<\/p>\n

Start Visual Studio 2008 and create a new F# class library.<\/p>\n

\"Creating<\/p>\n

Rename Module1.fs<\/em> in ListSpec.fs<\/em> and delete script.fsx<\/em> from the project:<\/p>\n

\"Solution<\/p>\n

Create a folder \u201cLib\u201d and unzip the NaturalSpec libraries into it.<\/p>\n

Add NaturalSpec.dll<\/em> and nunit.framework.dll<\/em> as references to your project:<\/p>\n

\"Adding<\/p>\n

Copy the following code into ListSpec.fs:<\/p>\n

module <\/span>ListSpec<\/pre>\n
open <\/span>NaturalSpec\n\n[<Scenario>]\nlet <\/span>When_removing_an_3_from_a_small_list_it_should_not_contain_3() =\n  Given [1;2;3;4;5]\n    |> When removing 3\n    |> It shouldn't contain 3\n    |> Verify<\/pre>\n
If you have TestDriven.Net installed you can run your spec via right click in the solution explorer:<\/p>\n
\"Run<\/p>\n
If you don\u2019t like the TestDriven.Net test runner you might want to use the NUnit GUI runner. The output should look like:<\/p>\n
\"NUnit<\/a><\/p>\n
In addition the test runner should produce a Spec output file with the name \u201cSpec.txt\u201d within the same folder.<\/p>\n
Summary<\/h5>\n
In a minimal environment you need SharpDevelop<\/a>, the F# compiler<\/a>, NUnit<\/a> and the NaturalSpec libraries<\/a> for using NaturalSpec. <\/p>\n
In the next post I will show how you can use NaturalSpec to create a spec for C# projects<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
In my last article (Introducing NaturalSpec \u2013 A Domain-specific language (DSL) for testing) I used NaturalSpec in two small samples. This time I will show how we can set up a NaturalSpec environment to write our first automatically testable scenarios. 1. Choosing an IDE The first step is to choose an integrated development environment for […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4,448,524],"tags":[533,664,666,219,531,633],"_links":{"self":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/705"}],"collection":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/comments?post=705"}],"version-history":[{"count":13,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/705\/revisions"}],"predecessor-version":[{"id":906,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/705\/revisions\/906"}],"wp:attachment":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/media?parent=705"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/categories?post=705"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/tags?post=705"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}