Archive for September 2015

Week 40, year 2015

  • C# and F# approaches to illegal state - You have probably heard of such phrase as “make illegal states unrepresentable” already. Basically, it stands for using some set of techniques for dealing with illegal states in your domain model. In this post, we’ll look at how C# and F# allow us to handle them. [Enterprise Craftsmanship]
Permalink | From 28 September 2015 to 04 October 2015 | Last updated on: Mon, 7 Jun 2021 09:11:15 GMT

Week 39, year 2015

  • Coded UI vs White - Today, we’ll look at Coded UI and White automation frameworks in terms of building an automated UI test suite for a WPF application. We are going to compare them from different points of view, such as performance, the ease of getting started and maintainability. You will see which of these two frameworks suits what kind of projects and how to make a decision in your particular circumstances. [Enterprise Craftsmanship]
  • Automating UI Tests for WPF Applications Pluralsight course - My first course for Pluralsight went live! In it, I talk about techniques and best practices for building a UI test suite for WPF applications. During the course, I go through such topics as: Why we should invest our time into UI tests in the first place. Different types of manual tests and which of them we can automate. The comparison of Coded UI from Microsoft and open source White from TestStack. [Enterprise Craftsmanship]
Permalink | From 21 September 2015 to 27 September 2015 | Last updated on: Mon, 7 Jun 2021 09:11:15 GMT

Week 38, year 2015

  • Fail Fast principle - The fail fast principle is underlying for many other software development practices. It comes out so often that it’s hard to cover all its appearances in a single article. Nevertheless, that is exactly what I’m going to do here :) [Enterprise Craftsmanship]
Permalink | From 14 September 2015 to 20 September 2015 | Last updated on: Mon, 7 Jun 2021 09:11:15 GMT

Week 37, year 2015

  • DRY revisited - Another principle we should follow when building a software project is the DRY principle. The abbreviation stands for Don’t Repeat Yourself. While it seems pretty straightforward and intuitive, this principle is more than meets the eye. Let’s see how it is so. [Enterprise Craftsmanship]
Permalink | From 07 September 2015 to 13 September 2015 | Last updated on: Mon, 7 Jun 2021 09:11:15 GMT