Beta Tester Reporting Requirements

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.

    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.

    Please login to see this link.

    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.

    Francois
    PM: Please login to see this link.

    "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".

    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.

    Please login to see this link.

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

    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. :)

    Please login to see this link.|Please login to see this link.|Please login to see this link.
    Need art for your game? I'm currently available for work.
    3D Modeler, Rigging TD, Animator for hire - Please login to see this link.
    Please login to see this link.

    Quote from PixelatedPict

    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.

    Yes i agree, Mantis would get my vote and it seems to work well for Andrew the 3DC developer, i have been a long time user of 3D-Coat and the Mantis system works perfectly i think.

    Also off-topic but i just wanted to say your 3DC video tutorials are great, they helped me learn to use the program quickly.

    Edited once, last by Atom (January 22, 2012 at 8:55 PM).

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login