-
Notifications
You must be signed in to change notification settings - Fork 149
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
jasmine - catchExceptions option is deprecated, replace with stopOnSpecFailure #731
Comments
+1 |
although this is not a preferred solution, but we worked around this by
The file diff between these 2 is simply 2-3 lines to prevent the warnings from showing up. We also use VS extensions for chutzpah and the latest version will discover chutzpah in nuget packages and use that. So we just replace the chutzpah in nuget packages. |
This causes a issue when using Azure Build Pipelines / DevOps. The standard build pipeline re-installs all NuGet packages so they do not have to be in source control and do not become accidentally broken. The Test part of the build then sees this "error" and assumes that the tests have failed, even if all have passed (see this question). Therefore it looks like the version in NuGet needs to be updated to use at least Jasmine 2.99.1, if not 3.* to allow any Jasmine tests to be run on DevOps - Note that Microsoft specifically state Chutzpah as a testing method to use with Build Pipelines. |
I updated in 4.4.3 to fix this issue |
I am receiving the following errors in my execution of my unit tests.
I am using the latest NuGet package and have
jasmine 2.9.0
referenced in mypackage.json
file. Please let me know if there is something else I can provide.The text was updated successfully, but these errors were encountered: