Skip to main content

SpecFlow v2 finally arrived

We had to wait for it a long time, but now it’s finally there, a new release of SpecFlow; my favorite  Behaviour-Driven Development (BDD) tool.

So what’s new?

Important changes in SpecFlow V2 include:

  • All components upgraded to .NET 4.5.
  • Upgraded to the new Gherkin 3 parser
  • Support for parallel SpecFlow tests within the same AppDomain
  • Visual Studio integration has been separated to a separate project
  • Support for xUnit 2.0 and NUnit 3.0, including parallel test execution. The older providers have been retained and renamed (to xunit.1 and nunit.2 respectively).
  • Ability to determine the execution order of hooks (e.g. [BeforeScenario])
  • Extensible table conversions and comparisons for CreateSet, CreateInstance, CompareToSet and CompareToInstance.
  • Access the details of the currently executed step with ScenarioContext.StepContext
  • Display tags in NUnit test adapter in Visual Studio
  • Better regular expression suggestions generated for missing steps with quoted parameters
  • Steps base class provides properties for thread-safe access to feature, scenario and step contexts
  • Scenario and feature context can be injected to the binding class, avoiding static ScenarioContext.Current and FeatureContext.Current accessors
  • Better matching of column names to property names by removing characters that are invalid in property names
  • Small improvements in the DI framework
  • Easily configure SpecFlow to work with MSTest using the SpecFlow.MsTest NuGet package
  • Test execution report now includes “tags” in the NUnit report, which can be displayed using a custom XSLT
  • Removed .NET runtime version from generated file headers to avoid unwanted changes

If you never used SpecFlow before, now is a good time to try it out. Writing tests will never be the same again…

Remark: If you are already using SpecFlow today, don’t forget to check the upgrade guide: http://www.specflow.org/updating-to-specflow-2/

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more