WeekNight Testing is Back


Inspiration?
The magic that transpired at Skills Matter on 23-Mar-2011 when WeekNightTesting went LIVE with Markus Gaertner facilitating from Hamburg, LisaCrispin from San Francisco and Mike and I from London has inspired us to take WeekNight Testing out of the chat app to LIVE testing sessions.

How do we plan to do it?
Testers meet at a common location in the evening at around 17:45 UK Time with their laptops and energy to test, question, learn, discuss about testing.

 At 18:00 the test session facilitator announces a testing challenge that is time boxed for an hour. Testers have the freedom to pair up with other testers or work on their own to meet the challenge. Testers can also use any test tools, strategies, and ideas to accomplish the challenge.

At the end of the hour we take a 5 min break and jump into a discussion session (de-briefing) for the next hour to share our test ideas, assumptions, tools used, strategy chosen to meet the challenge.

When & Where is the first event?
The first LIVE test session of the year is scheduled on 10th of April 2013 at SQS. I thank SQS a lot for their support and sponsorship of the first event.

Please Note: Since this is a LIVE event there are only 25 spots up for grabs. So don’t miss out. 

How do I register?
All details here-> http://weekendtesting.com/wntesting

Next Steps?
We want to run more such test sessions in the year frequently. So if any of you are interested in sponsoring, facilitating or just testing. Please email Tony or me.



Comments

Wardboy For Hospital In Pune said…
Hi
nice Concept sounds Very Peaceful.I would like to give a try for this Concept In My Work.
April 26, 2013 at 12:55 PM
Anonymous said…
Where are you nowadays! Its nearly a year that you have blogged!

Your Blog Reader!
February 12, 2014 at 4:08 PM
Sharath Byregowda said…
Thanks for the comment Anonymous Blog Reader.

I was off track for a while but stay tuned for a lot of updates.

February 16, 2014 at 2:44 AM
Post a Comment

Popular posts from this blog

Exploratory testing, Session based testing, Scripted testing…concertedly

In my last assignment a mix of exploratory, session based and scripted testing helped won an award, appreciation by managers & stake holders at our organization. The quotes from our award certificate “ QA team has come up with some intelligent testing techniques to validate the product. The customer test team was not able to find even a single critical bug after delivery ” Though the award was a small one in terms of the award categories our organization have, it meant a lot to me and the team, because this was the first time the team used exploratory approach. The assignment was not pure exploratory or session based, in fact it was supposed to be scripted, but a mix of all three exploratory, session based and scripted testing helped us learn, enjoy, and meet our mission. The assignment started off with developing test cases. We wrote test cases based on the initial requirement document provided. We did come up with a large number of test cases, of which most were re-written, some
Read more

What do you do when you find a bug?

What do you do when you find a bug? Hold on do not answer it right now. Let me first set the context. You are part of an agile team. The developers sit opposite to you. You are testing a feature in a session. You are time bound and have the good habit of capturing notes when you test. When you now find a bug what do you do? Assuming that you have taken enough notes you go on to write a good bug description and may capture a screen shot, video of the bug and continue with your session. At the end of the session do you Open the defect tracking tool (wait for it to load), enter all the fields for a bug, upload necessary evidence and have the tool share the defects with your dev team? Or Open the defect tracking tool (wait for it to load), enter all fields for a bug, upload necessary evidence and then compose an email to the dev team with the bug id’s/descriptions? Or Walk to the developer share your notes; reproduce it if required, work together to identify the problem? I work in
Read more

Regression Checks + Regression testing = Regression testing?!

One of the questions I find hard to answer when I use exploratory test techniques in my project is,”How do you run regression tests? How do you prioritise them? Do you automate them? Do you document regression test cases?” And then a bunch of questions follow. Let me define the context. I work closely with developers; we use either Scrum or Kanban - which ever best suits our project, product owner, business. We do not believe in individual metrics, blame games, stringent processes, and heavy documentation. All we care about is to deliver high quality software. This does not mean that there is no process, metrics or documentation. We have them all, but they are there to meet our needs and to help those who will come onboard to support/maintain the software. Regression Checks At the start of a story, testers pair up with developers to develop feature files using SpecFlow. Some call it Acceptance Test Driven Development and others Behaviour Driven Development [I am yet to figure out the d
Read more