Skip to content
davidmfoley edited this page Mar 8, 2011 · 50 revisions

future

- Visual Studio add-in:
– supports Syntax highlighting of plaintext files
– May also support navigating from feature file to implementation (or this may be postponed to 0.8)

version 0.7 (March 2011)

- supports .NET 4.0
- zero-config mode: storevil.config no longer required (StorEvil will infer settings)
- Many enhancements to ReSharper Integration
– Each example in a scenario outline is listed as a separate test
– Stability, sorting
– Ability to set breakpoint in plaintext in Visual Studio.
- new command: “glossary” – creates a report of all available context steps.
- Many bugfixes (thanks to Eric Lee [http://github.com/SaintGimp]])

version 0.6 (23 August 2010)

- ReSharper Integration – A test runner plugin for ReSharper.
- Custom Event Handlers – Allows extending StorEvil.
- Added an MSBuild Task that runs StorEvil specs.
- Team City Integration – reports StorEvil results in TeamCity. (Thanks to Pawel Pabich )
- StorEvil is now a Nu Gem (Thanks to: Bil Simser, Dru Sellers and everyone on the Nubular team )

version 0.5 (2 August 2010)

- Support for Backgrounds (Gherkin feature: common setup for all scenarios in a file)
- Custom Parameter Conversion by implementing CustomParameterConverter
- Added Guid parsing
- Context lifetime can now be set (per Session, Story or Scenario) docs here: StorEvil Context Classes
– Enables you “keep around” expensive contexts and do per-run or per-story setup/teardown
– For example, database setup/teardown or Watin/Selenium session creation/destruction
- Change: StorEvil now prefers context methods that have been used in the current scenario, rather than throwing MatchResolutionExceptions when a line can match multiple methods.
- Fixed bugs: negative numbers, outline table parsing, etc.
- Moved StorEvil to Visual Studio 2010

version 0.4 (10 April 2010)

- Debugging support
– new command “debug”… similar to “execute” but supports debugging
– Can set breakpoints in NUnit and Debug modes
– Supports F5 debugging in Visual Studio. (See release notes)
– Fixed bugs
– updated build script

version 0.3 (30 March 2010)

- Automated build, tests & packaging

- Supports @tags, similar to cucumber, on Stories and Scenarios (only inclusive tags, not exclusive)

- Brings NUnit-fixture generation on par with in-place execution

- Supports parsing arrays of custom types & hashtables

- Added tutorial and new screencast for dealing with tabular data

version 0.2 (16 March 2010)

HTML output

- Nicer HTML output by default. - Added suggestions for not implemented grammar to the default HTML template

Separated Assertions from Core

- Moved the ShouldXXXX extension methods out to a separate assembly (StorEvil.Assertions), so you can use StorEvil without them if desired.

- Add StorEvil.Assertions to your Assemblies list in storevil.config to include these extension methods.

Automatic stubbing

- Added a new command “stub” which can be used to generate the initial set of context classes to a file, the clipboard, or stdout.

- Generates stubs for any plaintext steps that could not be interpreted.

usage:
storevil stub (--destination {destination_file_name} | --clipboard )

- if no args specified, it will write to stdout (the console)

- Made some improvements to the suggestion engine when dealing with scenario outline parameters.

Added two more example projects

- Bowling – features were copied from the SpecFlow project (note: different license for these files than the rest of StorEvil)

- Tic Tac Toe

Parsing/interpreting improvements

- double-quoted strings are treated as a single term

- everything after a colon is treated as a single term

- comma-separated values can be automatically mapped to an array

- Handle apostrophes (in contractions… map plaintext “it’s” to C# “its”).

- HashTable/Dictionary & typed single argument parsing of Key/Value data in a table.

Tracing/debugging

- Added command line switch --debug which enables some tracing output

version 0.1 (10 March 2010)

- Initial binary release

Future

- Consolidate exception handling & display to user
- Web Automation example
- i18n …
– Parser/interpreter: handle grammar rules that are different (special treatment of “and”, “a/an”, genders, punctuation etc.)
– Messages: localize and move to resources
- More documentation
- Screencasts demonstrating more advanced features and implementation.