-
Notifications
You must be signed in to change notification settings - Fork 6
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
AzDevOpsProject: Integration tests fail with non-terminating error #18
Comments
@SphenicPaul do you know that is going on here? 🤔 |
I have a branch here that enable the integration tests https://github.com/dsccommunity/AzureDevOpsDsc/tree/f/enable-integration-tests. Will merge into main once the integration tests does not fail. |
@johlju - There are a few resources that do not have any Azure DevOps API support for updating the resource in particular ways (e.g. updating a Project resource from using The error/exception is thrown if the specific operation is invalid - e.g. I'm not clear why it's not being trapped/caught at present, but I was pondering (during development) about making use of I'll try and take a look at this although it might be later in the week or next weekend - I need to trace through the code execution path again as there are a few base and inherited classes and functions. I'm not initially sure why the |
Using |
@johlju - I got to the bottom of this and should be resolved with PR #20. I've run the integration tests in my own area/organization and these have run through without the same non-terminating error as before. Not sure if you want to merge this into It's probably worth focusing on #9 next (getting integration build into the pipeline) as these PRs will become a little convoluted/difficult switching the build config in and out when contributing. |
When running the integration tests some tests fail with non-terminating error make Pester think the test passed thus not failing the pipeline.
https://dev.azure.com/dsccommunity/AzureDevOpsDsc/_build/results?buildId=3711&view=logs&j=893fd6d3-ee14-5383-e15d-24a2acc7f145&t=417fa350-1299-5d83-5f55-4c06f3da5c2a
The text was updated successfully, but these errors were encountered: