Testing: Difference between revisions
Jump to navigation
Jump to search
Hhyyrylainen (talk | contribs) No edit summary |
Hhyyrylainen (talk | contribs) (trying to lay out the testing workflow) |
||
| Line 4: | Line 4: | ||
Next see especially the [[Testing_Checklist|Testing Checklist]]. | Next see especially the [[Testing_Checklist|Testing Checklist]]. | ||
== General Testing Workflow == | |||
The general workflow for testing is as follows: | |||
* Find a build to test (for example by subscribing to Github notifications or asking other team members) | |||
* Use the launcher (see: [[Linking_the_Launcher|Linking the Launcher]]) to download and play that build. It's very important to make sure you are playing the right version. Check that the commit hash the launcher says when starting the devbuild matches what Github reports as the newest commit for the pull request (PR) or other code to be tested. | |||
* Try out the new features / fixes in the build. Or if you are playing the BOTD or a version from master, try to find any bugs and issues in general. | |||
* For PRs you should report the issues found as comments on the original PR. For BOTD or master testing, new issues should be opened on the [https://github.com/Revolutionary-Games/Thrive/issues Thrive repo] (or [https://github.com/Revolutionary-Games/Thrive-Launcher/issues Launcher] if the bug is there). But before opening existing issues need to be searched to not make duplicate issues. | |||
Revision as of 16:00, 10 August 2021
This is the wiki page for the testing team. The testing team is responsible for testing new versions of Thrive and new pull requests to make sure they work correctly.
Next see especially the Testing Checklist.
General Testing Workflow
The general workflow for testing is as follows:
- Find a build to test (for example by subscribing to Github notifications or asking other team members)
- Use the launcher (see: Linking the Launcher) to download and play that build. It's very important to make sure you are playing the right version. Check that the commit hash the launcher says when starting the devbuild matches what Github reports as the newest commit for the pull request (PR) or other code to be tested.
- Try out the new features / fixes in the build. Or if you are playing the BOTD or a version from master, try to find any bugs and issues in general.
- For PRs you should report the issues found as comments on the original PR. For BOTD or master testing, new issues should be opened on the Thrive repo (or Launcher if the bug is there). But before opening existing issues need to be searched to not make duplicate issues.