Testing Explorer

If you can’t Fly,then Run, If you can’t Run,then Walk.
If you can’t Walk,then Crawl.But whatever you do,Keep Moving.
-Martin Luther King,Jr.

RSS
  • Home
  • About Me
  • Contact

Weekend Testing Musings - WT#24 Experience Report

Wednesday, February 10, 2010 by Jassi | 0 comments
Apart from Testing ,what do James Bach, Dr. Cem Kaner, Pradeep Soundararajan, Dr Meeta Prakash have in Common? Weekend Testing.

Date: 06- Feb-2010

Timing: 3 pm – 5pm

Mission: A Group discussion about Testing, Traps in Testing, Requirements, Skills

Guest Participant: Dr Meeta Prakash.

Coordinated By : Parimala Shankaraiah , Ajay Balamurugadas

Participants:
Ajay,Arun, Dhara ,Krishnaveni,Indra,Jaswinder,Last Samurai,Nitesh,Pari,Suman,Sunil,Ramakrishna,Rakshith


The Session started off with the question “What is Testing”?
Discussion continued on Topics like Traps in testing, Traceability ,Requirements and ended with important Skills needed in Testing.
Dr. Meeta Prakash very patiently replied to each of our queries and solved our doubts giving us some important leassons.She even Shared a link to understand Tree Diagrams which can be used to track traceability .

Overall the session was quite interesting and productive.


Major Discussion Highlights to remember:

What is Testing?
Testing is technical investigation/evaluation of the product to provide quality related information to the respective stakeholders
It is no different as applied to software from other domains &
the 2 aspects of verification and validation become the key identifiers while testing

What are the major Traps in Testing?
1. Not being able to ask the right questions
2. Aiming for a Quantity or number instead of quality of bugs.

Important Skills Needed for a Tester:

1.) Asking the right questions using the 3 columns approach
• Write the question
• Write key requirement coming out of it
• Track dependencies and outcomes.

2.) Objectivity in approach
• Objectivity means that you should not have a negative approach while testing. You should be able to see through the rationale behind each failure you observe
• To report each and every failure either as a defect or as an
• Not only just thinking of negative test cases but also be considering what way the software modularity flows and how can it be broken


The Entire Chat Transcript can be found here

Related Links:
WT 24 : Testers’ Day Out With Dr. Meeta Prakash

Dr.Meeta Prakash, Traps in Testing, Tree Diagram, Weekend Testing, WT#24

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Subscribe To

Posts
Atom
Posts
Comments
Atom
Comments

Blog Archive

  • ►  2021 (1)
    • ►  November 2021 (1)
  • ►  2011 (1)
    • ►  January 2011 (1)
  • ▼  2010 (7)
    • ►  April 2010 (2)
    • ▼  February 2010 (4)
      • WT26 - Do you have your Budget?
      • European weekend Testing–05 # EWT05
      • European Weekend Testing - 04 #EWT04
      • Weekend Testing Musings - WT#24 Experience Report
    • ►  January 2010 (1)
  • ►  2009 (3)
    • ►  October 2009 (1)
    • ►  September 2009 (2)

Labels

50th (1) Andy Glover (1) Bug Report (1) BugRepository (1) BWT (1) datamatics (1) Doug Hoffman (1) Dr Cem Kaner (1) Dr.Meeta Prakash (1) European (1) EWT (2) EWT-04 (1) EWT05 (1) Fireshot (1) first post (1) Heuristics (1) irctc (1) James Bach (1) knowTime (1) Maik (1) Matt (1) Mike Kelly (1) Navigation (1) Navratnas (1) Quick Testing (1) railticketonline (1) Report (1) Satisfice (1) Tips (1) Traps in Testing (1) Tree Diagram (1) Typewith.me (1) URL Shortener (1) Virtual Magnifying Glass (1) Weekend Testing (5) WT (1) WT#24 (1)

Blog's I Recommend

  • Ajay's Blog
  • Cartoon Tester
  • James Bach’s Blog
  • Markus Gartner's Blog
  • Matt Huesser's Blog
  • Michael Bolton's Blog
  • Pari's Blog
  • Pradeep's Blog
  • Scott's blog
  • Shrini's Blog
  • The Craft Of Software

Daily Wisdom

Copyright © 2010 Testing Explorer Wordpress Theme Blogger Template Credits For