You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 8, 2023. It is now read-only.
My recent PR #108 enables the test runner to take in an optional dictionary with NUnit test context parameters along with the test assembly. It solves the problem of no being able to set test context parameters, but the users have to make the dictionaries and pass it to NUnit.Xamarin.
I think a more direct way is to enable the test runner parsing command line parameters. In addition, it would be better if users can set the test options (AutoRun, ResultFilePath, tcp parameters...) from command line as well.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
My recent PR #108 enables the test runner to take in an optional dictionary with NUnit test context parameters along with the test assembly. It solves the problem of no being able to set test context parameters, but the users have to make the dictionaries and pass it to NUnit.Xamarin.
I think a more direct way is to enable the test runner parsing command line parameters. In addition, it would be better if users can set the test options (AutoRun, ResultFilePath, tcp parameters...) from command line as well.
The text was updated successfully, but these errors were encountered: