Everybody I’ve met that is new to Gherkin starts with an Imperative style of scenarios. The Imperative approach is simple and intuitive and reflects what manual testers do. But I hate the Imperative style with a passion. I favour a Declarative style of scenarios not least because a declarative style means I can test business rules. The UI is prone to change but the business rules tend to be more stable.
Continue reading
Tag Archives: flow
Developers don’t have time for code reviews and unit tests
The ticket moves to “Dev Done” but there are no unit tests and the code hasn’t been reviewed. When challenged the developer says “That’s because I don’t have time for that stuff”. If I hear that I want to know why they feel they don’t have time, then I give them the time.
Continue reading
Fluid Planning and Execution Creates Agility
Thought leaders in the US military are challenging traditional approaches to command and control. These military innovators are proposing a more fluid approach that allows simultaneous planning and execution. It is good to see they are catching up but as an Agile practitioner I already do fluid planning and execution.
Continue reading
Whose responsibility is testing anyway?
I have a painfully small manual test team, sometimes 1 tester per 15 developers. The answer to the obvious question “who tests?” is “mostly the developers”. Of course this only works if you’re doing extensive automated testing including Specification by Example with a tool such as Cucumber.
Continue reading