tag:blogger.com,1999:blog-5077189869336195827.post2343332308892066319..comments2023-09-25T04:46:47.467-04:00Comments on The expected result was 42. Now what was the test?: Breaking down the Agile Testing Quadrants (with an exploratory testing context)John Stevensonhttp://www.blogger.com/profile/05696297547425084869noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-5077189869336195827.post-22720674517187595142014-06-04T02:04:19.632-04:002014-06-04T02:04:19.632-04:00Hey Steve,
Firstly, thanks for the kind words in ...Hey Steve,<br /><br />Firstly, thanks for the kind words in the Epilogue - I’m glad I could help get your work finished :-)<br /><br />I like how you frame the post in relation to Exploratory Testing - ET occurring throughout each of the quads is a very important point to remember! <br /><br />I do have a couple of thoughts/questions though…<br /><br />Labels:<br /><br />You provide some great context around the different examples in each of the quadrants, but I don’t see any reference to why those examples are in a particular quad(e.g Scenarios in TR quad Q3)<br /><br />Is that a deliberate exclusion?<br /><br />I only ask because you have left the labels in the cropped images, making me think they offer some value.<br /><br />What do the think about the labels as they stand in Lisa & Janet’s version of the quadrant?<br /><br />Tools & Processes:<br /><br />You have specifically mentioned a couple of tools / processes in the post - namely Cucumber, Junit, Sprints. I feel like adding the disclaimer “other tools & processes are available” for those of us not using the tools & processes mentioned in the post :-)<br /><br />Good work providing an example of how a Tester can provide value at the unit test level (boundary / error conditions) - that is the trickiest conversation I have when explaining my approach to testing to Programmers (These aren’t the tests you’re looking for….)<br /><br />In the conclusion:<br /><br />“The testing role is about supporting the team and the business rather than a fixed role within a fixed stage of testing."<br /><br />When I read that statement, at the end of walking through the model which talks about "business facing" & "supporting the team", I see testing as residing solely in the TL quad 2, which is the opposite of what the rest of the post was saying.<br /><br />I’m guessing that’s not what you meant?<br /><br />Finally:<br /><br />“To succeed there needs to be a continuous integration/delivery system in place.”<br /><br />Do you believe that? Can you think of another scenario which would disprove the statement above?<br /><br />Once again, nice post John, thanks for sharing. I always enjoy dissecting a model in ways I’ve not done before. It’s great to see how other folks see the world!<br /><br />As always, I’m open to a Skype chat as well.<br /><br />Duncs Anonymoushttps://www.blogger.com/profile/13734686574367515881noreply@blogger.com