Comments on: TDD: Test DRYness

By: Continuous Testing with Selenium and JBehave using Page Objects « MikeCI Blog

Wed, 10 Nov 2010 13:23:23 +0000

[...] means that if the UI changes, the fixes need only be applied in one place. This means we get our DRY testing mojo back after our experiences with copy ‘n’ pasted Selenese markup. To make things even [...]

By: TDD: Expressive test names - Mark Needham - CodeBetter.Com - Stuff you need to Code Better!

Sat, 20 Mar 2010 01:03:42 +0000

[...] the end of a post I wrote just over a year ago I suggested that I wasn't really bothered about test names anymore because I could learn what I [...]

By: TDD: Expressive test names at Mark Needham

TDD: Expressive test names at Mark Needham — Fri, 19 Mar 2010 18:09:33 +0000

[...] the end of a post I wrote just over a year ago I suggested that I wasn't really bothered about test names anymore because I could learn what I [...]

By: TDD: Balancing DRYness and Readability at Mark Needham

TDD: Balancing DRYness and Readability at Mark Needham — Sun, 12 Apr 2009 14:55:54 +0000

[...] wrote previously about creating DRY tests and after some conversations with my colleagues recently about the balance between reducing [...]

By: Dew Drop - January 30, 2009 | Alvin Ashcraft's Morning Dew

Dew Drop - January 30, 2009 | Alvin Ashcraft's Morning Dew — Fri, 30 Jan 2009 16:45:44 +0000

[...] TDD: Test DRYness (Mark Needham) [...]

By: Reflective Perspective - Chris Alcock » The Morning Brew #276

Reflective Perspective - Chris Alcock » The Morning Brew #276 — Fri, 30 Jan 2009 08:32:35 +0000

[...] TDD: Test DRYness – Mark Needham talks about the Don’t Repeat Yourself (DRY) principle in unit tests, and highlights a few techniques you can use to avoid repetition. [...]