1
0
mirror of https://github.com/OpenRCT2/OpenRCT2 synced 2026-01-28 09:14:58 +01:00

Updated Testing (markdown)

danidoedel
2016-01-31 20:09:09 +01:00
parent 641740892e
commit 562184ec7f

@@ -4,7 +4,7 @@ Other than development and localisation, another important aspect of this projec
To get started with testing, download a pre-built version of the game or build from source. Once you have the game running, just play it as you would normally play RCT2. If you spot an issue note it down, remember how you made it happen, try to recreate and then get ready to report it.
##Reporting issues/bugs
OpenRCT2 uses the GitHub issues tracker to allow the community to let us know if there is something wrong. You can find the issue tracker at https://github.com/IntelOrca/OpenRCT2/issues
OpenRCT2 uses the GitHub issues tracker to allow the community to let us know if there is something wrong. You can find the issue tracker at https://github.com/OpenRCT2/OpenRCT2/issues
Steps to reporting the issue are as follows:
* Check the known issues either here on the wiki or the known issues txt included in the game package. If the issue is there, there is probably no need to report it.
@@ -13,8 +13,9 @@ Steps to reporting the issue are as follows:
* When creating a new issue, it really helps if you give it a meaningful title, and a good description. A good description will have:
* Description of the problem, so we can understand what it is
* A screenshot or a video of the problem (GitHub Markdown supports image and video embeds and links)
* Upload a saved game if possible to replicate the bug
* Reproduction steps. This is very important, as knowing how to make the issue appear on our sides, really helps us track down the cause.
* Version of the game, prebuilt (from where OpenRCT.net or OpenRCT2.com) or built from source
* Version of the game you are running and where you downloaded it from, e.g. openrct2.org develop 0.0.4 build d86bf8f
If you provide us with these details, we'll be able to squash the bugs faster.