This page details how to test new Decky Loader builds and Decky plugins. Make sure you have joined our Discord server for easy communication with other testers. https://decky.xyz/discord
Make sure to note what SteamOS update channel(s) you are using and what branch(es) (Release, Pre-Release or in rare cases as requested by a Loader developer: a custom binary) while you're testing a plugin. You can test on multiple branches, just make sure to tell us and the plugin developer so it can count towards sending their plugin to the production store!
In order to test a plugin, you will need to swap over to the testing store in the Decky Loader settings.
Once you've swapped over to the testing store, you can install the latest uploaded version of a plugin currently in the queue for testing. Plugins are submitted here.
Here's a view that will help you to determine what plugins need testing. Anything that is marked as "Ready for Review", "In Review" or above are ready for testing. Testing an "In Progress" plugin is fine, but the review many need to be redone at a later time.
Once a plugin is submitted/a plugin has an update submitted, it needs to meet a basic functionality evaluation by users. At the link you found above find the pull request for the relevant plugin submission or plugin update you want to test. Install the plugin from the testing store and begin using it, really try to break it!
If you want to install other non-testing plugins, simply swap back to the main store in Loader settings at any time!
Once you feel you've completely tested the features of a plugin, you should now submit a testing report, otherwise all your effort has been for naught! Since you've already noted what SteamOS update channel(s) and Decky Loader branch(es) you used while testing this should be easy!
Based off of this format:
Decky version(s), SteamOS version(s)
A) Any major blocking issues that you encountered, if any.
B) Any minor issues that you encountered (usually cosmetic, don't harm functionality).
C) A list of currently installed plugins (Name and version preferred)
(This list is needed due to potential conflicts between plugins etc).
D) Yay/nay on to send to the production store or if it requires more testing.
Once you've filed your report as a comment on the PR, we can either mark a plugin as being tested on a SteamOS update channel or as requiring a fix, or request more information from yourself or the plugin developer as needed.
Thanks for taking the time to help plugins make it to the store faster and easier, Plugin Developers greatly appreciate it.
New Decky Loader updates require review from a Decky Loader developer and an unaffiliated tester. This allows us to easily check both the code and functionality respectively. To get started testing new features, here's a basic walkthrough.
sudo systemctl stop plugin_loader to disable Decky Loader until restart.chmod 777 ~/homebrew/services/PluginLoader to make sure your Decky Loader runs correctly.