Issues working with large legacy automation test suites and how (we think) we got it right the next time

“The automation tests are passing at around 80% so I think we’re good to release”

We’ve heard this expression before and it doesn’t bode well. We release code into the production environment and within a few days a new defect is reported.

“How did this get missed?”¬†asks the editor.

Continue reading “Issues working with large legacy automation test suites and how (we think) we got it right the next time”

The One Day Ideas Splurge

We have recently experimented with some dev-first approaches for some distinctly different scenarios

  • riffing on a specific theme; generating and exploring lots of ideas quickly
  • starting a tech-architecture-heavy project

and were very happy with the outcomes.

tl;dr The essence of both approaches is

  • get the core group sitting in the same room for a day (Co-location is great. Who knew?)
  • dump all possibly relevant information into the mix at the start
  • let the developers have a play
  • see what happens

What follows in this post is a more detailed look at the approach we took for …

Riffing on a specific theme; generating and exploring lots of ideas quickly

Continue reading “The One Day Ideas Splurge”