Welcome to Seapine’s Perspectives on Testing. Every week I’m going to look at articles, blog posts, tweets, and other testing and quality content, and provide some perspective on the news or commentary. Enjoy, and I look forward to hearing your feedback.
Agile Point of View
What happens when a team spends the planning meeting focusing on the question of, “What are we trying to do?” as opposed to, “What should we be doing?” Mark Levison tells us that it’s a matter of creating acceptance criteria
Nenu Tech asks whether Agile is a good approach for mobile app development
It’s hard to dispute Nick Petri’s contention that Scrum is better than getting slapped
, but his point about its effect on productivity is a good one.
Fiona Charles tells us what happens when we let our test documents direct and drive our work, rather than serve us. She calls it the tyranny of form over substance
Peter Morgan says there is no such thing as an unreproducible bug
. If we can’t reproduce a bug, it’s because we don’t have sufficient detail of the circumstances that cause it.
The Ministry of Testing has created a list of resources for exploratory testing
. It includes articles, videos, tools, books, and blogs, and looks like it’s exceptionally comprehensive.
This is probably a case of preaching to the choir, but WireHarbor Security writes about the high cost of poor quality software
. I think most of us are aware of this, but it’s good to see others thinking in the same way.
What happens when we call testing quality assurance? Ian Pestelos says it could lead to an institutional misunderstanding of the role of testing
. Maria Kedemo makes a similar point here
, reclaiming the software testing flag.
Keith Klain says that the first thing we can do to improve the state of our testing team is to define our test management values
What happens when you meet someone with diametrically opposed ways of practicing testing, yet those practices seem to pan out pretty well? Rob Lambert says that this is where true innovation and learning
Colleague Jeff Amfahr was interviewed for an SD Times article on the changing paradigms of requirements management
Why do programmers code better at night? It’s because they are on the maker’s schedule
, not the manager’s schedule, says Swizec Teller.