The monthly dose for BDD addicts… In June #bdd, #specflow and #cucumber stories from Gojko Adzic, Kent Beck, Håkan Forss, Michael Whelan & Gaspar Nagy.
BDD Addict Newsletter June 2016
by Gáspár on July 6, 2016
by Gáspár on July 6, 2016
The monthly dose for BDD addicts… In June #bdd, #specflow and #cucumber stories from Gojko Adzic, Kent Beck, Håkan Forss, Michael Whelan & Gaspar Nagy.
by Gáspár on May 31, 2016
The monthly dose for BDD addicts… In May #bdd, #specflow and #cucumber stories from Reed Gusmus, Roberto Lo Giacco, Arado Oy, Tomasz Pluskiewicz & Gaspar Nagy.
by Gáspár on May 13, 2016
In the first part of this article I described why it is important to provide more information on errors and how you can collect useful artifacts (screenshots, log files, etc.) in an [AfterScenario] hook. In this part I would like to explain how to write more informative assertions.
by Gáspár on May 11, 2016
Many teams who use SpecFlow setup their continuous integration environment with Microsoft Team Foundation Server (TFS) or its cloud based service, the Visual Studio Team Services (VSTS, fka VSO). TFS/VSTS has an improved build system, where it is much easier to setup and customize builds. Regardless of the fact, which unit test provider you use for SpecFlow, it is super easy to setup a build to run your BDD scenarios, because all the major unit test frameworks provide the necessary adapter for it (this is the same adapter that you need to run the tests from the Visual Studio Test Explorer Window).
Since the infrastructure is relatively new and very generic, it is sometimes hard to find information on particular questions. For SpecFlow users one of the most typical question is, how to run only specific scenarios (marked with a tag) in a TFS/VSTS build.
by Gáspár on May 9, 2016