tag:blogger.com,1999:blog-2217179243762425644.post8491300038610950587..comments2024-03-29T15:35:10.301+13:00Comments on TestSheepNZ: Learning to use exploratory testing in your organisation ...TestSheephttp://www.blogger.com/profile/05047308702049182716noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-2217179243762425644.post-89793362156860418392014-03-02T16:44:25.317+13:002014-03-02T16:44:25.317+13:00Hey Srinivas - thanks for your comments.
Yes inde...Hey Srinivas - thanks for your comments.<br /><br />Yes indeed - when we talk about setting up test sessions or charters, this of course can become it's own spin off topic - both Elisabeth Hendricksons Explore It and James Bachs RST spend more time going into this, and indeed I may devote a future topic to it.<br /><br />To me the purpose of planning a session or charter is to help plan out at a high level those areas which you want to cover. Now in a way there are many ways to do this, but the most important thing to me is this - am I getting input in this from other testers and non-testers? If not, then I have to say however clever my approach is, I'm missing something fundamentally important. My system for organising this is only as good as the input I get for others.<br /><br />So a session plan can be pretty much anything - but it needs to be whatever is most useful to you and your team, esp for getting feedback. In my current team, with us being agile, our sessions are derived from user stories and include areas of functionality which we think could be affected etc. We start from the user stories and mindmap our test ideas from there.<br /><br />I've used a different approach of collecting system behaviour, and turned them into sessions "registration", "buying", "account amendment", "customer browsing", "helpdesk admin" for instance as broad banners for what our product does etc.TestSheephttps://www.blogger.com/profile/05047308702049182716noreply@blogger.comtag:blogger.com,1999:blog-2217179243762425644.post-27132272261623381702014-03-01T17:28:13.297+13:002014-03-01T17:28:13.297+13:00Test Scripts is usually referred as Test Cases rig...Test Scripts is usually referred as Test Cases right? - But which is the one to call for Front end - Functional testing?<br /><br />I am confused with the definition: Test Scenarios with yours.<br /><br />test session: An uninterrupted period of time spent in executing tests. In exploratory testing, each test session is focused on a charter, but testers can also explore new opportunities or issues during a session. The tester creates and executes test cases on the fly and records their progress. See also exploratory testing.<br /><br />"Typo Error / Cosmetic Error" - which should be used <br />"usre driven - should be user driven"<br /><br />Thanks, qTestExplorer - will try this one.Srinivas Kadiyalahttps://www.blogger.com/profile/04702798081842391077noreply@blogger.comtag:blogger.com,1999:blog-2217179243762425644.post-57393947304656942492014-02-27T22:51:40.096+13:002014-02-27T22:51:40.096+13:00Cheers Kim!
And thanks for promoting through Twit...Cheers Kim!<br /><br />And thanks for promoting through Twitter.TestSheephttps://www.blogger.com/profile/05047308702049182716noreply@blogger.comtag:blogger.com,1999:blog-2217179243762425644.post-71186677756868763672014-02-27T07:01:30.026+13:002014-02-27T07:01:30.026+13:00This just became recommended reading for anyone wo...This just became recommended reading for anyone working on my team.<br />It will tell me a lot based on:<br />- whether they raise at least one point for objection or dicsussion<br />- whether they look for recording tools to start using<br />- whether they look up more information on exploratory testing, oracles, tools, RST, etc<br />- whether they read all the way to the end :-)<br /><br />Great work.<br /><br />Cheers,<br />KimAnonymousnoreply@blogger.com