-
Notifications
You must be signed in to change notification settings - Fork 473
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
Support: Add interface to create ODataQueryOptions via a mock framework #1645
Comments
@ynauls #1352 (comment) may help you with your unit testing - not nice, but it works :) |
@freeranger, thank you, i saw that earlier and it works. I would def like some support out of the box :) |
kccarter76
added a commit
to kccarter76/WebApi
that referenced
this issue
Jun 29, 2020
…he injection occurs
kccarter76
added a commit
to kccarter76/WebApi
that referenced
this issue
Jun 29, 2020
kccarter76
added a commit
to kccarter76/WebApi
that referenced
this issue
Jun 30, 2020
kccarter76
added a commit
to kccarter76/WebApi
that referenced
this issue
Jun 30, 2020
OData#1645 unit test added and all unit tests passing
kccarter76
added a commit
to kccarter76/WebApi
that referenced
this issue
Jul 1, 2020
…ings base on vs studio.
2 tasks
kccarter76
added a commit
to kccarter76/WebApi
that referenced
this issue
Jul 1, 2020
kccarter76
added a commit
to kccarter76/WebApi
that referenced
this issue
Jul 1, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add interface/support to unit test ODataQueryOptions with a mock framework. I implemented logic using the following sample from here Server-Driven Paging. The code works, however, i am unable to unit test due to complexity of creating ODataQueryOptions
Assemblies affected
Microsoft.AspNet.OData.Query (7.0.1)
Reproduce steps
Create unit test sample outside "Microsoft.AspNet.OData" package.
Expected result
Able to easily create unit test for logic passing in a ODataQueryOptions
Actual result
unable to create unit tests
The text was updated successfully, but these errors were encountered: