ParagraphGrammar is untested as of right now. It's simple though. Just wanna use the old test data instead of having to make new ones;)

It would be good to have the Web.config for your StoryTeller project to be located at the project root instead of the bin directory.

I vote for depending on TD.Net as an adhoc runner

One of the things that stinks about having xml files that map to Grammars which in many cases are Methods is that you can't easily see where it's usages are when you are refactoring code. I would ideally like to fail a build if a grammar is removed, but tests still rely on that grammar.

Not sure we care, but if we do, add it back in.

See: http://confluence.jetbrains.com/display/TCD8/Including+Third-Party+Reports+in+the+Build+Results#IncludingThird-PartyReportsintheBuildResults-priorto8.1

The TeamCityListener work just needs to be flat out redone. The test observer infrastructure needs to know about the semantics of retries so that the listener can be a lot dumber and report when it's told to.

This is also a place holder to bring back the TC listener since it's been removed until we get to this.

Speed baby, speed!

Replace the purely reflection based approach w/ something that creates an Expression and compiles to a Func.

Let's wait until the WPF client is dead and the StoryTellerRunner.exe merges in. Or just deliver StorytellerRunner only for right now.

In the ui when you filter tests then execute a test suite via Ctrl+Click all tests in that suite are run. I'd expect to only have the filtered tests run.

Already fixed, but tracking this.

There are many times that we know that if a particular step fails then the rest of the test is doomed. Having a special exception that will stop the test and prevent the remainder of the grammars from running, would improve test run time and developer productivity.

which of course, originated in Storyteller 1 before moving to FubuCore;-)

Use the EquivalenceChecker, but have the selections built into the Cell construction

Maybe it would be convenient to combine EquivalenceChecker into Conversions so you can pass it all down at the same time

I'm not entirely sure this is necessary. Might be better to just add an option to embed a Sentence as the "before." Not doing unless this is used by the OE project at work.

Was in 2, add to 3.

Also add the [Header] attribute back in

Something like [ModifyCellAttribute] as a base class so you could do almost anything.

Maybe? Allow you to merge the two tools?

This time, we're gonna keep the service location completely separate from the state tracking within a spec run.

cc: @kharlamov

This has been a request over the years. Allow for selection lists that are built at runtime by the system under test instead of wired into Fixture or grammars. So you could do crazy things like build it from db tables or some such.

Add a table of contents page that isn't horrible. Need this for the executable spec story

When and only when we need this for the pilot project.

Not sure how we'll do it yet.

Merge the StorytellerRunner.exe into just storyteller.exe and use FubuCore CLI all the way through

Basically copy from FubuCore. If a concrete type has the constructor function w/ signature new(string), use that w/ the raw data to "convert"

Forget the silly open/create new project & history feature. Just do storyteller /some/dir and it works

Add IList/IEnumerable checking, have it delegate to the inner maybe

App.config in main directory
Web.config in main directory
assembly name config in bin/Target

hi all! @jeremydmiller pointed me here from the old site. I would like to +1 this post below. Is there a blog or anything that shows why you like StoryTeller, why you wrote it, and perhaps compares it to RSpec, which I love?
thank you!

https://groups.google.com/forum/#!topic/storyteller-dotnet-users/pOmk1b3JfyA
StoryTeller Documentation - Google Groups
StoryTeller Users ›
StoryTeller Documentation
1 post by 1 author
Fábio Luiz Esperati Pagoti
8/11/12
Hello guys,
I would like to give a try to StoryTeller but I have no idea what is, how to install, how to use, where I can find information etc. (Nothing apart from this group).
Is there any documentation available?

I strongly suggest to update the Read Me file inside git with useful information about the project.

I'm working with testing and I'm seeking some great open source ideas. StoryTeller gave me a bad impression for it lack of information but I'm willing to contribute if I like the idea.

This would make the artifact usage a lot easier in TeamCity. There's a way to define system-wide report tabs and reference zip files (and files inside of them).

Would let us define a report tab like:
StoryTeller | storyteller.zip!Storyteller.html

...instead of setting things up per-project.

Would be nice to treat these separately to help beat the problem with the "first run" timing out.

Use FubuCsProjFile templating to do it

Dependent upon the command line changes

• Add ST2 nuget reference
• Add the stupid ST2 project.xml, but we'll make that go away later
• Add a new ISystem that inherits from BasicSystem for now
• Add a Fixtures folder
• Add a Tests folder
• Add rake task to execute the ST tests for CI
• Add rake task to open the ST editor
• Make an all new command to do this.

fubu storyteller [Original Project] --name [name] --system-name [system-name]

Imported from FubuMvcArchive/fubu#34

If the ISystem is not specified -->

1.) If there is only one concrete ISystem w/ a public ctor, use that.
2.) If there is more than one, look for the only one in an assembly matching the folder name
3.) If there is still more than one, use NulloSystem

• Make the binary folder and test folders be opinionated w/ zero configuration
• Don't require the system. Use NulloSystem if absolutely nothing, use the one system if there's only one in the AppDomain
• Get the test template into just a text file and out of the project model

Mostly for the WebDriver "use Phantom in CI, Firefox/Chrome in UI" scenario

Prolly need to add to the fuburake helper as well.