We know that deadlines drive behavior. That’s why in scrum, and other agile methodologies, we timebox the development with those deadlines. They tell us: Focus on the important stuff, and make sure it’s done properly. Since they are good in essence, let’s see how we muck them up. Here’s the process. We prepare for the
Second part of the Leadership resoponsibilities for a better unit testing implementation on Everyday Unit Testing. Check it out. Also, don’t get too close to the cat, it’s on fire.
You’re probably looking at Cap there and asking: What is this post? Well, that’s the next post on Everyday Unit Testing about leadership’s role in the implementation. Check it out!
I was recently a judge at ISTC, the Israeli Testing Cup finals. So how does one judge testing? What makes some testers better than others? A few things to note about the competition, which differentiates the testing situation from regular work: The team is presented with a product to test that they know nothing about, apart
Last part of leading indicators on the implementation series, over at Everyday Unit Testing. This time it’s about something called TUBBF. Curious? You should be. Check it out.
New post in the series, and there’s another leading indicator post coming up. Check it out.
A new post on Everyday Unit Testing in the series on implementing unit testing as a new organization process. This time it’s the first part on metrics and leading indicators. Check it out.
A great time with great people at Let’s Test in Sweden. Here are the slides from the BDD workshop. More workshops are coming…
When I ask teams “Do you do continuous integration”, eight out of ten times I get “We have Jenkins”, or a similar tool. The other two don’t know what I’m talking about. Jenkins to CI is like JUnit to unit testing (which is, of course, the answer I get when I ask about unit testing). It’s
New post on Everyday Unit Testing. Started as a rant, and based on too many conversations I had. Does making members public a real danger? Check it out.