Summary: Your developers are already working feature-by-feature in iterations, but your testers are stuck with manual tests. How do you make the leap to agile testing when the nature of agile’s iterative releases challenges testers to test working segments of a product instead of the complete package? In this week’s column, Johanna Rothman explains that […]
A client recently asked me how many people should be on his agile team. “I have a two-person project here, and a 23-person project there. Do I want two teams, one of 2 and one of 23? Oh, and how many testers do I really need?” I can believe there’s a small and short project
I was shopping today, taking advantage of the summer sales. One of my favorite retailers offers petite sizes online, but almost nothing in the store. I go to the store to try the clothes on and then decide what to order online. I had a number of blice (blouses to those of you who are
I have a Stickyminds column up, Does Exploratory Testing Have A Place On Agile Teams? The column arose out of an email conversation I had with Jon Bach. Please leave comments there.
Michael Hunter, the Braidy Tester, and one of the smartest testers I know, interviewed me on his DDJ blog. To be honest, I emailed him and asked if he’d like to interview me 🙂 I had things to say about testing. The interview is here. You can’t leave comments there, so please leave them here.
Imagine this scenario: Your organization has moved to cross-functional, project-based teams, and you, once a developer, are now a project manager. You understand how to make development work, but testing is like a black box. Until now, you thought testing was something that other people—those in the testing group—did. Now you’re responsible for the testers’
I had the pleasure of speaking with two different colleagues today, both with the same dilemma. They are near the end of their projects. They don’t quite have enough time for one round of final testing–but if they’re lucky and the stars align, and they don’t find too many problems, they can still (maybe)
There are several questioning comments on my post Testing is Not a Service: What do I mean by testing and how do I reconcile my statement with the context-driven school of testing? Let me clarify what I mean by service first. The way the participants were discussing testing as a service, they meant a common
I taught a one-day workshop at StarEast yesterday with Esther. I was astonished at the number of test managers who think testing is a service. Effective testing is not a service. Effective testing is an integral part of development. When people–especially senior management–consider testing a service, there are inevitable consequences: Testers multitask between several
Guy in his We love Scrum at GigaSpaces, says something critical: […]we’ve been working in the past couple of months on upgrading our automated testing framework. I’ve been assigning five of my top engineers and architects on a project with the objective to provide the development team fast feedback and monitors on quality. Now