We cherish our community

Samuel fixed an error in our documentation.

Sandro send us again a lot of contributions to SpecFlow

• https://github.com/SpecFlowOSS/SpecFlow/pull/2410
• https://github.com/SpecFlowOSS/SpecFlow/pull/2566
• https://github.com/SpecFlowOSS/SpecFlow/pull/2570
• https://github.com/SpecFlowOSS/SpecFlow/pull/2565
• https://github.com/SpecFlowOSS/SpecFlow/pull/2573

Mateusz collected a lot of material related to BDD

Yann added support for a Playwright feature to SpecFlow.Actions.Playwright.

Sven added new helper methods.

Abdallah tells us about their experience with SpecFlow

Kamil added WebKit support for our Playwright SpecFlow.Action

Screenshots from SpecFlow Masterclass by Gáspár Nagy.

https://twitter.com/rajputabhay017/status/1404435449070833675?s=20

https://twitter.com/rajputabhay017/status/1404447720358645762?s=20

https://twitter.com/rajputabhay017/status/1404450092753428481?s=20

https://twitter.com/rajputabhay017/status/1404787954510270471?s=20

https://twitter.com/rajputabhay017/status/1404806790777348100?s=20

https://twitter.com/rajputabhay017/status/1405156257313353729?s=20

https://twitter.com/rajputabhay017/status/1405169981176696832?s=20

https://twitter.com/rajputabhay017/status/1405173271578898432?s=20

https://twitter.com/rajputabhay017/status/1405175381225721859?s=20

https://twitter.com/rajputabhay017/status/1405176421601869824?s=20

Feature "Added Feature Tag called parallelize" from #746 is broken, and there is already an alternative to it. See #2409

• Remove the feature introduced in #746

The approach in #746 of opting in to parallelization doesn't align well with the unit test frameworks which provide opt out behaviour.

MSTest v2, NUnit, and XUnit each have a mechanism to opt out of parallelism for a test class.

Roland uses Gherkin scenarios to describe the functional specifications of his software and SpecFlow to automate these scenarios as tests. Usually there will be a couple of scenarios describing the happy path of the feature he is building but also some scenarios concerning failures. Depending on how the application code works, these failures are represented by exceptions. In this post he explains how he handles these exceptions.

Behavior Driven Development is one of the most commonly misunderstood techniques in DevOps, but it is also one of the key enablers of both an Agile culture and true continuous deployment. This talk will attempt to fill in the missing pieces on exactly what BDD is and how your teams can use it to increase communication, drive quality, and reduce waste. We will also connect the dots on why you need a test-first strategy to enable trunk-based development, continuous integration, and continuous deployment. If your business still struggles with monthly or quarterly big-batch releases, this talk will show you what your teams must do to evolve to the next stage of continuous delivery.

https://github.com/SpecFlowOSS/SpecFlow/pull/2389

https://github.com/SpecFlowOSS/SpecFlow-Examples/pull/68

Behaviour Driven Development (BDD) is a branch of Test Driven Development (TDD). BDD uses human-readable descriptions of software user requirements as the basis for software tests. BDD is the definition of a shared vocabulary between stakeholders, domain experts, and engineers.

https://github.com/SpecFlowOSS/SpecFlow/pull/2350

https://github.com/SpecFlowOSS/SpecFlow/pull/2366

https://github.com/SpecFlowOSS/SpecFlow/pull/2368

SpecFlow is an excellent Behavior-Driven Development test framework for .NET. Recently, SpecFlow released a new reporting tool called SpecFlow+ LivingDoc, which generates living documentation for features.

In this video I will show you how you can get started with behavior driven development or BDD in .NET. For this video I will be using SpecFlow to demonstrate the concept and the implementation but there are ther packages as well that can be used.

This will always put a [DeploymentItem] attribute on every feature class. Which has a side effect for users, that don't have deployment items yet. When using DeploymentItems, the output path is different as without any. It will switch to the TestResults folder from the output directory.

If your automation team is converting manual test cases to BDD without following principles, please watch this video.

Ein neues Software Projekt beginnt. Das Design der Architektur steht. Nun können die hoch motivierten Entwickler starten, ihre Fachbereiche mit Code zu füllen. Doch kommt es schon nach kurzer Zeit zu großen Problemen! Die Anwendung macht an unterschiedlichen Stellen alles andere als das, was gefordert wurde. Keiner kann am Ende sagen woran das liegt, jeder versucht seine Position zu verteidigen.

In this video, we will discuss Specflow Living Documentation with Analytics, Step level failure report and more cosmetic features introduced with the new update!