SpecFlow Tips: Collect more information on error (part 2)
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.
BDD Addict Newsletter April 2016
by Gáspár on May 9, 2016
Dear BDD Addicts, April is the month when trees blossom, bees whir and BDD addicts come together in London in order to spend two days with talking about BDD at CukeUp! conference. Is there a need for a BDD Addict Newsletter in April at all? Of course, there is!
SpecFlow Tips: Collect more information on error (part 1)
by Gáspár on April 1, 2016
When BDD scenarios are turned into executable automated tests, they usually automate the application together with its dependencies (e.g. end-to-end with browser automation or headless with controller-layer automation). This ensures that the application works as a whole, but unfortunately it also makes the analysis of a failing test harder. So many things can go wrong, […]
BDD Addict Newsletter March 2016
by Gáspár on March 7, 2016
Dear BDD Addicts, Welcome to the second BDD Addict newsletter. My plan is to collect interesting posts, articles and events about behavior driven development, SpecFlow, Cucumber moreover also test automation and agile testing. I’m following many channels, but surely not all. So if you have seen something that fed your addiction, just send me the […]