-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Cleanup functional tests / Structure them like libraries tests #46810
Conversation
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @directhex Issue Details
|
78c888a
to
9837748
Compare
# Conflicts: # src/tests/FunctionalTests/wasm/AOT/console/Wasm.Aot.Console.Test.csproj # src/tests/FunctionalTests/wasm/Interpreter/browser/Wasm.Interpreter.Browser.Test.csproj # src/tests/FunctionalTests/wasm/Interpreter/console/Wasm.Interpreter.Console.Test.csproj
src/tests/FunctionalTests/wasm/AOT/browser/Wasm.Aot.Browser.Test.csproj
Outdated
Show resolved
Hide resolved
# Conflicts: # .config/dotnet-tools.json # eng/Version.Details.xml # eng/Versions.props
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.
Just a couple questions, but looks great otherwise!
# Conflicts: # src/tests/FunctionalTests/iOS/Simulator/AOT/iOS.Simulator.Aot.Test.csproj
You should now be able to run the functional tests locally the same way as running the libraries tests.
Example:
./dotnet.sh build /t:Test src/tests/FunctionalTests/wasm/Interpreter/console/ /p:TargetOS=Browser /p:TargetArchitecture=wasm /p:Configuration=Release