Folks ThoughtWorks is organizing a Quality Analyst meet on 2nd September 2010. Hope you guys are aware of the event. Do register and attend in case you are looking for some good discussion and talks on Testing.
We are delighted to invite you to a Quality Analyst Community Meet at our Koramangala office in Bangalore. This conference is a platform for our peers in the software testing industry to strengthen the QA community by sharing and learning new practices and ideas.
'QAConf' offers a unique opportunity to interact with people who are equally passionate about software testing and continuously strive to better the art. The format of 'QAConf' is scheduled such that each speaker will have 25 minutes to present followed by a couple of minutes of Q & A with participants. The topics covered in this workshop will be appropriate for any level of testing experience. Please note that this is a FREE to attend event. You can either register as a speaker or register as an attendee.
Who Should Attend
Quality analysts and testing aficionados who want to interact with the testing community. This is also relevant to those interested in the nuances of test automation and how testing works in an Agile environment. There is something for everyone participating in this event:
As a Speaker, you get to share your knowledge and gain recognition as a subject expert.
As an Attendee, you get to connect with like-minded peers & gain insight from industry practitioners.
The list of speakers will be published on 16th August, 2010
How to Register
Registration is free.
Thursday, Sept 2, 2010
5:30 pm to 8:30 pm
ACR Mansion, 2nd Floor,
147/F, 8th Main Rd
3rd Block, Koramangala
Bangalore - 560 034
About BizTech Live
BizTech Live is a seminar series for technologists, sponsored by ThoughtWorks. This is a forum for technophiles to exchange ideas, collaborate and network with like-minded people in the technology community.
As a QA I have been logging bugs since 5 years. But what do we do with that ? A typical flow: If this is the only thing we need to do then why taking so much of pain to have a defect tracking system . To log a standard bug (Standard Bug= Broken Functionality), we need to write steps to reproduce, pre-requisites (if any), expected result, actual result, priority, severity, snapshot (if any), Test environment details and finally save it. This takes around roughly 3-5 minutes to log a bug. To say truth, I have never seen any report coming out of defect tracking system which is of use in analyzing the pattern of bug or finding out any trend in them. All I have seen apart from tracking usage, is the summary of bugs with count based on Priority and Severity. Is that the only purpose of Defect Tracking System? If that is the case then why not use a Google spreadsheet rather then investing money of the company and time of QA in a bug logging system. I am sure if we mine the data which i
I came back from the background of writing test cases which were categorized in either Positive or Negative test cases. Positive test cases were business flows which may or may not give any result but they will certainly not give any exception or error. Negative test cases are those test cases which were bound to result into some exception or better expressed as error causing scenarios. Then those positive test cases were prioritized as High/Medium/Low . Finally it used to result in quite a comprehensive test case document. Then it will go through the process of review and few more updates or change of priority etc. Certainly it is a tedious process. Here in ThoughtWorks I got introduced to different way of categorizing test cases called “ Happy/Sad/Bad ”. A test case which results you in a positive result is a Happy path , for e.g. entering proper username and password on login page. A test case which yields no result like entering invalid username and invalid password on a logi
Have we ever noticed how excited we are when we start anything? But it’s a sad fact that 70% of people abandon what they have started with so much energy and love. It could be as small as building a hobby or starting a pet project or even an activity or a side learning we started. “ Well begun is half done .” Aristotle did say this but we are judged for how we have finished something. You separate yourself fro m the masses when you choose to give that task a finish. The first quality is finishing off what you started and it helps develop mental stamina or willpower. It builds confidence and inculcates as a habit in a long run. You don’t need to sign up for the mammoth activity to build this habit, even finishing mundane day-to-day routine tasks will help. Diligence — the quality of working carefully and with a lot of effort Diligence is a quality that almost never will get unnoticed. It’s one of the underlying traits of great works or success. The key to mediocrity on the o