{"id":738,"date":"2009-02-28T16:46:04","date_gmt":"2009-02-28T15:46:04","guid":{"rendered":"http:\/\/www.navision-blog.de\/2009\/02\/28\/parameterized-scenarios-with-naturalspec\/"},"modified":"2023-01-03T13:40:03","modified_gmt":"2023-01-03T13:40:03","slug":"parameterized-scenarios-with-naturalspec","status":"publish","type":"post","link":"http:\/\/www.navision-blog.de\/blog\/2009\/02\/28\/parameterized-scenarios-with-naturalspec\/","title":{"rendered":"Parameterized Scenarios with NaturalSpec"},"content":{"rendered":"

I wrote a lot about NaturalSpec<\/a> in my last articles<\/a>. This time I will show how we can use parameterized scenarios.<\/p>\n

1. Using predefined scenarios<\/h5>\n

By writing predefined parameterized scenarios we can easily create a scenario suite with lots of different test cases:<\/p>\n

\/\/ predefined scenario\n<\/span>let <\/span>factorialScenario x result =\n  Given x\n    |> When calculating factorial\n    |> It should equal result\n\n[<Scenario>]\nlet <\/span>When_calculation_factorial_of_1() =\n  factorialScenario 1 1\n    |> Verify   \n\n[<Scenario>]\nlet <\/span>When_calculation_factorial_of_10() =\n  factorialScenario 10 3628800\n    |> Verify<\/pre>\n
If we run these scenarios with NUnit<\/a> we will get the following output:<\/p>\n
\n
Scenario: When calculation factorial of 1<\/p>\n
  – Given 1 <\/p>\n
    – When calculating factorial <\/p>\n
       => It should equal 1<\/p>\n
==> OK<\/p>\n
==> Time: 0.0093s<\/p>\n
Scenario: When calculation factorial of 10<\/p>\n
  – Given 10 <\/p>\n
    – When calculating factorial <\/p>\n
       => It should equal 3628800<\/p>\n
==> OK<\/p>\n
==> Time: 0.0018s<\/p>\n<\/blockquote>\n
2. Using the ScenarioTemplate attribute<\/h5>\n
The second and shorter option is to use the ScenarioTemplate<\/em> attribute, which is inherited from NUnit\u2019s new TestCase<\/em> attribute<\/a>:<\/p>\n
\/\/ with ScenarioTemplate Attribute\n<\/span>[<ScenarioTemplate(1, 1)>]\n[<ScenarioTemplate(2, 2)>]\n[<ScenarioTemplate(5, 120)>]\n[<ScenarioTemplate(10, 3628800)>]\nlet <\/span>When_calculating_fac_(x,result) =\n  Given x\n    |> When calculating factorial\n    |> It should equal result\n    |> Verify<\/pre>\n
This code will create 4 different scenarios, which NUnit will display and report separately:<\/p>\n
\"NUnit<\/p>\n
3. Using ScenarioSource<\/h5>\n
The third option is to use the ScenarioSource<\/em> attribute. Here we define a function which generates TestData:<\/p>\n
\/\/\/ with a scenario source      \n<\/span>let <\/span>MyTestCases =\n  TestWith 12 3 4\n    |> And 12 4 3\n    |> And 12 6 2\n    |> And 1200 40 30\n    |> And 0 0 0 |> ShouldFailWith (typeof<System.DivideByZeroException>)<\/pre>\n
And then we have to tell NaturalSpec which TestData a scenario should use:<\/p>\n
[<Scenario>]\n[<ScenarioSource "MyTestCases"<\/span>>]\nlet <\/span>When_dividing a b result =\n Given a \n   |> When dividing_by b\n   |> It should equal result\n   |> Verify<\/pre>\n
 \"NaturalSpec  <\/pre>\n
Summary<\/h5>\n
Sometime it makes sense to test a scenario with a bunch of different parameters. We can use the ScenarioTemplate<\/em> attribute to easily parameterize our scenarios. If we want more flexibility we can use predefined scenarios with custom parameters or the ScenarioSource attribute.<\/p>\n
https:\/\/247apotheek.com<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"
I wrote a lot about NaturalSpec in my last articles. This time I will show how we can use parameterized scenarios. 1. Using predefined scenarios By writing predefined parameterized scenarios we can easily create a scenario suite with lots of different test cases: \/\/ predefined scenario let factorialScenario x result = Given x |> When […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[448,524],"tags":[664,666,219,538,531],"_links":{"self":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/738"}],"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=738"}],"version-history":[{"count":6,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/738\/revisions"}],"predecessor-version":[{"id":2052,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/738\/revisions\/2052"}],"wp:attachment":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/media?parent=738"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/categories?post=738"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/tags?post=738"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}