Before deploying your ViRSE plugin, you must first test it, in the same way it’ll be used with students.

<aside> ⚠️ Testing is critical! There will always be bugs hiding in your application, don’t assume you got everything perfect the first time, because you definitely didn’t!

You should test early, and test often. Ideally, your plugin’s development should consist of small incremental cycles: Add or change a small feature, test it, and repeat

</aside>

You must do test run-throughs of all functionality in your plugin in the following ways

1. Test everything in 2D mode
2. Test everything in VR mode (may require deploying to the test server and playing on a VR-enabled machine if your machine doesn’t support VR)
3. Test everything in multiplayer

Testing in multiplayer

The best way to conduct multiplayer testing is to deploy your plugin to the test server and run through it with other real people in real multiplayer across different machines. You are strongly recommended to test your application using this method at least a few times before deploying with students, however, you also want a faster, more lightweight way of conducting multiplayer testing so you can test more often.

ParrelSync is a third-party package used by ViRSE that allows you to open your project twice on the same machine (a second monitor can be particularly useful here, so you can have each instance of your project open on each one)

1. Find the “ParrelSync” dropdown at the top of the Unity window.
2. Click ParrelSync, Clones Manager
3. Click “Add new clone”, it will take a moment for ParrelSync to make a copy of your project
4. Click “Open in new editor”
5. This will now open a clone of your project in a separate Unity window, open your scene in both editors, and hit play on both, you should now be in multiplayer with yourself!

<aside> ⚠️ When making changes to your scene or scripts, make sure you do this in your original project, not the clone! Any changes made to the clone project will be lost.

</aside>