Using SpecFlow with a Coded UI API is already a well-worn path, according to the guys from Specflow.org. Yet after reading their post I was frustrated by how much C# code is involved; a tester shouldn’t be expected to do all of that. I’d like to propose this code sample […]
A big part of the testing done on Warewolf so far has been done using manual testing for the Studio User Interface and functional tests using SpecFlow. We use unit testing to handle the business layer of the system as both cannot test the UI (see Unit Testing vs UI […]
For those not familiar with using SpecFlow, it is an open source .Net tool which is based on the Gherkin syntax using plain English text format. It is used to express user stories and their expectations in a behavior-driven development (BDD) environment. Even though SpecFlow was inspired by the Cucumber framework, […]
As I mentioned in Part 2 of this series, I would write about how we are using SpecFlow for the Studio rewrite. Although this post does not have anything to do with Windows Workflow Foundation, it is the final part of the “Testing Custom WF Activity using SpecFlow for Warewolf series” […]
In a previous blog post we looked at testing custom WF activities using SpecFlow. In this post we will look at using SpecFlow to test the composition of custom activities. So maybe you are asking, why is this important?
Warewolf currently makes use of the Windows Workflow Foundation (WF) engine to execute services. We make use of custom activities for all the current tool connectors. In some cases these make use of built-in WF activities. During the development of Warewolf we needed to find a way for a non-developer […]