This is a guest blog post by Carey Fletcher, a Tet Manager with QualIT, and has over 10 years of testing experience working in various sectors with her expertise in software test processes and practices. Carey contacted Janet to get feedback on how she had implemented her process to see if she was on the right track.
We’re often asked whether our books are suitable for people who don’t yet know anything about testing. Another question we sometimes get is along the lines of “Why don’t your books contain in-depth explanations of systems thinking, coverage, oracles, model-based testing, performance testing, <fill in your favorite testing technique here>?” Agile Testing and More Agile […]
Thanks for being patient with us – it’s been a long delay, we know since we asked for the communities’ input. Life got in the way and we had so many good choices and we didn’t completely agree on any one, but we finally made a decision and combined ideas from three different suggestions. … […]
A successful whole-team approach to agile testing means lots of conversations about potential upcoming features. These might begin with a project inception, a design critique, a pre-iteration or iteration planning meeting. We need to learn so much about each feature if we’re going to successfully deliver what the business, customer and users want and need. […]
Our definition of “agile testing” Thanks everyone for your input on our original definition. We’ve changed it slightly based on new conversations and comments. Definition of agile testing: (by Lisa Crispin and Janet Gregory) Collaborative testing practices that occur continuously, from inception to delivery and beyond, supporting frequent delivery of value for our customers. Testing […]