SEERS - Standardised Bug Reporting
by booshtukka on Oct 25, 2009
- 1,150 views
SEERS is a standardised method of reporting bugs and defects - ensuring consistency and efficiency in your testing and development team.
SEERS is a standardised method of reporting bugs and defects - ensuring consistency and efficiency in your testing and development team.
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 1
- Downloads
- 18
- Comments
- 0
- Embed Views
- Views on SlideShare
- 1,139
- Total Views
- 1,150
Run a business called Silver Squid
Agile Evangelist. Big fan of process. Investigated and experimented with agile processes at several companies and no-one reports bugs properly.
Worked for BBC, Channel 4, Sky
People working in our industry all get bugs raised every day
A bit of history?
In 1947, Grace Murray Hopper was working on the Harvard University Mark II Aiken Relay Calculator (a primitive computer).
On the 9th of September, 1947, when the machine was experiencing problems, an investigation showed that there was a moth trapped between the points of Relay #70, in Panel F.
The word went out that they had "debugged" the machine and the term "debugging a computer program" was born
In today’s web 2.0 world, we have more complicated software, and more bugs. We have dedicated teams of testers just to find them.
Some detailed and complex.
And some not so much.
I’m a mac boy so I have no idea what windows software there is.
Ideally annotate - skitch is great for this.
Some scenarios, a screencast could be good.
The speed of the computer.
Plug-ins.
We will talk more about severity. First let’s mention things we need to know to gauge it.
This goes against Yahoo!’s very good graded browser support - but this an entire different discussion. Suffice to say, with the development time it takes, I do not believe making everything perfect in IE6 is more valuable than developing more features. Remember, your users do not compare browsers side by side like we do. They have no idea there are inconsistencies, and more often than not simply wouldn’t care even if they did. It is unfortunately impossible for a website to look the same in every browser or environment (without just using a huge image map, and even then a text-only browser like Lynx would not be able to render it) and there is nothing to gain in trying needlessly to overcome this.