Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
Bug in disarm( )
Nov 12, 2017, 6:54 pm
By GatewaySysop
Bug in will_fall( )
Oct 23, 2017, 1:35 am
By GatewaySysop
Bug in do_zap( ), do_brandish( )
Oct 18, 2017, 1:52 pm
By GatewaySysop
Bug in get_exp_worth( )
Oct 10, 2017, 1:26 am
By GatewaySysop
Bug in do_drag( )
Oct 8, 2017, 12:40 am
By GatewaySysop
LOP Heroes Edition
Author: Vladaar
Submitted by: Vladaar
Heroes sound extras
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.3
Author: Vladaar
Submitted by: Vladaar
Memwatch
Author: Johan Lindh
Submitted by: Vladaar
Beastmaster 6D sound files
Author: Vladaar
Submitted by: Vladaar
Users Online
CommonCrawl, Yandex, Bing, Google, Yahoo!, Majestic-12

Members: 0
Guests: 5
Stats
Files
Topics
Posts
Members
Newest Member
476
3,704
19,231
608
LAntorcha
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » General » General Discussions » Bug Testing
Forum Rules | Mark all | Recent Posts

Bug Testing
< Newer Topic :: Older Topic > Please try and follow this!

Pages:<< prev 1 next >>
Post is unread #1 Sep 17, 2005, 1:29 pm
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,639
JoinedJan 1, 2002

Ok, this is going to make me sound like a dick or something, but I need to nip this in the bud now before things start getting out of control.

If you find what you think is a bug, I want to see it verified first in a fresh copy of the package you are reporting it for. Even if this means you need to download it, compile it, and run it to find out, please do so.

More and more bug reports are sprining up on forums ( not so much here yet ) where people who have been using modified code, older packages, hacked frakenstein bases, and other even more bizzare setups, who find bugs and immediately report them as errors in the stock configuration. I have seen this begin to eat into the time it takes to fix a legitimate problem or rule it out as a real bug.

So if you find a bug, verify it. Start posting logs of the output you get if it generates any. Give details. Compiler errors if any. Log entries if any. Steps to reproduce on a stock copy, after you've verified it still happens there. If we all start to do this, then less of these bug reports will be left to sit around not being investigated.
       
Post is unread #2 Oct 7, 2005, 7:16 am
Go to the top of the page
Go to the bottom of the page

Noplex
Apprentice
GroupMembers
Posts62
JoinedAug 30, 2005

Why don't you setup some form of bugzilla on the server? For anyone other than the developers, it would make an easy way for them to contact you guys and post bugs. You could also check them off as you get done with them.
       
Post is unread #3 Oct 7, 2005, 11:29 pm
Go to the top of the page
Go to the bottom of the page

Greven
Magician
GroupMembers
Posts204
JoinedMar 5, 2005

We have set up a wiki with a bug tracking ticket system, works well, and is an easy alternative to bugzilla.
       
Pages:<< prev 1 next >>