in particular, my take on it is that the tools and processes should *support* the individuals and their interactions
Ilja Preuss wrote:In particular, my take on it is that the tools and processes should *support* the individuals and their interactions (instead of the other way around, which too often is the case in non-Agile environments).
Mads jacobsen wrote:
But often TDD is described as a methodology itself
Jeff Langr wrote:
Can you be more specific? Of course the tools and processes should support individuals and interactions, but I think a good question might be (and maybe what the OP was really asking), how specifically is testing an activity that is better focused around "individuals and interactions?"
Ilja Preuss wrote:A contrived example: In a project, the test manager sees that a specific tool, let's call it X, has improved tester's performance significantly. He thinks that it would make sense to use that same tool in other projects, too.
One way to do that would be to have the testing tool made mandatory in the companies' testing process. Another to organize a forum where testers can exchange their experiences with different tools and techniques and let each team decide for itself what to do with that information.
Jeff Langr wrote:
And another: Freeing up time for exploratory testing (once we've automated what can be automated) is a move away from dependence on tools, and one that emphasizes the expertise that an experienced tester brings to the team.
Mads jacobsen wrote:Hi
The agile Manifesto clearly states "Individuals and interactions over processes and tools" but usually testing is all about process and tools.
Does Agile Testing discuss this in any way?
Thanks in advance
Those who dance are thought mad by those who hear not the music. This tiny ad plays the bagpipes:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton