de:Das Test-Team-Handbuch/5 - Test-Board-Organisation•
en:The Test Team Handbook/5 - Test board organization•
es:The Test Team Handbook•
fr:The Test Team Handbook•
ru:The Test Team Handbook•
 
UnderConstruction.png
Translation to review
Don't blame the contributors, but come and help them 😎

Reference text ( Maintained text, used as reference ) :
Notes: (Ledania, 2022-03-21)

Test board organization scheme
Test board organization scheme
Test board process diagram
Test board process diagram

This document describes details how tasks on the Test team board are organized.

Contents

Theory

The board divides whole process into seven steps, with progress from left to right. Odd columns are meant for management and Non-Testers in the team. Every other column involves testing and is meant for Testers.

Every task starts in either Waiting for Yubo, Waiting for Gingo or Waiting for Atys column. It determines on which server the testing is initially placed. If the task progress (pass all server testing) it moves to right to next server or to end its lifetime as completed in the Done column.

The task remains "on server" and undertake one or more Test rounds/sessions until the all known or newly discovered issues are solved. The board organization use five main settings to indicate task details to all team members no matter of the current role.



Test Team board elements description


Board task elements

Board users

The work in the Test team is based on team members roles. Based on your current role you have chosen, you pay attention to different parts of the board and operate on different task base. The team itself consists of different type of Ryzom team members, pure testers who look for a running test, translators who work on strings, wiki project members who document changes, marketing team members who wants news for public, event team members who prepare games or scenes and developers who maintain the code. All of them can be, basically, divided into two groups.

Team members accept (use) different roles while working in the Test team. Your first step should be to tell yourself, what would you like to do with the board now. Based on that, you pay attention to different task details and different parts (columns) of the board:

After you open a desired task, based on your role you pay attention to different task details.

Some more about work in the Test team by various roles is described in Test Team roles article.

Columns (task progress)

The theory is that a new testing task travels during its lifetime from left to right when progress and right to left when troublesome. After each testing round or session it is decided if the task is ready to progress (move right on the board) or if there is more work on it (move left on the board).

Waiting for Yubo

This column contains new or actually closed tasks that will continue with testing on the Yubo server. It is a place where:

Before such task can continue for new testing on Yubo, a new test must be prepared. That means that all issues must be solved, all patches applied and all problems discussed.

Testing on Yubo

This column contains all opened tests on the Yubo server. It is a place where:

Waiting for Gingo

This column contains new or actually closed tasks that will continue with testing on the Gingo server. It is a place where

Before such task can continue for new testing on Gingo, a new test must be prepared. That means that all issues must be solved, all patches applied and all problems discussed.

Testing on Gingo

This column contains all opened tests on the Gingo or Atys BETA server. It is a place where:

Waiting for Atys

This column contains new or actually closed tasks that will continue with testing on the Atys server. It is a place where

Before such task can continue for new testing on Atys, a new test must be prepared. That means that all issues must be solved, all patches applied and all problems discussed.

Testing on Atys

This column contains all opened tests on the Atys server. It is a place where:

Done

This is a column where every task come at the end of its lifetime. Once the parent task is adjusted, testing task can be closed.

Colours (task state)

Test Team board task opened for testing
Test Team board task opened for testing
Test Team board task with known issues
Test Team board task with known issues
Test Team board task ready to be processed
Test Team board task ready to be processed
Test Team board task being adjusted by a coordinator
Test Team board task being adjusted by a coordinator

Each task can have one of various colours. This setting represents its state:

Position (task priority in current column)

Position of a task in each column tells you how important is a work on it. Higher position inside a column means higher task priority. Please ignore the task Priority settings. It belongs to team managers to set their priority. Optionally you can choose initial priority when the task arrives to new column to tell your priority guess, based on task progress, number and seriousness of issues, overall project priority...

Tag stickers (task symptoms)

Each task can have one or more stickers (tags) placed on. It represents main current task "symptoms".

Colour scheme

Tag stickers have coloured background to help you get oriented.

Commonly used tags

The list is dynamic so you can create any sticker you wish, however it is useful to have some standard list of those everyone should understand.

Deadline (task deadline in current column)

Applies to open tests only, otherwise ignore. The date and time represents when the test (round) will be closed on server. It is needed to have at least basic testing done completed due the date. Deadlines are important in case you need to prepare the change for upcoming patch or if some specific features will be activated for limited time (running events, bigger tests...).


Retrieved from "https://en.wiki.ryzom.com/w/index.php?title=The_Test_Team_Handbook/5_-_Test_board_organization&oldid=49593"