A late report from our workshop last year. I stumbled across it again in my preparations for KWST (Kiwi Workshop on Software Testing) 2015. It was supposed to be published through our gracious sponsor, The Association for Software Testing (AST), but it never eventuated. So I thought I’d post it here. Better late than never.
So here goes….
For the fourth year in a row, Wellington (New Zealand) has successfully hosted the Kiwi Workshop on Software Testing. The two-day intensive testing workshop is one of the key drivers of the Context-Driven Testing (CDT) community Down Under.
In its beginnings, the aim was to give the experienced and senior community members a platform to drive innovation and exchange ideas. The impact of KWST in the community over these past years has had far reaching effects in New Zealand as well as Australia.
Workshops, conferences, and magazines have emerged since, which have lifted the game right across the board. KWST 2014 was specifically aimed at involving new faces in the community and not drawing as much on the established KWST crowd.
The topic this year was:
“How to speed up testing? – and why we shouldn’t”
This post is the third in our series on metrics in software testing. So far we’ve looked at residual risk (here), coverage (here), and this time it’s defect density.
The following is taken from the post that sparked the series…
3. Defect density is another metric that matters. It translates into where are the defects and how many are there? Identify each of the parts of the solution that you care about (front end, back end, service layer), or user type, or functional area, or scenario then make sure everyone know these identifiers and uses them whenever a defect is raised.
From a bird’s eye view the idea of defect density is a good one, but as testers we know that the devil is in the detail. It could be seen as a powerful risk evaluation technique to be able to know where the defects are located in a particular product. However, the value stops with this illusion. It is about as useful as asking where the developer hid all the defects.
In the spirit of gamification, Sydney Testers Meetup have definitely levelled-up. Significant advancements in structure and commitment have seen a robust
platform to operate the meeting format from.
Last Wednesday’s evening on Test Automation, Vibe Hotel Sydney CBD, was a very successful event.
Posted in Communities, Event, Test Automation
- Tagged Automation, communities, Let's Test, Meetup, Richard, Robinson, SCRIMPS-STD, Sydney Testers, Test Automation
The Association for Software Testing (AST) has this year funded large parts of KWST. So I wrote a report for them on what we did. I thought I’d share here too.
The Third Kiwi Workshop on Software Testing
by Oliver Erlewein
It’s winter in the southern hemisphere: The weather is getting cold and windy, and people are staying inside. But not all! Testers from all over Australia and New Zealand were flocking to one of the testing highlights of the year, the two day long Kiwi Workshop on Software Testing (KWST) held in Wellington, New Zealand.
This is the third time round and we’re going from strength to strength. This time 19 people were sharing their experiences – LAWST style – about “Lighting the way; Educating others and ourselves about software testing”.
Posted in Context Driven Testing, Event
- Tagged Aaron, Brian, CDT, communities, education, event, experience report, KWST, Oliver, Richard, Test leaders, Thought leadership
Let’s Test 2013 had a lot to live up to. I had heard so much about the previous conference, with people confidently saying that “Let’s Test is the Best Testing Conference in the World”. After going this year, I have to say, I 100% agree. Let me explain why I had the testing time of my life.
Posted in Communities, Event
- Tagged context-driven, facilitating, James Bach, Letstest, letstestoz, miagi-do, Michael Bolton, paul holland, Richard, test lab
My first formal presentation was tonight. It was a 2 hour talk with a discussion on the topic of ‘Demise of Test Scripts; Rise of Test Ideas’. It was at Atlasssian headquarters, Sydney.
Here is my experience report.
The Kiwi Workshop on Software Testing is a dream come true for New Zealand testers. It represents an opportunity for the thought leaders and community-driven testers to gather and share war stories. But it’s so much more than that. James Bach has attended for the 2nd year running which adds the momentum and rich test ideas that gets the minds of the participants revved up.
KWST lets us debate on friendly turf. Through using turn-taking coloured cards, heated testing topics can be fully explored, and talking turns can be controlled. As a facilitator, I thoroughly enjoyed watching heated discussions progress until the deep issues came to the surface.
Posted in Context Driven Testing, Event
- Tagged bbst, James Bach, KWST, kwst2, peer conference, rapid software testing, Richard, richrichnz, richrichrichrichrich, richrob79, rst
I spoke with a tester recently about capturing tests to be reused. I had a discussion with them on what they thought about the process. I will outline their task, what they were supposed to do, what they did, and the questions and comments that came from the discussion afterwards. Some valuable lessons and insight were uncovered.
Hello all to this new testing Blog of Aaron Hodder, Brian Osman, Oliver Erlewein and Richard Robinson. Some of us have our own testing blogs but the thought here is that, since we think along the same lines and together seem to pack more testing-punch, it is natural for us to meld our minds into one blog. Our hope it is that you will be the main beneficiary of this and we can help you reflect and learn new things as you progress in your testing career and the profession in general.
You will also see our twitter streams at the bottom and rhs of this blog so follow us to stay on top of things.
Since STANZ 2011 is on next week in Wellington we’re rushing a bit to get this blog out the door and start reflecting on what’s happening in the scene. So please check back regularly to see new stuff.