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
Posts
