-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
PrimeTweenManager not created when running multiple PlayMode tests #83
Comments
PrimeTweenManager is created once before all other scripts (BeforeSceneLoad) and should be never destroyed after that because of DontDestroyOnLoad(). When the first PlayMode test is executed, PrimeTweenManager should be created and all other following tests will use the same PrimeTweenManager instance. Is this not the case for you? One potential corner case I can imagine is that if any of your tests exit the PlayMode by doing something like PrimeTween comes with a lot of runtime tests and you can enable them by adding these lines to your manifest.json file. Can you check if they work for you correctly?
|
I was able to identify the issue after your input. My PlayMode tests use Zenject's SceneTestFixture, and its |
When multiple PlayMode tests are run (by "Run All" or "Run Selected" with multiple selected tests), the PrimeTweenManager game object is only created in the first test. The following ones do not have the PrimeTweenManager created.
The text was updated successfully, but these errors were encountered: