-
-
Notifications
You must be signed in to change notification settings - Fork 140
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
Add standalone testmode support #219
Conversation
Add test for IL2CPP.
I'm not sure why the first test is failing, but I fixed the other tests I added. |
@webbertakken @davidmfinol Can you please take a look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Though I have little context about the specifics.
Can you confirm both?
- This works
- This does not break previous flows
dist/test-standalone-scripts/Assets/Player/UnityTestRunnerAction/TestRunCallback.cs
Outdated
Show resolved
Hide resolved
I'm also seeing some errors in the workflows: -----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/UnityEngine.TestRunner.dll
Microsoft (R) Visual C# Compiler version 2.9.1.65535 (9d34608e)
Copyright (C) Microsoft Corporation. All rights reserved.
Library/PackageCache/[email protected]/UnityEngine.TestRunner/NUnitExtensions/Runner/UnityLogCheckDelegatingCommand.cs(115,57): error CS0246: The type or namespace name 'TestMustExpectAllLogsAttribute' could not be found (are you missing a using directive or an assembly reference?)
Library/PackageCache/[email protected]/UnityEngine.TestRunner/NUnitExtensions/Runner/UnityLogCheckDelegatingCommand.cs(124,63): error CS0246: The type or namespace name 'TestMustExpectAllLogsAttribute' could not be found (are you missing a using directive or an assembly reference?)
Library/PackageCache/[email protected]/UnityEngine.TestRunner/NUnitExtensions/Runner/UnityLogCheckDelegatingCommand.cs(136,65): error CS0246: The type or namespace name 'TestMustExpectAllLogsAttribute' could not be found (are you missing a using directive or an assembly reference?)
-----CompilerOutput:-stderr----------
-----EndCompilerOutput---------------
- Finished compile Library/ScriptAssemblies/UnityEngine.TestRunner.dll
Library/PackageCache/[email protected]/UnityEngine.TestRunner/NUnitExtensions/Runner/UnityLogCheckDelegatingCommand.cs(115,57): error CS0246: The type or namespace name 'TestMustExpectAllLogsAttribute' could not be found (are you missing a using directive or an assembly reference?)
Library/PackageCache/[email protected]/UnityEngine.TestRunner/NUnitExtensions/Runner/UnityLogCheckDelegatingCommand.cs(124,63): error CS0246: The type or namespace name 'TestMustExpectAllLogsAttribute' could not be found (are you missing a using directive or an assembly reference?)
Library/PackageCache/[email protected]/UnityEngine.TestRunner/NUnitExtensions/Runner/UnityLogCheckDelegatingCommand.cs(136,65): error CS0246: The type or namespace name 'TestMustExpectAllLogsAttribute' could not be found (are you missing a using directive or an assembly reference?)
[ScriptCompilation] Recompiling all scripts because: Reload of assemblies failed
- Starting compile Library/ScriptAssemblies/UnityEngine.TestRunner.dll Not sure if they were introduced in this PR or not, but we can't merge if we're blind. |
…on/TestRunCallback.cs Co-authored-by: Webber Takken <[email protected]>
That's weird. The tests passed when I ran them in my fork. https://github.com/timcassell/unity-test-runner/actions/runs/4748246522 |
Yes, details under additional info in the PR description. |
@webbertakken I think those failures are Unity's fault (the only change in the project in those workflows is the TestFramework version update). I changed the workflows to use 2019.4.40f1 which seems more stable. About the other failing test, any idea what this is about? output
|
Looking at vercel/next.js#38530 with the same error, it appears that syntax requires node 14 or higher. The test is using |
Tests seem to be passing. Still looks good to me. Perhaps Andrew or David could have another look and merge it if they're also on board. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I'm using the
|
@joaoborks A new version with this feature has not been released yet. You can try it with
or for the specific commit
Also note that your |
Thanks @timcassell, it worked with the commit hash. Is there any ETA on the new release version? |
Resolves #208.
Changes
testMode: standalone
now builds the player with tests (StandaloneLinux64
orStandaloneWindows64
) and runs it directly. This is useful for running tests in the IL2CPP runtime (of course it's not restricted to IL2CPP).Checklist
Additional Info
Requires Unity 2019.2 or newer and Test Framework 1.0.15 or newer.
testmode: all
still only runseditmode
andplaymode
(so as to not break existing users).I got a working test run here. I was unable to test it on a Windows runner due to #200.