Dieses Dokument gibt Ihnen einen schnellen Überblick über die notwendigen Schritte, die Sie unternehmen müssen, um dem Test-Team beizutreten und gute Arbeit leisten zu können. Es ist mit Links zu anderen Dokumenten mit mehr Details angereichert, falls ein solcher Text existiert. Wenn Sie Fragen oder Anregungen haben, können Sie diese gerne unter #chat-general (nur für Teammitglieder zugänglich) oder #pub-general (offen für alle) stellen.
If you are willing to apply to become a member of the Testing team, please contact Tamarea, directly on Ryzom chat or by sending an e-mail to tamarea@ryzom.com. You need to get access to team tools and private chat rooms. After this step use the #t-test chat room for any questions related to testing.
More information: Get in touch with Ryzom Forge
As next you need to become familiar with tools used by the Ryzom team. For planning we use Kan Board, for collaboration we have a cloud system and internal (team) chat rooms.
More information: External team tools
The most of team work and testing is closely tight to our testing servers. You need to create two separated client installations to have access to Yubo, the developers server, Gingo, the testing server and also to beta updates for Atys server.
More information: Setting up connection to non-public Ryzom servers
Once you have access to testing servers, you need to prepare some characters to perform tests and become familiar with in-game tools for testers. It will make your life much easier.
More information: On a testing server
Your work in the Test team is mostly up to you. You are free to join any test and you can use any procedure that fits you. However there are some rules that help cooperation with others, prevents fails. You need to get familiar with our Test board where we track all existing testing tasks.
More information: Test board organization
Now you are getting to the core. Your work would be pointless if you could not provide all details from your testing. There are some tips that can help you in case you have no previous experience with a testing.
More information: Testing report tips