-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Testing
Other than development and localisation, another important aspect of this project is testing. It helps us track down bugs, either original ones or the ones introduced by the project.
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.
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.
- Visit the issue tracker, and search through the list of issues. We have a lot of people playing the game and others might have came across the same issue as you. If you find your issue already, feel free to leave a comment (especially if it's one of the rare ones and got us stumped), and then you are done with that issue. If however you didn't find it, continue reading.
- Make a new issue by clicking on the green new issue button, and fill out the title and the comment.
- 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 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.
Thanks for reading, and happy hunting :)
- Home
- FAQ & Common Issues
- Roadmap
- Installation
- Building
- Features
- Development
- Benchmarking & stress testing OpenRCT2
- Coding Style
- Commit Messages
- Overall program structure
- Data Structures
- CSS1.DAT
- Custom Music and Ride Music Objects
- Game Actions
- G1 Elements Layout
- game.cfg structure
- Maps
- Music Cleanup
- Objects
- Official extended scenery set
- Peep AI
- Peep Sprite Type
- RCT1 ride and vehicle types and their RCT2 equivalents
- RCT12_MAX_SOMETHING versus MAX_SOMETHING
- Ride rating calculation
- SV6 Ride Structure
- Settings in config.ini
- Sizes and angles in the game world
- Sprite List csg1.dat
- Sprite List g1.dat
- Strings used in RCT1
- Strings used in the game
- TD6 format
- Terminology
- Track Data
- Track Designs
- Track drawers, RTDs and vehicle types
- Track types
- Vehicle Sprite Layout
- Widget colours
- Debugging OpenRCT2 on macOS
- OpenGL renderer
- Rebase and Sync fork with OpenRCT2
- Release Checklist
- Replay System
- Using minidumps from crash reports
- Using Track Block Get Previous
- History
- Testing