50th Anniversary Weekend Testing Blast
Monday, January 17, 2011 by Jassi |
5
comments
50th Anniversary WT Blast,it was great, it was fun, it was thought provoking.
Date: 8-Jan-2011.
Time: 4pm – 6 pm IST.
Mission: FireShot is a browser add-on which captures, edits, annotates, organizes, exports, uploads and prints screenshots of your web pages.
They are facing a problem with many issues being raised on their support page and most of them lack important information. Please work in pairs and go through the issues logged and add additional information to help the programmer. Please work in pairs and go through the issues logged and add additional information to help the programmer. We were asked to discuss our points using typewith.me
Links: Download Fireshot & Defect Forum Page
Notes: After the mission was announced, I was a bit nervous to work in pairs, as I have never worked in pairs was wondering if it will be a good idea, will I be able to amalgamate my views with my co-pairer (is there a word like this, no idea).Anyways, I paired with Maik Nogens and it turned out to be a right decision.
Strategy: We started off with the Skype chat but then moved on to have a Skype call, as it was easier to speak & work in co-ordination & it saved Time too :)
We first decided to work on Defects related to Chrome add-on Maik gave a random search to fetch a list of defects related to the Chrome add-on. When we started , we went through the first defect we had fetched randomly, we tried to reproduce it but it was working fine, we read all the discussion threads but no where it was posted if the defect was still open or closed.
So we moved on to another but it was the same, we were unable to reproduce, the defects we had picked we were simply unable to reproduce as the defects seemed to be fixed .We observed that there was no clear way to understand whether the defects were closed or still in progress. We jotted down our Observations in Typewith.me( it turned out to be only us using it anyways ).It turned out to be a really wonderful session , worth to be the 50th WT session.
Lessons Learned:
Our Bonus:And what more we could ask for we also received the 50th WT Badge too,I have inserted the Badge above,Thanks Del Dewar for such a wonderful suggestion.
Special Mention: Andy Glover,Many Thanks Andy for the wonderful 50th WT Badge.I'm lovin' it :)
Chat Transcript: You can find our Chat Transcript here
Related Posts: 50th WT session and „Pairing“ , WT50 – Fireshot – Support Issues
Date: 8-Jan-2011.
Time: 4pm – 6 pm IST.
Mission: FireShot is a browser add-on which captures, edits, annotates, organizes, exports, uploads and prints screenshots of your web pages.
They are facing a problem with many issues being raised on their support page and most of them lack important information. Please work in pairs and go through the issues logged and add additional information to help the programmer. Please work in pairs and go through the issues logged and add additional information to help the programmer. We were asked to discuss our points using typewith.me
Links: Download Fireshot & Defect Forum Page
Notes: After the mission was announced, I was a bit nervous to work in pairs, as I have never worked in pairs was wondering if it will be a good idea, will I be able to amalgamate my views with my co-pairer (is there a word like this, no idea).Anyways, I paired with Maik Nogens and it turned out to be a right decision.
Strategy: We started off with the Skype chat but then moved on to have a Skype call, as it was easier to speak & work in co-ordination & it saved Time too :)
We first decided to work on Defects related to Chrome add-on Maik gave a random search to fetch a list of defects related to the Chrome add-on. When we started , we went through the first defect we had fetched randomly, we tried to reproduce it but it was working fine, we read all the discussion threads but no where it was posted if the defect was still open or closed.
So we moved on to another but it was the same, we were unable to reproduce, the defects we had picked we were simply unable to reproduce as the defects seemed to be fixed .We observed that there was no clear way to understand whether the defects were closed or still in progress. We jotted down our Observations in Typewith.me( it turned out to be only us using it anyways ).It turned out to be a really wonderful session , worth to be the 50th WT session.
Lessons Learned:
- While going through the defects I realized how important it is to write a proper bug Report, as the discussion threads were a bit confusing to understand,
- It is always good to have a bug reporting tool.
- Write the Big reports as descriptively as possible, attach evidences in the form of Screen-prints, video recordings etc.
- It is important to know the status of the bug whether bug is still open /closed or rejected.
Our Bonus:And what more we could ask for we also received the 50th WT Badge too,I have inserted the Badge above,Thanks Del Dewar for such a wonderful suggestion.
Special Mention: Andy Glover,Many Thanks Andy for the wonderful 50th WT Badge.I'm lovin' it :)
Chat Transcript: You can find our Chat Transcript here
Related Posts: 50th WT session and „Pairing“ , WT50 – Fireshot – Support Issues
James Recommends....................
Monday, April 19, 2010 by Jassi |
7
comments
It was a mundane Monday morning in office & so to perk myself up, I just started browsing www.satisfice.com; I opened the People recommendations page which I had missed/skipped last time I was browsing the site. The Title of this page said James Recommends & I found a list of 15 names with a description about each of them.
James Bach had listed a few names which made me reminisce King Akbar & his 9 Jewels or Navratnas.I clicked on the name Mike Kelly & I was like wow!
Mike Kelly’s blog seems to be like a Treasure Island. The categories seemed so interesting & the posts very informative. I was drawn towards the categories Heuristics & I’M an idiot (yeah!!! Sounds familiar isn’t it).
Check out these gems!
Managing focus when doing exploratory testing
Christina (Tina) Zaza’s advice for all of us:
• block off time to test (1 to 2 hours), close out email and IM, and schedule a conference room if needed so people know you’re unavailable
• before you start, open up everything you think you’ll need to do your testing effectively: applications, databases, spreadsheets, tools, etc… — this way you won’t get distracted or slowed down mid testing
• prioritize your tests – she listed three methods she uses:
o faster tests (or quick tests) first
o higher risks tests (or tests more important to the business) first
o group features together to reduce context switching while testing
• don’t stop your testing once you’ve started to write up defects or to ask developers/analysts questions — note them while you test, and then do that after your session is completed
The Hoffman Heuristic: Why not try them all?
Mike Kelly narrates how a small but a very interesting assignment given by James Bach made him reminisce Doug Hoffman’s Heuristic. This heuristic is based on Doug Hoffman’s testing of a massively parallel system
The Pirate Heuristic
Which says , when you run out of ideas – steal someone else’s,Pretty Interesting,what do you say.
Quick Testing Tips update
Which brought me to Quick Testing Tips website.
Coming up with a heuristic
It mentions about the heuristic test strategy by James Bach,Test Reporting Heuristic MCOASTER
Simple tips for testing application navigation
Some simple test ideas that can be pulled from the article include:
* Can you navigate without having to mouseover icons to figure out what’s what? Is it easy to find the link to the home page (or other core areas of your site)?
* Is there a way to distinguish between internal and external links?
* Can you easily open links in the same tab and a new tab? If you open it in the same tab and click back, do you actually go back to where you were?
* Can a user easily tell where they are within the site or application?
The list is endless, I am still reading, why don’t you drop by & join me.
Cheers,
Jassi
James Bach had listed a few names which made me reminisce King Akbar & his 9 Jewels or Navratnas.I clicked on the name Mike Kelly & I was like wow!
Mike Kelly’s blog seems to be like a Treasure Island. The categories seemed so interesting & the posts very informative. I was drawn towards the categories Heuristics & I’M an idiot (yeah!!! Sounds familiar isn’t it).
Check out these gems!
Managing focus when doing exploratory testing
Christina (Tina) Zaza’s advice for all of us:
• block off time to test (1 to 2 hours), close out email and IM, and schedule a conference room if needed so people know you’re unavailable
• before you start, open up everything you think you’ll need to do your testing effectively: applications, databases, spreadsheets, tools, etc… — this way you won’t get distracted or slowed down mid testing
• prioritize your tests – she listed three methods she uses:
o faster tests (or quick tests) first
o higher risks tests (or tests more important to the business) first
o group features together to reduce context switching while testing
• don’t stop your testing once you’ve started to write up defects or to ask developers/analysts questions — note them while you test, and then do that after your session is completed
The Hoffman Heuristic: Why not try them all?
Mike Kelly narrates how a small but a very interesting assignment given by James Bach made him reminisce Doug Hoffman’s Heuristic. This heuristic is based on Doug Hoffman’s testing of a massively parallel system
The Pirate Heuristic
Which says , when you run out of ideas – steal someone else’s,Pretty Interesting,what do you say.
Quick Testing Tips update
Which brought me to Quick Testing Tips website.
Coming up with a heuristic
It mentions about the heuristic test strategy by James Bach,Test Reporting Heuristic MCOASTER
Simple tips for testing application navigation
Some simple test ideas that can be pulled from the article include:
* Can you navigate without having to mouseover icons to figure out what’s what? Is it easy to find the link to the home page (or other core areas of your site)?
* Is there a way to distinguish between internal and external links?
* Can you easily open links in the same tab and a new tab? If you open it in the same tab and click back, do you actually go back to where you were?
* Can a user easily tell where they are within the site or application?
The list is endless, I am still reading, why don’t you drop by & join me.
Cheers,
Jassi
Doug Hoffman,
Heuristics,
James Bach,
Mike Kelly,
Navigation,
Navratnas,
Quick Testing,
Satisfice,
Tips
WT26 - Do you have your Budget?
Sunday, February 21, 2010 by Jassi |
1 comments
Weekend Testing Session #26 Experience Report
Date: 20-02-2010
Timing: 3pm - 5 pm IST
Mission: To test the Application and Report the bugs/issues in it.
Application Tested: Buddi ver-3.2.2.10
Operating System: Windows XP with Java installed
Bug Reporting: www.Bugrepository.com Select WT26 from the Project folder
Coordinated By: Ajay Balamurugadas,Jaswinder Kaur Nagi
Participants: Ajay Balamurugadas, Arvind Jaiswal,Arun, Allmas Mullah, Jaswinder Kaur Nagi ,Shakthi Bhuvaneshwaran, qudsia.yousaf
Application briefing: Buddi is a personal finance and budgeting program, aimed at those who have little or no financial background.
Arun: had initiated the discussion session, since the application was new for him he had no idea how to start testing with ,but once he had hands on the functionality, there were no problems for him. According to him the application was quite unstable,he felt there were many issues generating graphs. Overall it was a good experience for him since it was the first time he was testing any application without any requirements & that too a Financial application. Weekend Testing would like to appreciate him for helping other participants to understand the application.
Arvind: Learned how to test an application where there is less time and no requirements given as such. It was quite challenging for him. He also learnt about any finance related software, how it can be as he had never worked till now. He also came to know about himself and how can to handle such a situation.
Allmas Mullah: According to her the application was very basic & there was not so much fun in testing it and the main thing was she didn’t find it intuitive enough When she tried to read the tutorial to get more info, she found that it was online but was expecting it to be a part of the application which made her realize that it was completely not a desktop/stand-alone application, so having no internet connection can lead to no access to its Tutorials. According to her if a 55 yr old lady who is not used to computers uses this application then the Tutorial can be a problem. If the application is used by a novice user then it scores low in being attractive enough for the novice user to use, he/she would rather use book and pen. Her overall experience testing under pressure can be fun if one knows how to maintain one’s calm
Shakthi Bhuvaneshwaran: Was initially quite apprehensive as he was unable to understand what exactly he was supposed to do, but when helped by Arun he could continue very nicely. Shakthi did Ad-hoc testing. Being a Financial application made it quite interesting for him to test, he tried to learn the application with out idea of functionality this made it more interesting for him. Overall it was very good experience and he enjoyed testing the financial application.
Ajay Balamurugadas: Ajay was the facilitator for the WT#26 but unfortunately there was a power cut at his end so he was unable to continue, But he was back after an hour and decided to test the application later after the discussion was over.
My Experience:
I downloaded the application to test but found that it needed Java Virtual Machine, so downloaded Java. But then Ajay called up saying that since there was Power cut at his end I will have to take up the session and do the coordination .I was a bit apprehensive and quite nervous but I took up the challenge. I was worried since Ajay has been coordinating since almost 25+ sessions, it can be possible that I will not be accepted by the participants.But things went well & Ajay was also helping me through the phone calls & then online, the session was completed successfully. Many thanks to Ajay & Weekend Testing for giving me this opportunity.
I would like to Reiterate the important Lesson what Allmas said:
“Testing under pressure can be fun if one knows how to maintain one’s calm”
Date: 20-02-2010
Timing: 3pm - 5 pm IST
Mission: To test the Application and Report the bugs/issues in it.
Application Tested: Buddi ver-3.2.2.10
Operating System: Windows XP with Java installed
Bug Reporting: www.Bugrepository.com Select WT26 from the Project folder
Coordinated By: Ajay Balamurugadas,Jaswinder Kaur Nagi
Participants: Ajay Balamurugadas, Arvind Jaiswal,Arun, Allmas Mullah, Jaswinder Kaur Nagi ,Shakthi Bhuvaneshwaran, qudsia.yousaf
Application briefing: Buddi is a personal finance and budgeting program, aimed at those who have little or no financial background.
Arun: had initiated the discussion session, since the application was new for him he had no idea how to start testing with ,but once he had hands on the functionality, there were no problems for him. According to him the application was quite unstable,he felt there were many issues generating graphs. Overall it was a good experience for him since it was the first time he was testing any application without any requirements & that too a Financial application. Weekend Testing would like to appreciate him for helping other participants to understand the application.
Arvind: Learned how to test an application where there is less time and no requirements given as such. It was quite challenging for him. He also learnt about any finance related software, how it can be as he had never worked till now. He also came to know about himself and how can to handle such a situation.
Allmas Mullah: According to her the application was very basic & there was not so much fun in testing it and the main thing was she didn’t find it intuitive enough When she tried to read the tutorial to get more info, she found that it was online but was expecting it to be a part of the application which made her realize that it was completely not a desktop/stand-alone application, so having no internet connection can lead to no access to its Tutorials. According to her if a 55 yr old lady who is not used to computers uses this application then the Tutorial can be a problem. If the application is used by a novice user then it scores low in being attractive enough for the novice user to use, he/she would rather use book and pen. Her overall experience testing under pressure can be fun if one knows how to maintain one’s calm
Shakthi Bhuvaneshwaran: Was initially quite apprehensive as he was unable to understand what exactly he was supposed to do, but when helped by Arun he could continue very nicely. Shakthi did Ad-hoc testing. Being a Financial application made it quite interesting for him to test, he tried to learn the application with out idea of functionality this made it more interesting for him. Overall it was very good experience and he enjoyed testing the financial application.
Ajay Balamurugadas: Ajay was the facilitator for the WT#26 but unfortunately there was a power cut at his end so he was unable to continue, But he was back after an hour and decided to test the application later after the discussion was over.
My Experience:
I downloaded the application to test but found that it needed Java Virtual Machine, so downloaded Java. But then Ajay called up saying that since there was Power cut at his end I will have to take up the session and do the coordination .I was a bit apprehensive and quite nervous but I took up the challenge. I was worried since Ajay has been coordinating since almost 25+ sessions, it can be possible that I will not be accepted by the participants.But things went well & Ajay was also helping me through the phone calls & then online, the session was completed successfully. Many thanks to Ajay & Weekend Testing for giving me this opportunity.
I would like to Reiterate the important Lesson what Allmas said:
“Testing under pressure can be fun if one knows how to maintain one’s calm”
European weekend Testing–05 # EWT05
Monday, February 15, 2010 by Jassi |
0
comments
Date: 13-02-2010
Time: 3 pm – 5 pm GMT (3-4 pm Testing & 4-5 pm Debriefing).
Mission:To test the below mentioned application and Find quality related valuable information about the product.
Application Name: Virtual Magnifying Glass 3.3.2
Reporting issues: www.BugRepository.com
Participants : Anna Baik , Ajay Balamurugadas ,Indra, Jaswinder Kaur Nagi, Jeroen Rosink, Krishnaveni K, Markus Gärtner , Nagashree Manjunath , Shiva Shankari , Zeger Van Hese
As usual the Mission and Debriefing session were awesome. We started our Testing by introducing ourselves.
I downloaded the application from the link provided by Markus Gartner. But for some reasons the installer did not start it was getting an error related to permissions. Strange enough it was my own Personal PC & I had all the rights, so no idea why that was happening. Markus helped me by sending application installer via Skype but still no success.
As a last resort I closed all the applications and restarted the machine but unfortunately it did not work. So ,on Markus’ tip-off I reported this as a bug, the only one by me yesterday, pretty weird for me .Surprisingly, I tried to install it again today and the installer was okay. I was able to install so no idea what happened yesterday.
Debriefing was awesome, in which we came to know that Zeger and Ajay tried to pair and test together using SFDPOT Oracle by dividing the work between them, they found some serious usability issues
Jeroen used a different approach altogether .If you are interested in knowing the approach used by Jeroen and other testers to test the application, please dive in to read the entire Transcript here (Transcript courtesy: Markus Gartner)
Lesson Learned:
"Test this" is not a mission you should accept, we need to ask questions, so that we do not fall in the Traps we create ourselves by assuming things.
Some wonderful quotes:
“So many traps we create for ourselves” - Ajay B
“We need to clear the traps quickly” - Ajay B
“Clearing traps is a skill. Recognizing traps is a bigger skill” - Ajay B.
“More often than clearing I see people working around traps” - Anna Baik
“Sometimes we get so used to working around traps, we assume they will always constrain us” –Markus Gartner.
“It's a success if you can say "testing is fun" afterwards”- Jeroen
“Minds are shaped when guided under pressure in a certain direction trying to maintain vision and control” - Jeroen
“I feel as if I am triggered to think, probably my subconscious would just do its work in the background about new things that I learnt from this session and how could I have done better “ - Nagashree Manjunath
Happy Reading
Related Links
EWT05 – I can see clearly now
Weekend testing EWT05: my first attempt
Through the looking-glass, and what testers found there – EWT05
Weekend Testing - Motivating ans knowledge sharing platform
Time: 3 pm – 5 pm GMT (3-4 pm Testing & 4-5 pm Debriefing).
Mission:To test the below mentioned application and Find quality related valuable information about the product.
Application Name: Virtual Magnifying Glass 3.3.2
Reporting issues: www.BugRepository.com
Participants : Anna Baik , Ajay Balamurugadas ,Indra, Jaswinder Kaur Nagi, Jeroen Rosink, Krishnaveni K, Markus Gärtner , Nagashree Manjunath , Shiva Shankari , Zeger Van Hese
As usual the Mission and Debriefing session were awesome. We started our Testing by introducing ourselves.
I downloaded the application from the link provided by Markus Gartner. But for some reasons the installer did not start it was getting an error related to permissions. Strange enough it was my own Personal PC & I had all the rights, so no idea why that was happening. Markus helped me by sending application installer via Skype but still no success.
As a last resort I closed all the applications and restarted the machine but unfortunately it did not work. So ,on Markus’ tip-off I reported this as a bug, the only one by me yesterday, pretty weird for me .Surprisingly, I tried to install it again today and the installer was okay. I was able to install so no idea what happened yesterday.
Debriefing was awesome, in which we came to know that Zeger and Ajay tried to pair and test together using SFDPOT Oracle by dividing the work between them, they found some serious usability issues
Jeroen used a different approach altogether .If you are interested in knowing the approach used by Jeroen and other testers to test the application, please dive in to read the entire Transcript here (Transcript courtesy: Markus Gartner)
Lesson Learned:
"Test this" is not a mission you should accept, we need to ask questions, so that we do not fall in the Traps we create ourselves by assuming things.
Some wonderful quotes:
“So many traps we create for ourselves” - Ajay B
“We need to clear the traps quickly” - Ajay B
“Clearing traps is a skill. Recognizing traps is a bigger skill” - Ajay B.
“More often than clearing I see people working around traps” - Anna Baik
“Sometimes we get so used to working around traps, we assume they will always constrain us” –Markus Gartner.
“It's a success if you can say "testing is fun" afterwards”- Jeroen
“Minds are shaped when guided under pressure in a certain direction trying to maintain vision and control” - Jeroen
“I feel as if I am triggered to think, probably my subconscious would just do its work in the background about new things that I learnt from this session and how could I have done better “ - Nagashree Manjunath
Happy Reading
Related Links
EWT05 – I can see clearly now
Weekend testing EWT05: my first attempt
Through the looking-glass, and what testers found there – EWT05
Weekend Testing - Motivating ans knowledge sharing platform
Subscribe to:
Posts (Atom)
Subscribe To
Posts
All Comments
