User Tag List

Page 1 of 2 1 2 LastLast
Results 1 to 10 of 11

Thread: Beta Tester Reporting Requirements

  1. #1
    Clickteam Clickteam
    Jeff's Avatar
    Join Date
    Jun 2006
    Location
    Battle Ground Washington
    Posts
    11,822
    Mentioned
    7 Post(s)
    Tagged
    2 Thread(s)

    Beta Tester Reporting Requirements

    In order to track beta tester activity you should do the following:

    Start a thread titled with your name.
    Example -- My thread would be named Jeff Vance

    Inside this thread recap your weekly testing reports or if you have been busy for the week mention that.

    Then for each bug please start a new thread with a description of the bug and an MFA showing the bug if possible.

    As time goes on inactive beta testers may be replace with new testers.

    It is important to report bugs and recap your weekly testing. We want to make sure active beta testers get full recognition and rewards.

  2. #2
    Clicker

    Fusion 2.5 DeveloperAndroid Export ModuleHTML5 Export ModuleiOS Export ModuleSWF Export ModuleXNA Export ModuleUnicode Add-on
    Fusion 2.5 (Steam)
    ASD's Avatar
    Join Date
    Feb 2007
    Location
    Japan
    Posts
    1,777
    Mentioned
    9 Post(s)
    Tagged
    0 Thread(s)

    Re: Beta Tester Reporting Requirements

    Thread title is real name?

  3. #3
    Clicker Multimedia Fusion 2 DeveloperiOS Export ModuleSWF Export Module
    Francois's Avatar
    Join Date
    Jul 2006
    Location
    Montpellier, France
    Posts
    6,920
    Mentioned
    0 Post(s)
    Tagged
    1 Thread(s)

    Re: Beta Tester Reporting Requirements

    Yes, your name is OK.

  4. #4
    Clicker Fusion 2.5 DeveloperAndroid Export ModuleiOS Export ModuleSWF Export ModuleInstall Creator ProPatch Maker

    Join Date
    Jun 2006
    Location
    Norway
    Posts
    528
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Beta Tester Reporting Requirements

    Are we supposed to make a new thread on each bug report, or a new reply within our thread? Do we report bugs as we find them, or a full disclosure at the end of the week?

  5. #5
    Clicker Multimedia Fusion 2 DeveloperiOS Export ModuleSWF Export Module
    Francois's Avatar
    Join Date
    Jul 2006
    Location
    Montpellier, France
    Posts
    6,920
    Mentioned
    0 Post(s)
    Tagged
    1 Thread(s)

    Re: Beta Tester Reporting Requirements

    I think it is best to report all the bugs at the end of the week.
    Keep them inside your thread, this will diminish the numbver of active threads in the forum.

  6. #6
    Clicker

    Fusion 2.5 DeveloperAndroid Export ModuleHTML5 Export ModuleiOS Export ModuleSWF Export ModuleXNA Export ModuleUnicode Add-on
    Fusion 2.5 (Steam)
    ASD's Avatar
    Join Date
    Feb 2007
    Location
    Japan
    Posts
    1,777
    Mentioned
    9 Post(s)
    Tagged
    0 Thread(s)

    Re: Beta Tester Reporting Requirements

    When is this test end?

  7. #7
    Clicker Fusion 2.5 DeveloperAndroid Export ModuleSWF Export ModuleXNA Export Module

    Join Date
    Jun 2007
    Posts
    480
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Beta Tester Reporting Requirements

    long long time

  8. #8
    Clicker Multimedia Fusion 2 DeveloperiOS Export ModuleSWF Export Module

    Join Date
    Jan 2009
    Posts
    1,052
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Beta Tester Reporting Requirements

    "Keep them inside your thread, this will diminish the numbver of active threads in the forum."

    The only issue I see with this is that we all (including beta testers) will have to read each other's summary threads to see if a bug has been already reported, and discussions about a topic inside those threads could make a thread eventually unreadable.

    Why not having the best of two worlds? It would be easier, imvho, if we could:

    A) Have the thread "My Name: Test-Report Summary" to sum up our findings as sitcky threads where we can update the list weekly, where no betatesters can reply (only CT can). And

    B) Report each bug separately in a moving thread (non-sticky one) so as to keep any response/discussion in that thread (and away from the summary sticky thread), and also we can quickly verify if a bug has been reported.

    I´m not saying I won't comply, just suggesting an alternative reporting approach to "Keep everyhting inside one thread".

  9. #9
    Clicker Fusion 2.5 MacFusion 2.5 DeveloperAndroid Export ModuleiOS Export ModuleUniversal Windows Platform Export ModuleSWF Export ModuleXNA Export ModuleInstall Creator Pro
    Fusion 2.5 (Steam)Android Export Module (Steam)HTML5 Export Module (Steam)iOS Export Module (Steam)Universal Windows Platform Export Module (Steam)

    Join Date
    Jul 2009
    Location
    Québec
    Posts
    113
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Beta Tester Reporting Requirements

    This is simply a suggestion why don't you deploy a bug tracking engine like bugzilla. It is pretty useful and easy to follow for each kind of bug we tester report.

    http://www.bugzilla.org/

    I've used it a numerous times when I was working as QA tester for Longtail Studios.

  10. #10
    Clicker

    Fusion 2.5 DeveloperAndroid Export ModuleHTML5 Export ModuleiOS Export ModuleSWF Export ModuleXNA Export Module
    geothefaust's Avatar
    Join Date
    Jul 2006
    Location
    Portland, OR
    Posts
    498
    Mentioned
    3 Post(s)
    Tagged
    0 Thread(s)

    Re: Beta Tester Reporting Requirements

    Another alternative is Mantis. We've been using it for development of 3D-Coat for some time now, we and our users/testers have found it useful.

    Bugzilla is good too.

Page 1 of 2 1 2 LastLast

Similar Threads

  1. Reporting bugs
    By Anders in forum iOS Export Module Version 2.0
    Replies: 18
    Last Post: 29th October 2013, 09:04 AM
  2. Mid to Late '90s Beta Tester
    By stevehartwell in forum Multimedia Fusion 2 - Technical Support
    Replies: 8
    Last Post: 2nd November 2012, 08:57 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •