Comments on: productive testing tips

By: stephen o'grady

stephen o'grady — Sun, 18 Mar 2007 23:36:26 +0000

@andre: excellent news: will look forward to that. i don’t mind following instructions like these, but would argue that i’m probably in the minority.

By: Luis

Luis — Sun, 18 Mar 2007 22:43:49 +0000

Chris: Whether you’ll be testing stable or unstable depends on a lot of things, including developer availability, project priorities, etc., which were beyond the scope of my comment. The point I was trying to get across was that you need to use the latest version of whatever you’re trying to test. That means that if your purpose is to test the stable branch, you need to be building out of stable branch revision control which the next tarballs will come from, rather than the last released set of tarballs. Hope that is more clear.

By: andre

andre — Sun, 18 Mar 2007 21:55:49 +0000

@stephen: the user would have to install additional debug *packages* to provide a better stacktrace. we hope that for 2.20, we will be able to use the google airbag code to workaround this problem.

By: Chris

Chris — Sun, 18 Mar 2007 16:49:35 +0000

“2. Where possible, use the very latest code”

I think there is too much emphasis on the latest code. How about fixing issues in current releases instead of always pointing to new releases?

I am talking from a users point of view where I always have to upgrade to the latest version just to get fixes that should go into the current version (Firefox, Gnome etc.)

By: stephen o'grady

stephen o'grady — Sun, 18 Mar 2007 16:00:38 +0000

“every major OS now has ways to catch stack traces of catches and send them back to a bug database”

it would also help if the tools would automate the activation of debug flags or other necessary information; most of the stack traces i’ve submitted have come back with messages like the following:

“Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue.”

By: Slawek's Tech Hideout

Slawek's Tech Hideout — Tue, 30 Nov 1999 00:00:00 +0000

Zapomniałeś zapłacić rachunek ? Billreminder ci o tym przypomni. Więcej oraz przykładowe screenshot’y na stronie Og Maciel’a tutaj.Jak efektywnie testować. Przynajmniej kilka rad dał Luis Villa. Więcej na jego blog’u.Zasięg użycia google earth jest coraz bardziej imponujący. Można np. zobaczyć jakie zniszczenia stworzyły kopalnie odkrywkowe. Więcej w artykule na SlashDot’cie.Linux domination ? Po IBM’ie, Monachium itp. teraz Citroen się zdecydował na