I was just able to push the official Nugets for Storyteller 4.2 with some cool new features we built for my shop’s internal automated testing, including:
- Storyteller 4.2
- dotnet-storyteller 1.1.2
- Storyteller.AspNetCore 1.0
- Storyteller RDBMS 1.0
- StorytellerRunner 1.1.2 (used by dotnet storyteller)
- StorytellerRunnerCsproj 4.2 (the classic csproj/appdomain runner for .Net 4.6 apps)
The entire list of Github issues in the 4.2 release is here.
- Built in support to make declarative checks against the expected structure of a Json string via the JsonComparisonFixture class
- Support for using Storyteller to write specifications against ASP.Net Core applications via the new Storyteller.AspNetCore nuget. See also
- Support for addressing and verifying databases with the new Storyteller.RDBMS nuget. See also A Concept for Integrated Database Testing within Storyteller.
- New Fixture base classes for checking model state (CheckModelFixture), setting up model state (ModelFixture), and executing API’s that can be treated as “one model in, one model out” using the new ApiFixture
- A new extension model for the Storyteller engine
What’s Coming Next for Storyteller?
- The big thing coming next is a dotnet test adapter for VS2017 so that you can easily kick off or debug Storyteller specifications from within Visual Studio.Net or JetBrains Rider
- Fleshing out the Selenium add-on
- It’s an oddball thing, but we have a proof of concept for an approach to test React/Redux frontend’s subcutaneously with Storyteller. If that works out, we’ll be publishing that add on as well