Add support to ExecuteDelete and ExecuteUpdate #81
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Details
Add Support for ExecuteDelete, ExecuteUpdate, ExecuteDeleteAsync, and ExecuteUpdateAsync in MockQueryable Library
Description
This PR introduces support for mocking the ExecuteDelete, ExecuteUpdate, ExecuteDeleteAsync, and ExecuteUpdateAsync methods in the MockQueryable library. These methods allow for both synchronous and asynchronous deletion and updating of entities using expressions, now fully integrated into the mocking process for EF Core's IQueryable-based testing.
Changes include:
Related Issue
This PR addresses the need to support EF Core 7’s new ExecuteDelete/ExecuteDeleteAsync and ExecuteUpdate/ExecuteUpdateAsync methods in unit tests, enabling developers to simulate bulk delete and update operations without direct access to the database.
Related Issue: #66
How Has This Been Tested
Checklist