Skip to main content

SpecFlow Reusable steps

I’m a big fan of SpecFlow, a BDD style testing framework for .NET. For me it was a life changer, that made testing fun again.
As you start to use SpecFlow more and more, you’ll see the same test steps appear over and over again. The guys from Endjin recognized the same pattern and bundled some of these steps in a re-usable NuGet package(together with some other useful functionality) .
Here is the list of features from the GitHub site:
    • Path & ScenarioContext extensions
    • Shared Steps for dealing with Exceptions:
      [Then(@"an ""(.*)"" should be thrown")]
[Then(@"a ""(.*)"" should be thrown")]
     
      And Results:
            
        [Then(@"the result count should be (.*)")]
  [Then(@"the result should equal the datetime (.*)")]
  [Then(@"the result should equal the datetimeoffset (.*)")]
  [Then(@"the result should equal the integer (.*)")]
  [Then(@"the result should equal the string ""(.*)""")]
  [Then(@"the result should be false")]
  [Then(@"the result should be greater than the datetime (.*)")]
  [Then(@"the result should be greater than the datetimeoffset (.*)")]
  [Then(@"the result should be greater than the integer (.*)")]
  [Then(@"the result should be greater than or equal to the datetime (.*)")]
  [Then(@"the result should be greater than or equal to the datetimeoffset (.*)")]
  [Then(@"the result should be greater than or equal to the integer (.*)")]
  [Then(@"the result should be less than the datetime (.*)")]
  [Then(@"the result should be less than the datetimeoffset (.*)")]
  [Then(@"the result should be less than the integer (.*)")]
  [Then(@"the result should be less than or equal to the datetime (.*)")]
  [Then(@"the result should be less than or equal to the datetimeoffset (.*)")]
  [Then(@"the result should be less than or equal to the integer (.*)")]
  [Then(@"the result should be null")]
  [Then(@"the result should be of type (.*)")]
  [Then(@"the result should be true")]
  [Then(@"the result should contain")]
  [Then(@"the result should equal the context value (.*)")]
  [Then(@"the result should not be null")]
  [Then(@"the result should not equal the string ""(.*)""")]
   
    • Custom step argument transformations:
      • TimeSpan transformation converts to TimeSpan for the following free-text argument formats:
                  
        1 day, 1 hour, 1 minute, 1 second
5 days, 4 hours, 3 minutes, 2 seconds
5 days, 4 hours, 3 minutes
5 days, 3 minutes, 2 seconds
5 days, 4 hours, 2 seconds
4 hours, 3 minutes, 2 seconds
5 days, 4 hours
5 days, 3 minutes
5 days, 2 seconds
4 hours, 3 minutes
4 hours, 2 seconds
3 minutes, 2 seconds
5 days
4 hours
3 minutes
2 seconds
If you are a SpecFlow user, this is a must have!


Remark: Also check the other SpecFlow extensions they made; Endjin.SpecFlow.Composition and Endjin.SpecFlow.Owin.Hosting
Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more