From EncyclopAtys
(Created page with "{{WIP}} {{Trad |DE =Test Team |EN =Test Team |ES =Test Team |FR =Test Team |RU =Test Team |H = |palette=Grey }} # Joining the Test team:<br /> https://cloud.ryzom.com/f/34...") |
m |
||
(49 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
− | |||
{{Trad | {{Trad | ||
− | |DE =Test Team | + | |DE =Das Test-Team-Handbuch|DEs=4 |
− | |EN =Test Team | + | |EN =The Test Team Handbook|ENs=0 |
− | |ES =Test Team | + | |ES =The Test Team Handbook|ESs=5 |
− | |FR = | + | |FR =Manuel de l'équipe de test|FRs=5 |
− | |RU =Test Team | + | |RU =The Test Team Handbook|RUs=5 |
|H = | |H = | ||
|palette=Grey | |palette=Grey | ||
}} | }} | ||
+ | This document gives you quick overview about necessary steps you must undertake to join the [[Test Team]] and be able to do good work. It is enriched with links to other documents with more details in case such text exists. If you have any questions or suggestions, feel free ask on [https://chat.ryzom.com/group/chat-general #chat-general] (accessible for team members only) or [https://chat.ryzom.com/channel/pub-general #pub-general] (open for everybody). | ||
− | + | =Step 1: Apply to join= | |
− | + | If you are willing to apply to become a member of the Testing team, please contact Tamarea, directly on [https://chat.ryzom.com/direct/Tamarea Ryzom chat] or by sending an e-mail to [mailto:tamarea@ryzom.com tamarea@ryzom.com]. You need to get access to team tools and private chat rooms. After this step use the [https://chat.ryzom.com/group/t-test #t-test] chat room for any questions related to testing. | |
− | |||
− | # - | ||
+ | '''More information:''' [[The Test Team Handbook/1 - Get in touch with Ryzom Forge|Get in touch with Ryzom Forge]] | ||
+ | |||
+ | =Step 2: Get familiar with team tools= | ||
+ | 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:''' [[The Test Team Handbook/2 - External team tools|External team tools]] | ||
+ | |||
+ | =Step 3: Configure Ryzom clients= | ||
+ | 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:''' [[The Test Team Handbook/3 - Setting up connection to non-public Ryzom servers|Setting up connection to non-public Ryzom servers]] | ||
+ | |||
+ | =Step 4: Prepare for testing= | ||
+ | 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:''' [[The Test Team Handbook/4 - On a testing server|On a testing server]] | ||
+ | |||
+ | =Step 5: Choose a test= | ||
+ | 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:''' [[The Test Team Handbook/5 - Test board organization|Test board organization]] | ||
+ | |||
+ | =Step 6: Start testing= | ||
+ | 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:''' [[The Test Team Handbook/6 - Testing report tips|Testing report tips]] | ||
+ | |||
+ | |||
+ | {{Portal|Forge}} | ||
[[Category:Test|Test team]] | [[Category:Test|Test team]] | ||
[[Category:Tutorials|Test team]] | [[Category:Tutorials|Test team]] | ||
− | Category:Test | + | [[Category:Testing Team]] |
− | Category:Tutorials | + | [[Category:Ryzom Team]] |
+ | [[Category:Test]] | ||
+ | [[Category:Tutorials]] |
Latest revision as of 10:39, 22 March 2022
This document gives you quick overview about necessary steps you must undertake to join the Test Team and be able to do good work. It is enriched with links to other documents with more details in case such text exists. If you have any questions or suggestions, feel free ask on #chat-general (accessible for team members only) or #pub-general (open for everybody).
Contents
Step 1: Apply to join
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
Step 2: Get familiar with team tools
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
Step 3: Configure Ryzom clients
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
Step 4: Prepare for testing
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
Step 5: Choose a test
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
Step 6: Start testing
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