From: aglover@acorn.co.uk (Alan Glover) Subject: Bugs without flames Date: 11 Nov 91 14:57:11 GMT Organization: Acorn Computers Ltd, Cambridge, England Ok, looks like it's time to try this again. As someone remarked, this group is getting to look like alt.flame.acorn, so let's put all this energy to some constructive use instead ..... Below is the standard electronic form used within Acorn, and by external testers, to report faults in software or hardware. Instead of flaming about a bug simply fill in as much as you can on the form below, (remembering that the stranger the bug, the more info will be needed to make it happen controllably), and email it to me. If a lot of supporting info is needed, it may be better to send a letter (possibly with accompanying disc) - address it to Customer Services, Acorn Computers Ltd., Fulbourn Road, Cherry Hinton, Cambridge, CB1 4JN, UK. I will not acknowledge receipt unless requested to, or respond to anything flame-like, so don't bother sending it - just send the information needed to reproduce a bug. To give you an idea of what is and is not useful: a) Do this, do this, do this and it does this (which it shouldn't). Very useful, especially when 100% repeatable. b) Do this, do this, and it sometimes does this. Try to quantify how often 'sometimes' is. Failures are never truly random - try to identify what missing factor is needed to make the bug thoroughly reproducable. c) This is cr*p, and doesn't do x, y, z. Unless we said it should do x,y and z this is categorised as a change to the specification of a product, and is only likely to happen if a number of people agree with you. No product can be everything to all people! Avoid saying something is cr*p. It's inaccurate, irrelevant, and just gets people wound up. d) X crashes all the time. Absolutely useless :-). Obviously it didn't do it for us during testing or it would never have got released. Gradually eliminate elements of your working environment until you find the source of the clash (which is a typical reason for this). If you don't manage to localise if further, turn your attention to any soft-loaded modules, and then to any Expansion Cards. Please note: The fact that bugs exist (or are alleged to exist) in a product is no guarantee that a new version will be released, or that the alleged bug will be fixed. Most of the fields are self explanatory, but here are some brief notes: App. version number - from the Info Box, or from a module where appropriate. Exact Hardware Config - be exact ! Include any expansion cards. ROM Version Number - 2.00, 2.01 (A540 only) or 3.00 (A5000 only). Tester Email name - in full please Test Number - a number of your own devising Fault Number - will be filled in by us - leave it blank Priority - your idea of seriousness - rate as Low, Medium or High Summary - keep it to one line of <60 characters Status - will be filled in by us - leave it blank Date encountered - guess! :-) Test and Fault description - be verbose but relevant ! If you feel some feature is missing from an Acorn product then use the same form, but make clear: a) Why the feature should be provided, and exactly what it should do. b) Who it would be useful to (ie, what groups of people). Again, remember that this is not provided as a way to let off steam, objectivity is important! Alan --- cut here --- FAULT REPORT Application Name: Application Version Number: Exact Hardware configuration: ROM Version Number: Tester Email Name: Test Number: Fault Number: Priority: Summary: Status: Date Encountered: Test and Fault Description: --- cut here --- -------------------------------------------------------------------------- aglover@acorn.co.uk - Moderator of comp.binaries.acorn/comp.sources.acorn Mail submissions to submit@acorn.co.uk, other mail to moderator@acorn.co.uk