<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>storyq Work Item Rss Feed</title><link>http://www.codeplex.com/storyq/WorkItem/List.aspx</link><description>storyq Work Item Rss Description</description><item><title>Commented Issue: Cannot translate to Russian [16121]</title><link>http://storyq.codeplex.com/workitem/16121</link><description>Hello&amp;#33;&lt;br /&gt;&lt;br /&gt;I have created a Russian grammar file &amp;#40;attached&amp;#41;. However the generate.ps1 script shows the following error when processing this file&amp;#58;&lt;br /&gt;&lt;br /&gt;ru-RU.txt&lt;br /&gt;- Generating obj&amp;#92;StoryQ.flit.ru-RU code from ru-RU&lt;br /&gt;error &amp;#58; Running transformation&amp;#58; System.NullReferenceException&amp;#58; Object reference not set to an instance of an object.&lt;br /&gt;   in Microsoft.VisualStudio.TextTemplating673cb8208b3b4c71b29c04fb73c92521.GeneratedTextTransformation.TransformText&amp;#40;&amp;#41; in&lt;br /&gt; c&amp;#58;&amp;#92;Users&amp;#92;Никита&amp;#92;AppData&amp;#92;Local&amp;#92;Temp&amp;#92;obj&amp;#92;StoryQ.flit.tt&amp;#58;line 219&lt;br /&gt;   in Microsoft.VisualStudio.TextTemplating.TransformationRunner.RunTransformation&amp;#40;TemplateProcessingSession session, Str&lt;br /&gt;ing source, ITextTemplatingEngineHost host, String&amp;#38; result&amp;#41;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;It seems that the TextTransform.exe does not like Cyrillics. I also doubt that translation to other languages that are not based on English alphabet is possible.&lt;br /&gt;&lt;br /&gt;I&amp;#39;ve managed to create the StoryQ.flit.ru-RU.g.cs that works for me manually &amp;#40;using the StoryQ.flit.en-US.g.cs file as a source&amp;#41;.&lt;br /&gt;Comments: Here is the manually created StoryQ.flit.ru-RU.g.cs.</description><author>ni28</author><pubDate>Mon, 25 Feb 2013 08:49:01 GMT</pubDate><guid isPermaLink="false">Commented Issue: Cannot translate to Russian [16121] 20130225084901A</guid></item><item><title>Created Issue: Cannot translate to Russian [16121]</title><link>http://storyq.codeplex.com/workitem/16121</link><description>Hello&amp;#33;&lt;br /&gt;&lt;br /&gt;I have created a Russian grammar file &amp;#40;attached&amp;#41;. However the generate.ps1 script shows the following error when processing this file&amp;#58;&lt;br /&gt;&lt;br /&gt;ru-RU.txt&lt;br /&gt;- Generating obj&amp;#92;StoryQ.flit.ru-RU code from ru-RU&lt;br /&gt;error &amp;#58; Running transformation&amp;#58; System.NullReferenceException&amp;#58; Object reference not set to an instance of an object.&lt;br /&gt;   in Microsoft.VisualStudio.TextTemplating673cb8208b3b4c71b29c04fb73c92521.GeneratedTextTransformation.TransformText&amp;#40;&amp;#41; in&lt;br /&gt; c&amp;#58;&amp;#92;Users&amp;#92;Никита&amp;#92;AppData&amp;#92;Local&amp;#92;Temp&amp;#92;obj&amp;#92;StoryQ.flit.tt&amp;#58;line 219&lt;br /&gt;   in Microsoft.VisualStudio.TextTemplating.TransformationRunner.RunTransformation&amp;#40;TemplateProcessingSession session, Str&lt;br /&gt;ing source, ITextTemplatingEngineHost host, String&amp;#38; result&amp;#41;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;It seems that the TextTransform.exe does not like Cyrillics. I also doubt that translation to other languages that are not based on English alphabet is possible.&lt;br /&gt;&lt;br /&gt;I&amp;#39;ve managed to create the StoryQ.flit.ru-RU.g.cs that works for me manually &amp;#40;using the StoryQ.flit.en-US.g.cs file as a source&amp;#41;.&lt;br /&gt;</description><author>ni28</author><pubDate>Mon, 25 Feb 2013 08:48:17 GMT</pubDate><guid isPermaLink="false">Created Issue: Cannot translate to Russian [16121] 20130225084817A</guid></item><item><title>Edited Issue: Early 'Not-Implemented' Exceptions Should Abort Test with 'Pending' Result [16120]</title><link>http://storyq.codeplex.com/workitem/16120</link><description>There is a discussion on this issue here&amp;#58; http&amp;#58;&amp;#47;&amp;#47;storyq.codeplex.com&amp;#47;discussions&amp;#47;256021&lt;br /&gt;&lt;br /&gt;The current implementation is problematic because earlier &amp;#39;Given&amp;#39; and &amp;#39;When&amp;#39; functions set things up for assertions in the later &amp;#39;Then&amp;#39; functions.  When the earlier functions throw a &amp;#39;Not-Implemented&amp;#39; exception it is likely that there will be exceptions in the later functions, like NotImplementedException, when asserting on complex objects that are set up in the earlier functions.&lt;br /&gt;&lt;br /&gt;In this situation it makes it hard to implement tests first and still have a passing integration build.  It is very important to be able to tell the difference between tests that are failing because something changed and tests that are &amp;#34;failing&amp;#34; because they were simply written before the implementation is complete.&lt;br /&gt;&lt;br /&gt;Please fix this.  It hurts nothing and helps those of us trying to write test first.&lt;br /&gt;</description><author>bjmarte</author><pubDate>Thu, 03 Nov 2011 20:04:21 GMT</pubDate><guid isPermaLink="false">Edited Issue: Early 'Not-Implemented' Exceptions Should Abort Test with 'Pending' Result [16120] 20111103080421P</guid></item><item><title>Edited Issue: Early 'Not-Implemented' Exceptions Should Abort Test with 'Pending' Result [16120]</title><link>http://storyq.codeplex.com/workitem/16120</link><description>There is a discussion on this issue here&amp;#58; &amp;#60;a href&amp;#61;&amp;#39;http&amp;#58;&amp;#47;&amp;#47;storyq.codeplex.com&amp;#47;discussions&amp;#47;256021&amp;#39;&amp;#62;discussion&amp;#60;&amp;#47;a&amp;#62;&lt;br /&gt;&lt;br /&gt;The current implementation is problematic because earlier &amp;#39;Given&amp;#39; and &amp;#39;When&amp;#39; functions set things up for assertions in the later &amp;#39;Then&amp;#39; functions.  When the earlier functions throw a &amp;#39;Not-Implemented&amp;#39; exception it is likely that there will be exceptions in the later functions, like NotImplementedException, when asserting on complex objects that are set up in the earlier functions.&lt;br /&gt;&lt;br /&gt;In this situation it makes it hard to implement tests first and still have a passing integration build.  It is very important to be able to tell the difference between tests that are failing because something changed and tests that are &amp;#34;failing&amp;#34; because they were simply written before the implementation is complete.&lt;br /&gt;&lt;br /&gt;Please fix this.  It hurts nothing and helps those of us trying to write test first.&lt;br /&gt;</description><author>bjmarte</author><pubDate>Thu, 03 Nov 2011 20:04:02 GMT</pubDate><guid isPermaLink="false">Edited Issue: Early 'Not-Implemented' Exceptions Should Abort Test with 'Pending' Result [16120] 20111103080402P</guid></item><item><title>Created Issue: Early 'Not-Implemented' Exceptions Should Abort Test with 'Pending' Result [16120]</title><link>http://storyq.codeplex.com/workitem/16120</link><description>There is a discussion on this issue here&amp;#58; http&amp;#58;&amp;#47;&amp;#47;storyq.codeplex.com&amp;#47;discussions&amp;#47;256021&lt;br /&gt;&lt;br /&gt;The current implementation is problematic because earlier &amp;#39;Given&amp;#39; and &amp;#39;When&amp;#39; functions set things up for assertions in the later &amp;#39;Then&amp;#39; functions.  When the earlier functions throw a &amp;#39;Not-Implemented&amp;#39; exception it is likely that there will be exceptions in the later functions, like NotImplementedException, when asserting on complex objects that are set up in the earlier functions.&lt;br /&gt;&lt;br /&gt;In this situation it makes it hard to implement tests first and still have a passing integration build.  It is very important to be able to tell the difference between tests that are failing because something changed and tests that are &amp;#34;failing&amp;#34; because they were simply written before the implementation is complete.&lt;br /&gt;&lt;br /&gt;Please fix this.  It hurts nothing and helps those of us trying to write test first.&lt;br /&gt;</description><author>bjmarte</author><pubDate>Thu, 03 Nov 2011 20:02:46 GMT</pubDate><guid isPermaLink="false">Created Issue: Early 'Not-Implemented' Exceptions Should Abort Test with 'Pending' Result [16120] 20111103080246P</guid></item><item><title>Commented Issue: Support the Silverlight Unit Test framework [16114]</title><link>http://storyq.codeplex.com/workitem/16114</link><description>Create a build of storyq that runs in silverlight.codeplex.com&amp;#39;s framework. Potential problems include picking up Console.Writeline text, and saving the report.xml file to disk&lt;br /&gt;Comments: Eagerly waiting for this to complete...</description><author>ajayjadhav</author><pubDate>Wed, 21 Sep 2011 19:25:24 GMT</pubDate><guid isPermaLink="false">Commented Issue: Support the Silverlight Unit Test framework [16114] 20110921072524P</guid></item><item><title>Commented Issue: support Test per Scenario in StoryQ GUI Converter [16116]</title><link>http://storyq.codeplex.com/workitem/16116</link><description>Just a personal preference here, but my preferred test style the test method-per-scenario approach, with a single story per test fixture&amp;#47;class &amp;#40;exactly as demonstrated in the StoryQ.Converter.Wpf.Specifications project in the source code, right down to the use of the SpecificationBase base class&amp;#41;.&lt;br /&gt;Each test fixture&amp;#47;class is named after the story, and each test method is named after the scenario.&lt;br /&gt;&lt;br /&gt;It would be a great time saver if this style could be added to the supported code generation strategies in the GUI converter.&lt;br /&gt;&lt;br /&gt;Comments: &amp;#43;1 - It would be beneficial, if a distinct TestMethod&amp;#47;Test could simply add a new scenario, have a failure during its Execute&amp;#40;&amp;#41; call show up as a fail for itself only, and yet still have its output nested under the story.</description><author>chicagogrooves</author><pubDate>Mon, 11 Jul 2011 18:53:11 GMT</pubDate><guid isPermaLink="false">Commented Issue: support Test per Scenario in StoryQ GUI Converter [16116] 20110711065311P</guid></item><item><title>Commented Issue: Story Title From Method Name [16106]</title><link>http://storyq.codeplex.com/workitem/16106</link><description>I like to call the method the same as the story title, i.e.&amp;#58;&lt;br /&gt;&lt;br /&gt;        &amp;#91;TestMethod&amp;#93;&lt;br /&gt;        public void EnsureAllItemsAreSameSize&amp;#40;&amp;#41;&lt;br /&gt;        &amp;#123;&lt;br /&gt;            new Story&amp;#40;&amp;#34;Ensure All Items Are Same Size&amp;#34;&amp;#41;&lt;br /&gt;            ...&lt;br /&gt;        &amp;#125;&lt;br /&gt;&lt;br /&gt;Therefore it would be nice if there was a default Story constructor that could use the method name to determine the title.&lt;br /&gt;Comments: I am also after something like this but I would like to use the fixture &amp;#40;class&amp;#41; name as the Story name and the test name as the scenario. What I do at the moment&amp;#58;&amp;#10;&amp;#10;&amp;#91;TestFixture&amp;#93;&amp;#10;public class When_adding&amp;#10;&amp;#123;&amp;#10;Feature story &amp;#61; new Story&amp;#40;&amp;#34;When adding&amp;#34;&amp;#41;...&amp;#59;&amp;#10;&amp;#10;&amp;#91;Test&amp;#93;&amp;#10;public void Should_add_two_positive_numbers&amp;#40;&amp;#41;&amp;#10;&amp;#123;&amp;#10;store.WithSenario&amp;#40;&amp;#34;Should add two positive numbers&amp;#34;&amp;#41;...&amp;#59;&amp;#10;&amp;#125;&amp;#10;&amp;#10;&amp;#91;Test&amp;#93;&amp;#10;public void Should_add_two_negative_numbers&amp;#40;&amp;#41;&amp;#10;&amp;#123;&amp;#10;store.WithSenario&amp;#40;&amp;#34;Should add two negative numbers&amp;#34;&amp;#41;...&amp;#59;&amp;#10;&amp;#125;&amp;#10;&amp;#10;&amp;#125;</description><author>bronumski</author><pubDate>Fri, 20 May 2011 23:44:49 GMT</pubDate><guid isPermaLink="false">Commented Issue: Story Title From Method Name [16106] 20110520114449P</guid></item><item><title>Commented Feature: Data Driven stories / scenarios [16117]</title><link>http://storyq.codeplex.com/workitem/16117</link><description>Storyq needs a way to run the same story over different parameter datasets. Ideally, we&amp;#39;d aggregate the results &amp;#40;like in Caley&amp;#39;s fork&amp;#41; and allow developers complete freedom regarding what the datasource is &amp;#40;passing an IEnumerable&amp;#60;T&amp;#62; would be good&amp;#41;.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Comments: No, the parser to convert text into StoryQ code is very rudimentary. The parser that creates the StoryQ fluent interface &amp;#40;a t4 template&amp;#41; is a bit different, it&amp;#39;s based on Dot &amp;#40;flit.codeplex.com&amp;#41;</description><author>robfe</author><pubDate>Tue, 17 May 2011 21:56:51 GMT</pubDate><guid isPermaLink="false">Commented Feature: Data Driven stories / scenarios [16117] 20110517095651P</guid></item><item><title>Commented Feature: Data Driven stories / scenarios [16117]</title><link>http://storyq.codeplex.com/workitem/16117</link><description>Storyq needs a way to run the same story over different parameter datasets. Ideally, we&amp;#39;d aggregate the results &amp;#40;like in Caley&amp;#39;s fork&amp;#41; and allow developers complete freedom regarding what the datasource is &amp;#40;passing an IEnumerable&amp;#60;T&amp;#62; would be good&amp;#41;.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Comments: Out of curiosity, does StoryQ use the official Gherkin parser&amp;#63;  I noticed that SpecFlow updates this parser with each of their releases.&amp;#10;&amp;#10;Gherkin Parser &amp;#40;official .NET implementation&amp;#41;&amp;#58;&amp;#10;https&amp;#58;&amp;#47;&amp;#47;github.com&amp;#47;cucumber&amp;#47;gherkin&amp;#47;blob&amp;#47;master&amp;#47;README.rdoc</description><author>jlb0001</author><pubDate>Tue, 17 May 2011 16:30:58 GMT</pubDate><guid isPermaLink="false">Commented Feature: Data Driven stories / scenarios [16117] 20110517043058P</guid></item><item><title>Commented Feature: Data Driven stories / scenarios [16117]</title><link>http://storyq.codeplex.com/workitem/16117</link><description>Storyq needs a way to run the same story over different parameter datasets. Ideally, we&amp;#39;d aggregate the results &amp;#40;like in Caley&amp;#39;s fork&amp;#41; and allow developers complete freedom regarding what the datasource is &amp;#40;passing an IEnumerable&amp;#60;T&amp;#62; would be good&amp;#41;.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Comments: Thanks jlb, I was just sitting down to work on this and these examples are very good inspiration. </description><author>robfe</author><pubDate>Mon, 16 May 2011 21:04:14 GMT</pubDate><guid isPermaLink="false">Commented Feature: Data Driven stories / scenarios [16117] 20110516090414P</guid></item><item><title>Commented Feature: Data Driven stories / scenarios [16117]</title><link>http://storyq.codeplex.com/workitem/16117</link><description>Storyq needs a way to run the same story over different parameter datasets. Ideally, we&amp;#39;d aggregate the results &amp;#40;like in Caley&amp;#39;s fork&amp;#41; and allow developers complete freedom regarding what the datasource is &amp;#40;passing an IEnumerable&amp;#60;T&amp;#62; would be good&amp;#41;.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Comments: This issue and the initiating discussion thread &amp;#40;http&amp;#58;&amp;#47;&amp;#47;storyq.codeplex.com&amp;#47;discussions&amp;#47;234652&amp;#41; reminds me of the &amp;#34;Examples&amp;#34; section that has been added to the &amp;#34;Scenario Outline&amp;#34; in Gherkin syntax.  For the sake of additional conversation, here are some posts that show how that plays out in the Gherkin syntax.  Since one of the goals for StoryQ is to covert from Gherkin, it&amp;#39;s not terribly important that we use one style of parameter-driven tests vs another in the generated C&amp;#35; -- whatever works, since it&amp;#39;ll be automatically generated most of the time, right&amp;#63;&amp;#10;&amp;#10;&amp;#34;Examples&amp;#34; section in &amp;#34;Scenario Outline&amp;#34;&amp;#58;&amp;#10;http&amp;#58;&amp;#47;&amp;#47;railscasts.com&amp;#47;episodes&amp;#47;159-more-on-cucumber&amp;#10;https&amp;#58;&amp;#47;&amp;#47;rspec.lighthouseapp.com&amp;#47;projects&amp;#47;16211&amp;#47;tickets&amp;#47;274-scenario-outline-ease-writing-examples&amp;#10;&amp;#10;In reading about the ways that data tables have evolved in Cucumber &amp;#47; Gherkin, these are the best examples of the syntax I could find that relates to this issue&amp;#58;&amp;#10;&amp;#10;https&amp;#58;&amp;#47;&amp;#47;github.com&amp;#47;cucumber&amp;#47;cucumber&amp;#47;wiki&amp;#47;Multiline-Step-Arguments&amp;#10;https&amp;#58;&amp;#47;&amp;#47;github.com&amp;#47;cucumber&amp;#47;cucumber&amp;#47;wiki&amp;#47;Scenario-outlines&amp;#10;&amp;#10;This quickly gets tangled with another table concept used in Cucumber where the tables are treated as a parameter in and of themselves whereby the entire table is compared as a value &amp;#40;i.e., not used as a substitution data driven table source&amp;#41;&amp;#58;&amp;#10;&amp;#10;https&amp;#58;&amp;#47;&amp;#47;github.com&amp;#47;coreyhaines&amp;#47;practice_game_of_life&amp;#47;blob&amp;#47;master&amp;#47;features&amp;#47;multiple_generations.feature&amp;#10;https&amp;#58;&amp;#47;&amp;#47;github.com&amp;#47;aslakhellesoy&amp;#47;cucumber-rails-test&amp;#47;blob&amp;#47;master&amp;#47;features&amp;#47;manage_lorries.feature</description><author>jlb0001</author><pubDate>Mon, 16 May 2011 20:40:13 GMT</pubDate><guid isPermaLink="false">Commented Feature: Data Driven stories / scenarios [16117] 20110516084013P</guid></item><item><title>Commented Issue: Gherkin Syntax [16119]</title><link>http://storyq.codeplex.com/workitem/16119</link><description>I am wondering about Gherkin formality in the  parsing application, StoryQ.Converter.Wpf.exe&lt;br /&gt;&lt;br /&gt;Rather than &lt;br /&gt;&lt;br /&gt;&amp;#34;Story is&amp;#34;, The common Gherkin expression I see is &amp;#34;Feature&amp;#58;&amp;#34;&lt;br /&gt;&lt;br /&gt;Likewise, &amp;#34;With Scenario&amp;#34; becomes &amp;#34;Scenario&amp;#58;&amp;#34;&lt;br /&gt;&lt;br /&gt;This might seem a subtle point, but the standard notation sets off the important elements of the requirement to my eyes and just seems tighter. I suppose it would be easy enough to add in support for both syntaxes.S&lt;br /&gt;&lt;br /&gt;&amp;#34;So, pull the code, Dave.&amp;#34;&lt;br /&gt;&lt;br /&gt;&amp;#34;yeah, yeah, I hear you&amp;#34;&lt;br /&gt;Comments: LOL&amp;#33; Awesome&amp;#33; Thank you&amp;#33;</description><author>DaddyStarr</author><pubDate>Tue, 03 May 2011 13:01:34 GMT</pubDate><guid isPermaLink="false">Commented Issue: Gherkin Syntax [16119] 20110503010134P</guid></item><item><title>Commented Issue: Gherkin Syntax [16119]</title><link>http://storyq.codeplex.com/workitem/16119</link><description>I am wondering about Gherkin formality in the  parsing application, StoryQ.Converter.Wpf.exe&lt;br /&gt;&lt;br /&gt;Rather than &lt;br /&gt;&lt;br /&gt;&amp;#34;Story is&amp;#34;, The common Gherkin expression I see is &amp;#34;Feature&amp;#58;&amp;#34;&lt;br /&gt;&lt;br /&gt;Likewise, &amp;#34;With Scenario&amp;#34; becomes &amp;#34;Scenario&amp;#58;&amp;#34;&lt;br /&gt;&lt;br /&gt;This might seem a subtle point, but the standard notation sets off the important elements of the requirement to my eyes and just seems tighter. I suppose it would be easy enough to add in support for both syntaxes.S&lt;br /&gt;&lt;br /&gt;&amp;#34;So, pull the code, Dave.&amp;#34;&lt;br /&gt;&lt;br /&gt;&amp;#34;yeah, yeah, I hear you&amp;#34;&lt;br /&gt;Comments: Fixed in changeset 38a38cbc6d45</description><author>robfe</author><pubDate>Mon, 02 May 2011 21:32:28 GMT</pubDate><guid isPermaLink="false">Commented Issue: Gherkin Syntax [16119] 20110502093228P</guid></item><item><title>Edited Issue: Gherkin Syntax [16119]</title><link>http://storyq.codeplex.com/workitem/16119</link><description>I am wondering about Gherkin formality in the  parsing application, StoryQ.Converter.Wpf.exe&lt;br /&gt;&lt;br /&gt;Rather than &lt;br /&gt;&lt;br /&gt;&amp;#34;Story is&amp;#34;, The common Gherkin expression I see is &amp;#34;Feature&amp;#58;&amp;#34;&lt;br /&gt;&lt;br /&gt;Likewise, &amp;#34;With Scenario&amp;#34; becomes &amp;#34;Scenario&amp;#58;&amp;#34;&lt;br /&gt;&lt;br /&gt;This might seem a subtle point, but the standard notation sets off the important elements of the requirement to my eyes and just seems tighter. I suppose it would be easy enough to add in support for both syntaxes.S&lt;br /&gt;&lt;br /&gt;&amp;#34;So, pull the code, Dave.&amp;#34;&lt;br /&gt;&lt;br /&gt;&amp;#34;yeah, yeah, I hear you&amp;#34;&lt;br /&gt;</description><author>robfe</author><pubDate>Mon, 02 May 2011 21:32:28 GMT</pubDate><guid isPermaLink="false">Edited Issue: Gherkin Syntax [16119] 20110502093228P</guid></item><item><title>Closed Issue: Parameterized Test fails with ExecuteWithReport() [16118]</title><link>http://storyq.codeplex.com/workitem/16118</link><description>Good evening folks.&lt;br /&gt;&lt;br /&gt;This is practically my first test with StoryQ and my first post to a CodePlex forum, so apologies in advance&lt;br /&gt;&lt;br /&gt;The test is failing when I do&lt;br /&gt;&lt;br /&gt;&amp;#9;.ExecuteWithReport&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;&lt;br /&gt;It passes when I just do&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#9;.Execute&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;&lt;br /&gt;I&amp;#39;ve been able to get a simple test to pass with .ExecuteWithReport&amp;#40;&amp;#41;&amp;#59; but NOT this parameterized one.&lt;br /&gt;&lt;br /&gt;PS&amp;#58; I understand that I&amp;#39;m not allowed underscores in method names but what about variables&amp;#63;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Apendix 1&amp;#58; Stack Trace &amp;#40;for first test&amp;#41;&lt;br /&gt;&lt;br /&gt;C&amp;#58;&amp;#92;Data&amp;#92;Websites&amp;#92;MyWeb&amp;#92;MyWeb.Tests.UAT&amp;#92;bin&amp;#92;Release&lt;br /&gt;Story is will check that links work&lt;br /&gt;  In order to see that links work&lt;br /&gt;  As a non-subscriber&lt;br /&gt;  I want to click each link&lt;br /&gt;&lt;br /&gt;      With scenario &lt;br /&gt;        Given I am on the login page            &amp;#61;&amp;#62; Passed&lt;br /&gt;        When I click a link&amp;#40;mw_ContactViaLogin&amp;#41; &amp;#61;&amp;#62; Passed&lt;br /&gt;        Then I go to the right page             &amp;#61;&amp;#62; Passed&lt;br /&gt;TestCase &amp;#39;MyWeb.Tests.UAT.StoryQ.Client.OnLoginPageButNotLoggedIn.AllTheLinksWillWork&amp;#40;&amp;#41;&amp;#39;&lt;br /&gt;failed&amp;#58; System.ArgumentNullException &amp;#58; Value cannot be null.&lt;br /&gt;Parameter name&amp;#58; value&lt;br /&gt;  at System.Xml.Linq.XAttribute..ctor&amp;#40;XName name, Object value&amp;#41;&lt;br /&gt;  at StoryQ.Execution.Rendering.XmlRenderer.&amp;#60;Render&amp;#62;b__0&amp;#40;Result x&amp;#41;&lt;br /&gt;  at System.Linq.Enumerable.WhereSelectListIterator&amp;#96;2.MoveNext&amp;#40;&amp;#41;&lt;br /&gt;  at System.Xml.Linq.XContainer.AddContentSkipNotify&amp;#40;Object content&amp;#41;&lt;br /&gt;  at System.Xml.Linq.XContainer.AddContentSkipNotify&amp;#40;Object content&amp;#41;&lt;br /&gt;  at System.Xml.Linq.XElement..ctor&amp;#40;XName name, Object&amp;#91;&amp;#93; content&amp;#41;&lt;br /&gt;  at StoryQ.Execution.Rendering.XmlRenderer.Render&amp;#40;IEnumerable&amp;#96;1 results&amp;#41;&lt;br /&gt;  at StoryQ.Infrastructure.FragmentBase.&amp;#60;&amp;#62;c__DisplayClass7.&amp;#60;StoryQ.Infrastructure.IStepContainer.Execute&amp;#62;b__5&amp;#40;IRenderer x&amp;#41;&lt;br /&gt;  at System.Array.ForEach&amp;#91;T&amp;#93;&amp;#40;T&amp;#91;&amp;#93; array, Action&amp;#96;1 action&amp;#41;&lt;br /&gt;  at StoryQ.Infrastructure.FragmentBase.StoryQ.Infrastructure.IStepContainer.Execute&amp;#40;IRenderer&amp;#91;&amp;#93; renderers&amp;#41;&lt;br /&gt;  at StoryQ.Infrastructure.FragmentBase.ExecuteWithReport&amp;#40;MethodBase currentMethod&amp;#41;&lt;br /&gt;  at StoryQ.Infrastructure.FragmentBase.ExecuteWithReport&amp;#40;&amp;#41;&lt;br /&gt;  C&amp;#58;&amp;#92;Data&amp;#92;Websites&amp;#92;MyWeb&amp;#92;MyWeb.Tests.UAT&amp;#92;StoryQ&amp;#92;Client&amp;#92;OnLoginPageButNotLoggedIn.cs&amp;#40;47,0&amp;#41;&amp;#58; at MyWeb.Tests.UAT.StoryQ.Client.OnLoginPageButNotLoggedIn.AllTheLinksWillWork&amp;#40;HyperLink link&amp;#41;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;PS&amp;#58; Line 47 of OnLoginPageButNotLoggedIn is the line beginning&amp;#58; new Story&amp;#40;&amp;#34;will check that links work&amp;#34;&amp;#41;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Apendix 2&amp;#58; The Code&amp;#58;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;using System&amp;#59;&lt;br /&gt;using System.Collections.Generic&amp;#59;&lt;br /&gt;using System.Linq&amp;#59;&lt;br /&gt;using System.Text&amp;#59;&lt;br /&gt;using StoryQ&amp;#59;&lt;br /&gt;using NUnit.Framework&amp;#59;&lt;br /&gt;using OpenQA.Selenium.IE&amp;#59;&lt;br /&gt;&lt;br /&gt;namespace MyWeb.Tests.UAT.StoryQ.Client&lt;br /&gt;&amp;#123;&lt;br /&gt;  &amp;#91;TestFixture&amp;#93;&lt;br /&gt;  public class OnLoginPageButNotLoggedIn&lt;br /&gt;  &amp;#123;&lt;br /&gt;    private InternetExplorerDriver _driver&amp;#59;&lt;br /&gt;&lt;br /&gt;    &amp;#91;TestFixtureSetUp&amp;#93;&lt;br /&gt;    public void FixtureSetUp&amp;#40;&amp;#41;&lt;br /&gt;    &amp;#123;&lt;br /&gt;      _driver &amp;#61; new InternetExplorerDriver&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;      _driver.Manage&amp;#40;&amp;#41;.Timeouts&amp;#40;&amp;#41;.ImplicitlyWait&amp;#40;new TimeSpan&amp;#40;0, 0, 30&amp;#41;&amp;#41;&amp;#59;&lt;br /&gt;    &amp;#125;&lt;br /&gt;&lt;br /&gt;    &amp;#91;TestFixtureTearDown&amp;#93;&lt;br /&gt;    public void FixtureTearDown&amp;#40;&amp;#41;&lt;br /&gt;    &amp;#123;&lt;br /&gt;      if &amp;#40;_driver &amp;#33;&amp;#61; null&amp;#41; _driver.Close&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;    &amp;#125;&lt;br /&gt;&lt;br /&gt;    &amp;#91;SetUp&amp;#93;&lt;br /&gt;    public void TestSetUp&amp;#40;&amp;#41;&lt;br /&gt;    &amp;#123;&lt;br /&gt;      _driver.Navigate&amp;#40;&amp;#41;.GoToUrl&amp;#40;Constants.LOGIN_URL&amp;#41;&amp;#59;&lt;br /&gt;&lt;br /&gt;    &amp;#125;&lt;br /&gt;&lt;br /&gt;    &amp;#91;Test, TestCaseSource&amp;#40;typeof&amp;#40;HyperLink&amp;#41;, &amp;#34;LinkArray&amp;#34;&amp;#41;&amp;#93; &lt;br /&gt;    public void AllTheLinksWillWork&amp;#40;HyperLink link&amp;#41;&lt;br /&gt;    &amp;#123;&lt;br /&gt;      Console.WriteLine&amp;#40;Environment.CurrentDirectory&amp;#41;&amp;#59;&lt;br /&gt;&lt;br /&gt;      new Story&amp;#40;&amp;#34;will check that links work&amp;#34;&amp;#41;&lt;br /&gt;        .InOrderTo&amp;#40;&amp;#34;see that links work&amp;#34;&amp;#41;&lt;br /&gt;        .AsA&amp;#40;&amp;#34;non-subscriber&amp;#34;&amp;#41;&lt;br /&gt;        .IWant&amp;#40;&amp;#34;to click each link&amp;#34;&amp;#41;&lt;br /&gt;        .WithScenario&amp;#40;link.Description&amp;#41;&lt;br /&gt;        .Given&amp;#40;IAmOnTheLoginPage&amp;#41;&lt;br /&gt;        .When&amp;#40;IClickALink, link.LinkID&amp;#41;&lt;br /&gt;        .Then&amp;#40;IGoToTheRightPage, link&amp;#41;&lt;br /&gt;        .ExecuteWithReport&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;&lt;br /&gt;    &amp;#125;&lt;br /&gt;&lt;br /&gt;    public void IAmOnTheLoginPage&amp;#40;&amp;#41;&lt;br /&gt;    &amp;#123;&lt;br /&gt;      Assert.True&amp;#40;_driver.Url.Contains&amp;#40;Constants.LOGIN_PAGE&amp;#41;, &amp;#34;I&amp;#39;m not on the login page&amp;#34;&amp;#41;&amp;#59;&lt;br /&gt;    &amp;#125;&lt;br /&gt;&lt;br /&gt;    public void IClickALink&amp;#40;string linkID&amp;#41;&lt;br /&gt;    &amp;#123;&lt;br /&gt;      _driver.FindElementById&amp;#40;linkID&amp;#41;.Click&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;    &amp;#125;&lt;br /&gt;&lt;br /&gt;    public void IGoToTheRightPage&amp;#40;HyperLink link&amp;#41;&lt;br /&gt;    &amp;#123;&lt;br /&gt;      Assert.AreEqual&amp;#40;link.PageTitle, _driver.Title, &amp;#34;Title is wrong&amp;#34;&amp;#41;&amp;#59;&lt;br /&gt;      Assert.AreEqual&amp;#40;link.Url, _driver.Url, &amp;#34;Url is wrong&amp;#34;&amp;#41;&amp;#59;&lt;br /&gt;      Assert.IsTrue&amp;#40;_driver.PageSource.Contains&amp;#40;link.SomeContent&amp;#41;, &amp;#34;Page does not contains expected&amp;#58; &amp;#34; &amp;#43; link.SomeContent&amp;#41;&amp;#59;&lt;br /&gt;    &amp;#125;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;  &amp;#125;&lt;br /&gt;&lt;br /&gt;  public class HyperLink&lt;br /&gt;  &amp;#123;&lt;br /&gt;    public string LinkID &amp;#123; get&amp;#59; set&amp;#59; &amp;#125;&lt;br /&gt;    public string Description &amp;#123; get&amp;#59; set&amp;#59; &amp;#125;&lt;br /&gt;    public bool IsSlow &amp;#123; get&amp;#59; set&amp;#59; &amp;#125;&lt;br /&gt;    public string PageTitle &amp;#123; get&amp;#59; set&amp;#59; &amp;#125;&lt;br /&gt;    public string Url &amp;#123; get&amp;#59; set&amp;#59; &amp;#125;&lt;br /&gt;    public string SomeContent &amp;#123; get&amp;#59; set&amp;#59; &amp;#125;&lt;br /&gt;&lt;br /&gt;    public HyperLink&amp;#40;&amp;#41; &amp;#123; &amp;#125;&lt;br /&gt;&lt;br /&gt;    public HyperLink&amp;#40;string linkID, string description, bool isSlow, string title, string url, string content&amp;#41;&lt;br /&gt;    &amp;#123;&lt;br /&gt;      this.LinkID &amp;#61; linkID&amp;#59;&lt;br /&gt;      this.Description &amp;#61; Description&amp;#59;&lt;br /&gt;      this.IsSlow &amp;#61; isSlow&amp;#59;&lt;br /&gt;      this.PageTitle &amp;#61; title&amp;#59;&lt;br /&gt;      this.Url &amp;#61; url&amp;#59;&lt;br /&gt;      this.SomeContent &amp;#61; content&amp;#59;&lt;br /&gt;    &amp;#125;&lt;br /&gt;&lt;br /&gt;    public override string ToString&amp;#40;&amp;#41;&lt;br /&gt;    &amp;#123;&lt;br /&gt;      return Description&amp;#59;&lt;br /&gt;    &amp;#125;&lt;br /&gt;&lt;br /&gt;    public static List&amp;#60;HyperLink&amp;#62; Links &amp;#61; new List&amp;#60;HyperLink&amp;#62;&lt;br /&gt;    &amp;#123;&lt;br /&gt;      new HyperLink &amp;#40;&amp;#34;SubscriptionLink&amp;#34;, &amp;#34;Subscription Link&amp;#34;   , false, Constants.Contact_Title, Constants.CONTACT_URL, Constants.Contact_Content&amp;#41;,&lt;br /&gt;      new HyperLink &amp;#40;&amp;#34;ForgotPassword&amp;#34;  , &amp;#34;Forgot Password Link&amp;#34;, false, Constants.Contact_Title, Constants.CONTACT_URL_ForgotPassword, Constants.Contact_Content&amp;#41;&lt;br /&gt;    &amp;#125;&amp;#59;&lt;br /&gt;&lt;br /&gt;    public static HyperLink&amp;#91;&amp;#93; LinkArray &amp;#61; Links.ToArray&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;&lt;br /&gt;  &amp;#125;&lt;br /&gt;&amp;#125;&lt;br /&gt;&lt;br /&gt;Comments: Can only assume this is the issue that was fixed without more feedback...</description><author>robfe</author><pubDate>Mon, 02 May 2011 21:01:58 GMT</pubDate><guid isPermaLink="false">Closed Issue: Parameterized Test fails with ExecuteWithReport() [16118] 20110502090158P</guid></item><item><title>Created Issue: Gherkin Syntax [16119]</title><link>http://storyq.codeplex.com/workitem/16119</link><description>I am wondering about Gherkin formality in the  parsing application, StoryQ.Converter.Wpf.exe&lt;br /&gt;&lt;br /&gt;Rather than &lt;br /&gt;&lt;br /&gt;&amp;#34;Story is&amp;#34;, The common Gherkin expression I see is &amp;#34;Feature&amp;#58;&amp;#34;&lt;br /&gt;&lt;br /&gt;Likewise, &amp;#34;With Scenario&amp;#34; becomes &amp;#34;Scenario&amp;#58;&amp;#34;&lt;br /&gt;&lt;br /&gt;This might seem a subtle point, but the standard notation sets off the important elements of the requirement to my eyes and just seems tighter. I suppose it would be easy enough to add in support for both syntaxes.S&lt;br /&gt;&lt;br /&gt;&amp;#34;So, pull the code, Dave.&amp;#34;&lt;br /&gt;&lt;br /&gt;&amp;#34;yeah, yeah, I hear you&amp;#34;&lt;br /&gt;</description><author>robfe</author><pubDate>Mon, 02 May 2011 21:00:55 GMT</pubDate><guid isPermaLink="false">Created Issue: Gherkin Syntax [16119] 20110502090055P</guid></item><item><title>Edited Issue: Support the Silverlight Unit Test framework [16114]</title><link>http://storyq.codeplex.com/workitem/16114</link><description>Create a build of storyq that runs in silverlight.codeplex.com&amp;#39;s framework. Potential problems include picking up Console.Writeline text, and saving the report.xml file to disk&lt;br /&gt;</description><author>robfe</author><pubDate>Mon, 02 May 2011 19:57:40 GMT</pubDate><guid isPermaLink="false">Edited Issue: Support the Silverlight Unit Test framework [16114] 20110502075740P</guid></item><item><title>Closed Feature: Leverage C# dynamic for .NET 4 [16101]</title><link>http://storyq.codeplex.com/workitem/16101</link><description>There are some cool ways that StoryQ could leverage C&amp;#35; 4&amp;#39;s dynamic keyword. I have plans that would make the following work&amp;#58;&lt;br /&gt;&lt;br /&gt;dynamic given &amp;#61; new DynamicStepGenerator&amp;#40;this&amp;#41;&amp;#59;&lt;br /&gt;&lt;br /&gt;given.someMethodNameThatDoesntExist&amp;#40;10&amp;#41;&lt;br /&gt;when.someMethodThatIsOnThis&amp;#40;true&amp;#41;&amp;#59;&lt;br /&gt;Comments: If we did do this, we&amp;#39;d be losing our StoryQness - it would deserve to be its own project...</description><author>robfe</author><pubDate>Tue, 01 Mar 2011 22:31:04 GMT</pubDate><guid isPermaLink="false">Closed Feature: Leverage C# dynamic for .NET 4 [16101] 20110301103104P</guid></item><item><title>Closed Issue: System.IO.FileLoadException: Could not load file or assembly 'StoryQ, [16112]</title><link>http://storyq.codeplex.com/workitem/16112</link><description>Test method StoryQ.StoryQTestClass.ARomanticEvening threw exception&amp;#58; &lt;br /&gt;System.IO.FileLoadException&amp;#58; Could not load file or assembly &amp;#39;StoryQ, Version&amp;#61;2.0.4.12787, Culture&amp;#61;neutral, PublicKeyToken&amp;#61;90a7d07ba39412de&amp;#39; or one of its dependencies. The located assembly&amp;#39;s manifest definition does not match the assembly reference. &amp;#40;Exception from HRESULT&amp;#58; 0x80131040&amp;#41;&lt;br /&gt;&lt;br /&gt;I created a new C&amp;#35; test project in VS2010. Added my code file &amp;#40;attached &amp;#41; and it threw an error once I hit F5 to debug. any thoughts&amp;#63;&lt;br /&gt;</description><author>robfe</author><pubDate>Tue, 01 Mar 2011 22:30:37 GMT</pubDate><guid isPermaLink="false">Closed Issue: System.IO.FileLoadException: Could not load file or assembly 'StoryQ, [16112] 20110301103037P</guid></item></channel></rss>