= Confirm an Issue Ready for ingame testing? Get a predictable game-state and start picking up an issue from "Open / Validated". == Claim it {F104, size=full} Open one or two issues in a second tab (usually ctrl + click). {F98, size=full} Select "Reassign / Claim" on the new input screen (red arrow). Add yourself in the "Assigned to" (green arrow) field. A comment is optional. == Test it Get in the latest dev-build and start with the supplied steps to reproduce the issue. = Confirmed Issue happens as described == Update workflow Drag it from "Open" to "Confirmed / Validated" {F108, size=full} == Add the result When you were testing a single issue or needed to adjust something to make it happen, its easiest to add your outcome directly {F106, size=full} Now update/add the testing results {F110} Make sure you have the correct build in the field. Type only the version number in the last tested version field, nothing else. Also add you and the people that tested together with you in the "assigned tester" field. == Send your confirmed issues to development In case you confirmed more than one issue in your testing run and they all were happening exactly as described, you can confirm them in one pass. If you do not own all tasks in that column, filter the others {F114, size=full} and go to the confirmed "workflow column" and open the drop-down. {F112, size=full} Now select "Batch edit Tasks.." Check the list on top, to make sure you have the issues in you want. Now adjust the actions list like this: {F116, size=full} Change Status: in queue (Game) Now hit "Update Tasks" Herald will see the task, pick it up, and adjust workflows accordingly. You do not have to care about other settings in the issue. = Failed to reproduce Issue failed to reproduce (more content to come here)

= Confirm an Issue Ready for ingame testing? Get a predictable game-state and start picking up an issue from "Open / Validated". == Claim it {F104, size=full} Open one or two issues in a second tab (usually ctrl + click). {F123, size=full} Select "Reassign / Claim" on the new input screen (red arrow). Add yourself in the "Assigned to" (green arrow) field. A comment is optional, as this only notes your intention to pick this up, and shows others they can pick up the next one. NOTE: A claim is only done on status change. You cannot take over a claimed issue if it's not older than 3 days, contact the assignee if you want to take it up faster. == Test it Get in the **latest dev-build** and start with the supplied steps to reproduce the issue. = Result: Confirmed Issue happens as described == Update workflow Drag it from "Open / Validated" to "Confirmed" {F108, size=full} == Add the result When you were testing a single issue or needed to adjust something to make it happen, its easiest to add your outcome directly {F106, size=full} Make sure to add a **How-to-reproduce** section to either the description or your comment (preferable: description) {F1967, size=full} Now update/add the testing results {F110, size=full} Make sure you have the correct build in the field. Type only the version number in the last tested version field, nothing else. ~~Also add you and the people that tested together with you in the "assigned tester" field.~~ **(The field "Assigned Tester" is currently hidden due to a [[ https://secure.phabricator.com/T8836 | bug in phabricator ]] )** == Send your confirmed issues to development Edit the task again after moving it to the confirmed column. Scroll to the end and alter the status to "in queue (game)" for game related issues Herald will see the task, pick it up, and adjust workflows accordingly. You do not have to care about other settings in the issue. = Result: Failed to reproduce Issue failed to reproduce Think about possible factors the user may have had different from your environment. Take the following factors into account: - Operating System (File-Access, 'Does not load') - Java Version (Weird error-messages you didn't ever see before) - Hardware (Video glitches of all kind, variable performance for no reason) - Messed up client (Mods, manually deleted files, corrupted universe) Do not close or reject the issue directly, as this may get the user upset, and he/she may not even know its maybe a fault on his side. This will lead to them blaming 'us' or 'the game' for his own fault. Much better way is to ask the user for feedback about this Read [[ http://phab.starma.de/w/tester/issue_navigation/feedback/ | here ]] how to do this.

= Confirm an Issue Ready for ingame testing? Get a predictable game-state and start picking up an issue from "Open / Validated". == Claim it {F104, size=full} Open one or two issues in a second tab (usually ctrl + click). {F98{F123, size=full} Select "Reassign / Claim" on the new input screen (red arrow). Add yourself in the "Assigned to" (green arrow) field. A comment is optional, as this only notes your intention to pick this up, and shows others they can pick up the next one. A comment is optionalNOTE: A claim is only done on status change. You cannot take over a claimed issue if it's not older than 3 days, contact the assignee if you want to take it up faster. == Test it Get in the **latest dev-build** and start with the supplied steps to reproduce the issue. = Result: Confirmed Issue happens as described == Update workflow Drag it from "Open" to "Confirmed / Validated" / Validated" to "Confirmed" {F108, size=full} == Add the result When you were testing a single issue or needed to adjust something to make it happen, its easiest to add your outcome directly {F106, size=full} Make sure to add a **How-to-reproduce** section to either the description or your comment (preferable: description) {F1967, size=full} Now update/add the testing results {F110, size=full} Make sure you have the correct build in the field. Type only the version number in the last tested version field, nothing else. ~~Also add you and the people that tested together with you in the "assigned tester" field.~~ Also add you and the people that tested together with you in the "assigned tester" field.**(The field "Assigned Tester" is currently hidden due to a [[ https://secure.phabricator.com/T8836 | bug in phabricator ]] )** == Send your confirmed issues to development In case you confirmed more than one issue in your testing run and they all were happening exactly as described, you can confirm them in one passEdit the task again after moving it to the confirmed column. If you do not own all tasks in that columnScroll to the end and alter the status to "in queue (game)" for game related issues Herald will see the task, filter the others {F114,pick it up, and adjust workflows accordingly. size=full}You do not have to care about other settings in the issue. and go to the confirmed "workflow column" and open the drop-down.= Result: Failed to reproduce {F112, size=full}Issue failed to reproduce Now select "Batch edit Tasks.." Check the list on top, to make sure you have the issues in you want. Now adjust the actions list like this:Think about possible factors the user may have had different from your environment. Take the following factors into account: - Operating System (File-Access, 'Does not load') {F116, size=full} - Java Version (Weird error-messages you didn't ever see before) Change Status: in queue (Game - Hardware (Video glitches of all kind, variable performance for no reason) Now hit "Update Tasks" Herald will see the task - Messed up client (Mods, manually deleted files, pick it up, and adjust workflows accordingly. You do not have to care about other settings in the issue. = Failed to reproducecorrupted universe) Do not close or reject the issue directly, as this may get the user upset, and he/she may not even know its maybe a fault on his side. Issue faileThis will lead to reproducethem blaming 'us' or 'the game' for his own fault. (more content to come here) Much better way is to ask the user for feedback about this Read [[ http://phab.starma.de/w/tester/issue_navigation/feedback/ | here ]] how to do this.