View View source History

Contribute/Bugsquad/BugDays/06APR08

< Contribute‎ | Bugsquad‎ | BugDays
Revision as of 15:45, 6 April 2008 by JLP (Talk | contribs)

Jump to: navigation, search

Contents

Introduction

This triage day will run from 0:00 UTC - 23:59 UTC on April 6th 2008. Our target for triage is bugs listed in bugs.kde.org under the product Konqueror.

The goal of this bug-day is to check for: simple step-by-step instructions, reproducibility, and most of all, come up with test-cases for reproducing the bugs. This will enable the Konqueror developers to deal with bugs more easily, and so have more time left to actually fix them. When you have added either a test-case or step-by-step instructions for the reproduction of a bug, please list it in the appropriate section below, so that a second triager can see if they can get your instructions/test-case to work correctly. This page provides an excellent explanation of how to create a test-case. This page also has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Konqueror doesn't have as many duplicates as some applications, and we don't want to claim things are duplicates when they aren't. So do not look too hard for them, and make sure to double check them with someone else, preferably one of the developers before marking/closing.We especially don't want to create more work for developers!

Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

You should either be working with Konqueror from KDE 4 (either 4.0.2 or newer is best or SVN trunk) for testing these bugs. In this case, it probably won't matter which one, because KHTML/KJS are aggressively forward-ported and back-ported, and you might find 4.0.x easier to compile.

You may need another browser to test things in.

Testcases

If you come across a bug with a testcase in the text, put it under the testcase section. If it isn't marked "testcase" in the title, make a note of that. Check that the testcase works! (And doesn't work!)

Most importantly, we need to create testcases. These are time-consuming, but extremely useful and really help out developers. These are especially important if it is a site that is either a non-Western language or a site you need some sort of account for.

Unclear

If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the bugs awaiting feedback section. Be polite, we want to be nice to our bug reporters!

Is it a big bug?

Prioritizing is good. If a major website doesn't work, that is important. Let's keep track of them.

Version field

Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", it won't show up in developer's searches for 4.0 bugs! Change the version field to match what the other one says, i.e. to match version the bug was first reported in, or mark it below if you don't have bugzilla permissions. Do not update or change the version number (ex. from 3.5.2 to 4.0.2) if it is currently set as a number! Just make a note on the bug of what the status is in the version you are testing with (be explicit as to what version of 4 you are using, mentioning whether it is a source build or which distro the packages come from).

Double Check!

Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.

Details

Please select a period of bugs from the Division of Labour section below and mark your name next to it and mark it with your irc nickname to show that you are working on it. When you have completed all the bugs in that section, please mark it as complete.

For each bug, try and reproduce it as described in the report. Then list it in the appropriate section below. If you wish to close or mark as duplicate a bug, please list it here even if you have the bugzilla permissions to do so, in order to get a second opinion from another triager. This will help to reduce the number of incorrect actions taken on bugs.

Sign-in

Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)

Please give distro/version or SVN branch/trunk with revision below:

IRC Nickname KDE version used for testing
Grundleborg svn trunk r793457
Blauzahl svn branches/KDE/4.0 r793901
FiNeX svn trunk r793368
lemma svn trunk r793971
krop svn trunk r793966
annma svn trunk r793777
kirun 4.0.3 kubuntu
Njg234908 4.0.3 opensuse
matt__ svn trunk r793709
JLP svn trunk r794088
Ktip.png
 
Tip
Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup ~~~ to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).


Division of Labour

Please choose a month that is not already taken and then query bugs.kde.org for all bugs in that month. Please mark you irc nickname in the table below to show which month's bugs you are working on to avoid duplication of effort.

The bugzilla query to use for this triage day can be found here. Be sure to correct the dates to the month which you will triage before running the query.

Month No of bugs IRC Nickname Status
pre 2003 20 Grundleborg done
2003-01 4 FiNeX done
2003-02 6 lemma done
2003-03 6 lemma done
2003-04 3 lemma done
2003-05 3 lemma done
2003-06 5 blauzahl done
2003-07 6 Grundleborg done
2003-08 5 lemma done
2003-09 3 Grundleborg done
2003-10 8 Grundleborg done
2003-11 12 annma done
2003-12 13 Blauzahl starting
2004-01 13 Finex Skipped bug #79369 need more testing
2004-02 10 Njg234908 3 down 7 to go
2004-03 14 matt__ done
2004-04 11 Finex done
2004-05 14 Grundleborg done up to+including bug #80771, someone else can do the rest as have to stop now.
2004-06 8 lemma done
2004-07 8 lemma done
2004-08 11 lemma in progress
2004-09 16 Finex working
2004-10 9
2004-11 12 kirun starting
2004-12 13 Finex started
2005-01 11
2005-02 16
2005-03 20
2005-04 16
2005-05 24
2005-06 22
2005-07 10
2005-08 10
2005-09 16
2005-10 20
2005-11 16
2005-12 21
2006-01 13 krop starting
2006-02 13
2006-03 17
2006-04 19
2006-05 20
2006-06 21
2006-07 16
2006-08 18
2006-09 23
2006-10 27
2006-11 25
2006-12 17
2007-01 26
2007-02 26
2007-03 25
2007-04 11
2007-05 20
2007-06 21
2007-07 16
2007-08 12
2007-09 9
2007-10 16
2007-11 21
2007-12 23
2008-01 32
2008-02 28
2008-03 22
2008-04 2

(Total bugs 974)

Bugs needing version field changed

Bugs should be listed here if their version field is invalid and they are still present in KDE 4, so that the version field can be corrected.


Bugs with test-cases Added

Bugs that have had a test case (an example of how to reproduce the bug) added should be entered below.

  • bug #19921 - test case was already there but wasn't marked. Grundleborg
  • bug #32563 - testcase added. Grundleborg
  • bug #79492 - testcase already present. Bug still reproducible Finex
  • bug #79813 - testcase already present. Added on the subject. Bug still reproducible: Saving the file of the testcase will start Kget which save an empty file Finex
  • bug #79813 - testcase already present. Added on the subject. Bug (?) still reproducible. Is it really a bug? It should be checked if a valid email address could contain a "#" char Finex
  • bug #80432 - testcase already present (even on subject). Bug still reproducible. Finex
  • bug #54844 - simple (!) testcase added. Bug still reproducible but minor. Needs version change. lemma
  • bug #54696 - testcase already present (even on subject). Bug still reproducible. Needs version change. lemma
  • bug #56118 - testcase already present (even on subject). Was actually two different bugs (partly fixed), maybe rename to make the issue clearer. Needs version change. lemma
  • bug #55946 - testcase already present (even on subject). Still present in trunk. Needs version change. lemma
  • bug #37007 - added a testcase and [testcase] tag Grundleborg
  • bug #53885 - Added an admittedly simple testcase. It might be disputable if this is actually a bug, a wish or deemed as correct behaviour. Needs version change. lemma
  • bug #57819 - Old testcases no longer valid. Added a new testcase. Bug still present in trunk. lemma
  • bug #57360 - Some testcases seem to work on trunk, others not. name-anchors seem more likely to work than id-anchors. Needs version change lemma
  • bug #49441 - test case uploaded Grundleborg
  • bug #50688 - testcase copy uploaded. Grundleborg
  • bug #57485 - added a simpler testcase (already labeled). still present in trunk. Needs version change. lemma
  • bug #57995 - readded testcase (already labeled). still present in trunk. Needs version change. lemma
  • bug #51202 - test case still fails. added testcase tag Grundleborg
  • bug #59492 - css test suite case; last test fails, can't add testcase tag, needs version change Blauzahl
  • bug #58111 - testcase already there (needs label), still reproducible in trunk. Needs version change. lemma
  • bug #58432 - added new testcase, still reproducible in trunk. lemma
  • bug #60867 - uploaded testcase as attachment. Still present in trunk. Grundleborg
  • bug #62072 - testcase was already there (needs label), still present in trunk. lemma
  • bug #63048 - testcase was already there (needs label), still present in trunk. Needs version change. lemma
  • bug #61176 - testcase tag added. still in trunk. Grundleborg
  • bug #61417 - testcase tag added. still present in trunk Grundleborg
  • bug #64705 - testcase tag added, still present in trunk. Grundleborg
  • bug #65722 - testcase tag added, still present in trunk. Grundleborg
  • bug #66781 - new testcase added by lemma.
  • bug #67353 - new testcase added by annma.
  • bug #83916 - testcase already there (needs label), could probably be made a wish. lemma
  • bug #84217 - testcase (needs label), confirmed, could probably be made a wish. lemma
  • bug #83755 - testcase (already has label), confirmed. Needs version. lemma
  • bug #82930 - testcase (needs label), confirmed. lemma
  • bug #83326 - testcase (needs label), confirmed, needs recheck if I actually understood the problem. Needs version. lemma
  • bug #83880 - testcase (already has label), still minor issues. lemma
  • bug #92885 - testcase already present (needs label), confirmed.
  • bug #84498 - testcase already present, confirmed. lemma
  • bug #85774 - testcase already present (needs label), confirmed. lemma
  • bug #68391 - testcase already present, confirmed. annma
  • bug #76489 - testcase already present, confirmed, suggested patch already attached, matt__
  • bug #76676 - testcase already present, confirmed. matt__
  • bug #77833 - testcase already present. animated gif no longer animates at all, if you save the file and then open it in iceweasel it works fine. matt__
  • bug #74569 - 2 testcases already present and marked as [testcase]. 1st worked ok for me but 2nd partially reproduced problem. Njg234908
  • bug #68429 - added testcase, confirmed but low priority. annma
  • bug #87094 - Bug (with testcase) reproduced on trunk. FiNeX
  • bug #78331 - test case already given. matt__
  • bug #78725 - test case already given. matt__
  • bug #68876 - test case already given, not fixed in Konqueror 4.0.68. annma
  • bug #69091 - test case already given, not fixed in Konqueror 4.0.68. annma
  • bug #120458 - Testcase already present, confirmed in trunk. krop

Bugs with step-by-step instructions

If you have provided step by step instructions on how to reproduce a bug, please list the bug here.

  • bug #80067 - For reproduce the bug go to google.com, type some text on the search field, press "TAB" and "SPACE" quickly. The search will not be started. Finex
  • bug #51649 - reproduced using instructions. Grundleborg
  • bug #61710 - instructions to reproduce. Would be good if someone could figure out how to make a testcase out of it. Grundleborg
  • bug #65528 - instructions tag added, since easy steps to reproduce. Grundleborg

Bugs no longer present in 4.x

If a bug is reported against a version of KDE before 4.0, but the bug can no longer be reproduced in KDE 4.x, then it should be listed here. Please do not close the bug. The Konqueror developers would like to check each one before they are closed.


Bugs to be marked as RESOLVED

Bugs filed against KDE 4 (ie, only very recent ones) that can no longer be reproduced should be listed here. Bugs filed against earlier versions of KDE that can no longer be reproduced should be listed in the section above.

Bugs to be marked as INVALID

Bugs which are no longer valid go here. A link to the bug and why it qualifies as invalid should be provided.

Some examples of when a bug should be closed as INVALID:

  • The reported behavior is not a bug
  • The bug is completely unrelated to KDE


  • bug #59815 - Closed with REMIND per SadEagle's instructions Blauzahl
  • bug #85783 - testcase renders the same in 3.5.9, trunk, FF2, IE6/7, probably an error in the page. lemma
  • bug #85688 - testcase (needs to be labeled), one part of the bug has been fixed, the other is not checkable due to the external testcase being unavailable. lemma
  • bug #87357 - Bug not reproducible: website changed and no informations about the problem. FiNeX

This list is not exhaustive. If you feel a bug is invalid for any other reason, be sure to list it here, mentioning why you think it is invalid.

Bugs to be marked as DUPLICATE

Duplicates found should be placed here with a link to the bug which you think it is a duplicate of.

Bugs needing users with particular setups

Bugs that require particular software or hardware that you don't have available should be listed here with a description of the non-standard requirement.

  • bug #55087 - the reporter was using a PIII 500MHz, I'm on a Q6600. Moving the mouse as reported uses quite some CPU (>32% on 3.5.9, <27% on trunk) but someone with an older CPU should see if this is still an issue. lemma
  • bug #60652 - needs someone with an ebay account to create a simple test-case so non-ebay account holders can reproduce the bug. Grundleborg
  • bug #77030 - needs someone who can read hindi (Devanagari script) to check this one - possibly fixed in trunk. matt__
  • bug #77246 - needs someone with a Yahoo! ID. matt__
  • bug #77592 - needs someone with Java. matt__
  • bug #78210 - needs someone with a gay.com account. matt__

Non english locales

Bugs requiring non-English locales should be listed here, along with the locale they require.

Bugs needing attention from Konqueror developers

Add bugs here if you need to find out whether the observed behavior is intended, or if there's some other reason that it would be useful for a Konqueror developer to take a look. Make sure you indicate why the bug needs attention from them.

  • bug #79897 - Bug with complete testcases. Firefox 3b5 behavior is like konqueror (on KDE3 and KDE4). Actually konqueror is respecting standard. Emulate IE breaking them is not a good idea. FiNeX
  • bug #80285 - On this report is proposed to split on certain condition long lines without spaces. FiNeX
  • bug #52665 - Issue about XML mime. Need some attention. A lot of testcase are still valid. FiNeX
  • bug #53175 - Question about JS which test the browser. How should konqueror be identified? FiNeX
  • bug #47320 - no idea what to do about this one... probably best to do nothing Grundleborg
  • bug #40116 - can't figure out what's going on here. Grundleborg
  • bug #50815 - not sure if this is intended behavior or not? Grundleborg
  • bug #60956 - carewolf: what to do about this bug? Grundleborg
  • bug #59803 - Icky XSLTProcessor and browser specific stuff. Blauzahl
  • bug #65516 - don't know about this one. test case wraps in both konq and firefox. Don't know what the correct behavior is. Grundleborg
  • bug #65606 - should this bug be closed as per the last comment, or is the _new stuff really a bug? Grundleborg
  • bug #65673 - behavior is still the same as firefox. Should it be changed? Grundleborg
  • bug #83284 - testcase (needs label), confirmed, needs checking what the default behaviour should be.
  • bug #85712 - external testcase, too slow to check the bug. If this concerns META Refresh is there another way to test this? lemma
  • bug #88377 - Need some attention: is this a kmail or a konqueror bug? Is kmail using khtml for rendering html emails? FiNeX
  • bug #86671 - The websites which were reported to make konqueror crash are changed/closed. There is no testcase or specific instruction. Instead there are about 20 duplicate of the bug. (maybe some dups are not real dups says Grundleborg on IRC) FiNeX
  • bug #80771 - problem seems to be much less severe on KDE4, perhaps the bad JS code is responsible for the CPU use? Grundleborg

Needs more information

  • bug #55870 - The URL (k-state) given by the original reporter is offline. According to archive.org the menu consisted of an image map which works flawless in 3.5.9 and trunk. The second URL (mplayer) looks the same in Firefox. It seems this problem is not reproducible. lemma
  • bug #86747 - Website which make konqueror crash is no more reachable. There are no infos and testcases. FiNeX

Bugs awaiting feedback

NB. Feedback should only be requested for bugs if you have tried and failed to reproduce them or if the report contains insufficient information to try and reproduce the bug. Requesting feedback for a bug should be seen as a last resort only.

Bugs for which feedback has been requested, which should be revisited in 30 days to see if there's any response. Please list all bugs here for which feedback has been requested.

  • bug #5698 - I can't reproduce this from the old links given. teve could at one point. (nyt js popup bug) Blauzahl
Retrieved from ‘http://techbase.kde.org/index.php?title=Contribute/Bugsquad/BugDays/06APR08&oldid=23033’

Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V. • Legal