-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Integration test error post upgrade to 4.0.56-beta.4 #135
Comments
I'm getting the same issue with integration tests on 4.0.56-beta.4. |
@davidjsteele did you ever find a solution for this? I'm still struggling to get integration tests to run with ExecuteHttpAsync |
@mmeckes if memory serves this was actually down to a problem with discovery of app.config files as part of ioc resolution. If you can provide more info might be able to help |
@davidjsteele any help appreciated. I know it's been a while since you raised this issue.
As soon as I call ExecuteHttpAsync I the error below where the provider is not getting injected in correctly. It does feel like there is some config that is off that is stopping it from resolving the dependencies correctly, but I'm struggling to track it down.
|
Hi,
Having trouble running my integration tests after upgrading to latest version of FM and Azure SDK running on .net Core 3.1.
App runs fine, just the tests that are broken.
Any insight would be much appreciated.
Thanks
The text was updated successfully, but these errors were encountered: