marcofolio.net - Archives (septembre 2016)
design, jquery, programming, webdevelopment, fun, php, html, css, javascript
Assuming my previous article got you conviced into writing your specifications in Gherkin, we can go on to the next step: The automation of these specifications. This article will show you how to automate your acceptence process using those specifications, speeding up your acceptence process as well as as making your regression tests for the UI-layer fully automated.
When it comes to continuous delivery (CD), automation is key. The automation of your specification will help a lot in the long run, speeding up your CD flow drastically.
Because I love C# and mobile, I'll show you how to automate these tests using SpecFlow (which is Cucumber for .NET) and a little bit of Xamarin.UITest (which makes it able to run on a phone).
This article is the second part about this subject and I'll post the next updates in the upcoming weeks. If you want to hear me speak about this subject, feel free to join my "Turn specs into high quality apps"-presentation at TechDaysNL 2016.
Test-driven development (TDD) has been a pretty decent standard in software development for the past years. Writing solid unit tests is something every professional developer should do. (Nightly) builds execute these tests all in order to validate the quality of your code. But for those of you that know the testing pyramid from Mike Cohn, will also know there are more tests than unit tests.
This article will show you the first step into Acceptance test-driven development (ATDD) to test the UI-layer of the application you're building. It might help you get your business requirements in focus to make sure that what you're building is right.
This article is the first part about this subject and I'll post the next updates in the upcoming weeks. If you want to hear me speak about this subject, feel free to join my "Turn specs into high quality apps"-presentation at TechDaysNL 2016.