Skip to content
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

Remove QueryBugsTest class #1015

Closed
AndriySvyryd opened this issue Nov 6, 2014 · 0 comments · Fixed by #32542
Closed

Remove QueryBugsTest class #1015

AndriySvyryd opened this issue Nov 6, 2014 · 0 comments · Fixed by #32542
Assignees
Labels
area-test merge-impact Code formatting or other changes that may impact future code merges punted-for-3.1 punted-for-7.0 Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints. type-cleanup
Milestone

Comments

@AndriySvyryd
Copy link
Member

The tests contained in this class should be moved to the appropriate classes according to the scenario they target.

@smitpatel smitpatel modified the milestones: MQ, 7.0.0 Jan 21, 2022
@ajcvickers ajcvickers modified the milestones: 7.0.0, MQ Apr 23, 2022
@ajcvickers ajcvickers added punted-for-7.0 Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints. and removed propose-punt labels Apr 23, 2022
@ajcvickers ajcvickers added the merge-impact Code formatting or other changes that may impact future code merges label Sep 7, 2022
@smitpatel smitpatel removed their assignment Nov 10, 2022
maumar added a commit that referenced this issue Dec 7, 2023
- Moving tests from QueryBugsTests to other more appropriate places (either AssertQuery - enabled or proper AdHoc suites)
- Adding a bunch of AdHoc suites (navigations, splitting, filters, weird mappings)
- Unified format of AdHoc tests

Resolves #1015
maumar added a commit that referenced this issue Dec 7, 2023
- Moving tests from QueryBugsTests to other more appropriate places (either AssertQuery - enabled or proper AdHoc suites)
- Adding a bunch of AdHoc suites (navigations, splitting, filters, weird mappings)
- Unified format of AdHoc tests

Resolves #1015
maumar added a commit that referenced this issue Dec 7, 2023
- Moving tests from QueryBugsTests to other more appropriate places (either AssertQuery - enabled or proper AdHoc suites)
- Adding a bunch of AdHoc suites (navigations, splitting, filters, weird mappings)
- Unified format of AdHoc tests

Resolves #1015
maumar added a commit that referenced this issue Dec 7, 2023
- Moving tests from QueryBugsTests to other more appropriate places (either AssertQuery - enabled or proper AdHoc suites)
- Adding a bunch of AdHoc suites (navigations, splitting, filters, weird mappings)
- Unified format of AdHoc tests

Resolves #1015
maumar added a commit that referenced this issue Dec 8, 2023
- Moving tests from QueryBugsTests to other more appropriate places (either AssertQuery - enabled or proper AdHoc suites)
- Adding a bunch of AdHoc suites (navigations, splitting, filters, weird mappings)
- Unified format of AdHoc tests

Resolves #1015
maumar added a commit that referenced this issue Dec 8, 2023
- Moving tests from QueryBugsTests to other more appropriate places (either AssertQuery - enabled or proper AdHoc suites)
- Adding a bunch of AdHoc suites (navigations, splitting, filters, weird mappings)
- Unified format of AdHoc tests

Resolves #1015
maumar added a commit that referenced this issue Dec 8, 2023
- Moving tests from QueryBugsTests to other more appropriate places (either AssertQuery - enabled or proper AdHoc suites)
- Adding a bunch of AdHoc suites (navigations, splitting, filters, weird mappings)
- Unified format of AdHoc tests

Resolves #1015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-test merge-impact Code formatting or other changes that may impact future code merges punted-for-3.1 punted-for-7.0 Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints. type-cleanup
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants