How to request new testing - Revision history

Leda at 05:09, 27 May 2023

2023-05-27T05:09:13Z

Moniq: /* Test is closed */ +image

2020-04-21T12:52:41Z

‎Test is closed: +image

Moniq: /* Do the task adjustment */ +image

2020-04-21T12:51:28Z

‎Do the task adjustment: +image

Moniq: /* Issues resolved */ -image

2020-04-21T12:51:11Z

‎Issues resolved: -image

Moniq: /* Test is closed */ +images

2020-04-21T12:50:08Z

‎Test is closed: +images

Moniq: /* Test is closed */ correction

2020-04-21T12:35:41Z

‎Test is closed: correction

Moniq: /* Do the task adjustment */ list split

2020-04-21T12:25:44Z

‎Do the task adjustment: list split

Moniq: /* Do the task adjustment */ do not open

2020-04-21T12:23:50Z

‎Do the task adjustment: do not open

Moniq: /* Creating new task */ +scheme image

2020-04-09T23:28:42Z

‎Creating new task: +scheme image

Moniq: /* What happens next */ +diagram image

2020-04-09T23:27:18Z

‎What happens next: +diagram image

← Older revision		Revision as of 05:09, 27 May 2023
Line 1:		Line 1:
−	{{WIP}}	+	{{WIP}}<noinclude>{{Trad\|DE=Wie man neue Tests anfordert\|EN=How to request new testing\|palette=team\|H=1}}</noinclude>
	This document attempts to give you information about how you can request a testing to be done by the [[Test Team]]. To prepare such task is not easy and we need your cooperation and help. There are several steps we need you to do that will help team coordinators to prepare testing. First part is dedicated to steps that are necessary to undertake when a new task is created. Second part describes what will happen with your task and when your attention will be needed again.		This document attempts to give you information about how you can request a testing to be done by the [[Test Team]]. To prepare such task is not easy and we need your cooperation and help. There are several steps we need you to do that will help team coordinators to prepare testing. First part is dedicated to steps that are necessary to undertake when a new task is created. Second part describes what will happen with your task and when your attention will be needed again.

@@ Line 43: / Line 43: @@
 =Test is closed=
 When a test is closed, it does not mean the task is finished. In case there were any issues discovered during the last test, it is your turn again. The task was returned back and updated. Read all its sub-tasks to learn about known issues, that exists in three types:
 * <font style="color: red;">issue</font> - an important or critical issue that significantly affects the game play like wrong functionality, exploit or incomplete parts

@@ Line 18: / Line 18: @@
 ==Do the task adjustment==
 Next thing you need to do is to adjust the task. Please perform the following:
 * Set its colour to yellow to indicate the task is ready to be processed by a team coordinator.

← Older revision		Revision as of 12:51, 21 April 2020
Line 56:		Line 56:

	==Issues resolved==		==Issues resolved==
−	~~[[File:Tteam task new.png\|thumb\|alt=Test Team board task ready to be processed\|Test Team board task ready to be processed]]~~
	When no issues blocking the task progress remain open, the task can move to next server on right on the board and the whole process repeats for that server. In such case your only responsibility is to make sure the change is present on that new server so testing can continue. This repeats until the task gets to the last Done column.		When no issues blocking the task progress remain open, the task can move to next server on right on the board and the whole process repeats for that server. In such case your only responsibility is to make sure the change is present on that new server so testing can continue. This repeats until the task gets to the last Done column.

@@ Line 49: / Line 49: @@
 ==It is not a bug, it is a feature==
 An existing issue, especially those of <font style="color: orange;">minor</font> or <font style="color: blue;">clarify</font> type, do not necessary mean there is any work needed. It depends on the matter of the issue and your vision about the change that is subject of testing. It might happen that the test guide or testers did not understand your purposes or something they consider to be an issue is a feature after all.
@@ Line 55: / Line 56: @@
 ==Issues resolved==
 When no issues blocking the task progress remain open, the task can move to next server on right on the board and the whole process repeats for that server. In such case your only responsibility is to make sure the change is present on that new server so testing can continue. This repeats until the task gets to the last Done column.

@@ Line 44: / Line 44: @@
 When a test is closed, it does not mean the task is finished. In case there were any issues discovered during the last test, it is your turn again. The task was returned back and updated. Read all its sub-tasks to learn about known issues, that exists in three types:
 * <font style="color: red;">issue</font> - an important or critical issue that significantly affects the game play like wrong functionality, exploit or incomplete parts
-* <font style="color: orange;">minor</font> - a minor issues that must be solved but does not prevent using of the feature, for example missing translations, wrong elements layout, missing icons or
+* <font style="color: orange;">minor</font> - a minor issues that must be solved but does not prevent using of the feature, for example wrong or missing translations, wrong elements layout, missing icons or unclear instructions for players
 * <font style="color: blue;">clarify</font> - all aspects that were not understandable for testers like attributes that were not part of your details specification, unexpected behaviour or results of possible combination with other game features
 All related details are in the last [https://cloud.ryzom.com/f/36038 testing PAD] and also testers feedback or suggestions. Please review them and fix all that is possible. If something is not clear or you need more details, feel free to contact previous test guide or other team coordinator on the team chat. Once you are done with changes and those changes are available on the testing server, [[How_to_request_new_testing#Do_the_task_adjustment|do the task adjustment]] and all repeats until all issues that block task progress are solved.

@@ Line 22: / Line 22: @@
 * Add a tag sticker with a responsible developer name so we know who to contact for additional information.
 * '''Do not''' assign the task to any team member.
 * Notify team coordinators on the chat about the task

@@ Line 2: / Line 2: @@
 This document attempts to give you information about how you can request a testing to be done by the [[Test Team]]. To prepare such task is not easy and we need your cooperation and help. There are several steps we need you to do that will help team coordinators to prepare testing. First part is dedicated to steps that are necessary to undertake when a new task is created. Second part describes what will happen with your task and when your attention will be needed again.
 =Creating new task=
 First of all you need to create a task on the [https://board.ryzom.com/?controller=BoardViewController&action=show&project_id=51 &#91;Team&#93; Test board]. We understand that you also have your work to do so feel free to contact team coordinators to perform all the following steps.
@@ Line 24: / Line 25: @@
 [[File:Test board diagram.png|thumb|150px|alt=Test board process diagram|Test board process diagram]]
 =What happens next=
 Once the task is created on the board, you have to wait until one of Test team coordinators will overtake the task and prepare a test. Feel free to alert them on the team chat. Optionally you can take the [[Being a Test Team Coordinator|role of coordinator]] yourself and do necessary steps yourself. Basically, the following progress will follow these steps: