[PC-BSD Testing] Alpha/Beta Testing Checklist

[Ian Robinson]

Dear Kris --

Would it help your work if we could develop a master checklist for testing
alpha and beta releases so we could make thorough and consistent reports to
you?  It would not take much to develop a standard checklist of the most
common areas you want us to test.  This is a very small start towards
listing some of the issues that crop up frequently:


Testing Checklist

1.  General Install
a    Downloaded OK?
b    Full Screen Display
c    Added Users OK
d    Partitioning
e    Optional Packages Added
f

2.  Video Configuration
a    Resolution
b    Depth
c    Name of Driver
d    Advanced Settings
e    Works As Expected
f    Problems Noted
      Symptoms
      Programs running
      Repeatable conditions
      Error Messages
      Possible fix or solution
      Recommended command line to troubleshoot or capture critical info.

3.  KDE Desktop/Panel Icons Functions
a    Icons activate program
b    Desktop can be locked/unlocked
c    Desktop can be resized
d    Applets can be added/removed
e    Programs can be added/removed
f    System/PBI Updater Working


3a.  Other Windows Managers


4.  System Settings
a    Can Enter Administrative Mode
b    Can Generate System Report
c    Can Update System
d    Can Update Ports
e
f    Problems Noted
      Symptoms
      Programs running
      Repeatable conditions
      Error Messages
      Possible fix or solution
      Recommended command line to troubleshoot or capture critical info.

5.  Sound Card
a    Mfg & Model
b    Detected/Not-Detected
c    Volume/Mixer Control
d    Sound produced
e
f    Problems Noted
      Symptoms
      Programs running
      Repeatable conditions
      Error Messages
      Possible fix or solution
      Recommended command line to troubleshoot or capture critical info.
5.  PBI
a    Work/Do-not-work normally
b    Can be downloaded and installed
c    Problems noted
      Symptoms
      Programs running
      Repeatable conditions
      Error Messages
      Possible fix or solution
      Recommended command line to troubleshoot or capture critical info.

6.  Packages
a
b
c

7.  Ports
a    Ports tree installed
b    Ports tree can be updated
c    Ports install normally
d
e
f    Problems Noted
      Programs running
      Repeatable conditions
      Error Messages
      Possible fix or solution
      Recommended command line to troubleshoot or capture critical info.

8.  Disk Drives
      Type (ide/sata/scsi & internal/external)

9.  Dual Booting

10.  Networking (Wired/Wireless)
      Auto detected
      Functioning normally
      Problems Noted
          Programs running
          Repeatable conditions
          Error Messages
          Possible fix or solution
          Output of ifconfig command
          Other recommended command line to troubleshoot or capture critical
info.

11.  USB

12.  Desktop Users Guide
        Adequacy of instructions
        Incorrect instructions
        Missing instructions

etc.



When it comes to reporting to you, there is of course the FreeBSD guidance
from "Writing FreeBSD Problem Reports" @
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html
and a similar article "How to Report Bugs Effectively" @
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html .


Should a problem report template be created as an adjunct to the master
checklist?  Moreover, if we accessed the report/survey/template on a web
page form or pdf web page form, perhaps someone could develop a "capture
routine" to log the data.

There are many brighter lights than me so perhaps they could chime in on
whether this documentation project is a good idea or not.

Ian Robinson
Salem, Ohio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pcbsd.org/pipermail/testing/attachments/20090318/939ced65/attachment.html