Last time we talked about the different mechanisms and practices we put in place in order to get us to working software, the main metric in agile delivery. We talked about how “working software” means not just that software is functional, it’s built to last. One of the most effective of these practices is code
Category Archives: Uncategorized
I’ve written a series of posts on integration testing with Spring on “Everyday Unit Testing”. You can find the following: Configurations – How configurations works in Spring (and Spring Boot), not just for integration tests Mocking – How to use different configurations for injecting mocks in integration tests Testing a REST API – How to
If you liked the Asserting on Not Null pattern, here comes the lazier version. Why do people write tests without asserts? Check it out.
Anti-patterns are just popping up on the Everyday Unit Testing site! This time it’s about asserting that a returned object is not null. Noisy. Check it out.
Time for a new anti-pattern. This time: Tests for data transformation. Check it out on Everyday Unit Testing .
Agile Testing Days is oodles of fun, as you know (and if not, why?) Apart from a tutorial, a lightning talk and a workshop, and a game I ran, I also read a poem at Cabaret Night. I’m a renaisance man, yeah (and so is my daughter who drew the ATD Horror Story Unicorn). Here
Wonderful time. Again. The Agile Testing Days guys are doing a wonderful job, creating a magical, friendly, family-like conference. Awesome job. I’ve done a tutorial, a workshop, a lightning talk, ran a story telling game, joined a powerpoint karaoke and, oh yes, wrote a poem. Here are the slides from the very funny, killer pony
The agile manifesto says we value working software. What is working software anyway? We can talk about software working in different contexts. First are the non-tangible parts (more working than software): Idea – The ideas for the product we’re going to build need to make sense and solve the our customer problem Design – We
When I first took on product management, I started learning techniques, like understanding the market, strategy, SWOT analysis. While I didn’t write “proper” user stories, I prioritized requirements, and was there for the team to describe scenarios, answer questions, update on news, test the application and give feedback. My time was split between doing “product management”
Great fun, and it requires 2 hours, not 1.5 hours. Here are the slides.