Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Tests' folder missing when added via VCC #55

Open
sam-ln opened this issue Nov 26, 2022 · 4 comments
Open

'Tests' folder missing when added via VCC #55

sam-ln opened this issue Nov 26, 2022 · 4 comments
Assignees

Comments

@sam-ln
Copy link

sam-ln commented Nov 26, 2022

When installing ClientSim into a VRC World Project via the Creator Companion, it is missing the 'Tests' folder, making it impossible to follow the Instructions for Automated Testing. A workaround is to manually install ClientSim from git by opening Unity Package Manager -> Add package from git URL.. -> enter https://github.com/vrchat-community/ClientSim.git?path=Packages/com.vrchat.ClientSim

@momo-the-monster
Copy link
Collaborator

Thanks for pointing this out, @sam-ln. Unfortunately, Unity does not properly ignore the test assemblies for embedded packages, so we had to strip out these files from the general releases to avoid adding the test assemblies to everyone's projects (verified by Unity Support). We'll need to update the documentation with the info you have above or a similar workaround.

@sam-ln
Copy link
Author

sam-ln commented Dec 1, 2022

@momo-the-monster Thanks for your answer! I think it would be more intuitive for creators to simply remove the TestAssembly themselves (if they are even bothered by it showing up in the Test Runner), than having to pull the ClientSim from a different source just to get the Test features. That being said, the Test Runner currently gets populated by Udon Graph Editor Tests in every fresh project anyways.

@Happyrobot33
Copy link

this is unfortunate, was just starting to look into unit tests :/

@sam-ln
Copy link
Author

sam-ln commented May 5, 2023

@Happyrobot33 Using the work-around in my first message, unit testing with Edit-Mode tests works quite well. Unfortunately Play-Mode tests do not (see #63).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants