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
Currently, integration tests (OATS tests) only work with using local project references. It would be great if they could also be used to validate packages uploaded to NuGet. Then we could run the test suite after each new package upload.
Describe the solution you'd like:
Some configuration setting that allows to let OATS tests run against published NuGet packages instead of local project reference. It should be possible to specify the version of the package.
Describe alternatives you've considered.
Currently, those smoke tests for uploaded NuGet packages have to be done manually.
The text was updated successfully, but these errors were encountered:
Feature Request
Is your feature request related to a problem?
Currently, integration tests (OATS tests) only work with using local project references. It would be great if they could also be used to validate packages uploaded to NuGet. Then we could run the test suite after each new package upload.
Describe the solution you'd like:
Some configuration setting that allows to let OATS tests run against published NuGet packages instead of local project reference. It should be possible to specify the version of the package.
Describe alternatives you've considered.
Currently, those smoke tests for uploaded NuGet packages have to be done manually.
The text was updated successfully, but these errors were encountered: