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

Move Design tests to Microsoft.EntityFrameworkCore.Specification.Tests #32315

Open
AndriySvyryd opened this issue Nov 16, 2023 · 2 comments
Open
Assignees
Milestone

Comments

@AndriySvyryd
Copy link
Member

Microsoft.EntityFrameworkCore.Design.Tests should only contain tests that don't connect to the database.

@roji
Copy link
Member

roji commented Nov 16, 2023

Should this just go into Microsoft.EntityFrameworkCore.Specification.Tests (or its relational counterpart), i.e. do we need a separate new package for design tests?

@ajcvickers
Copy link
Member

ajcvickers commented Nov 17, 2023

Notes from triage:

  • Design tests will go in the functional tests for the given provider
    • This will mean Cosmos tests have reference to Relational package, which isn't ideal, but is probably not too bad.
  • Other "black box" tests that can/should be overridden by providers will also move so that they are shipped on NuGet.

@ajcvickers ajcvickers added this to the MQ milestone Nov 17, 2023
@AndriySvyryd AndriySvyryd changed the title Create and publish Microsoft.EntityFrameworkCore.Design.Specification.Tests Move Design tests to Microsoft.EntityFrameworkCore.Specification.Tests Dec 6, 2023
AndriySvyryd added a commit that referenced this issue Dec 6, 2023
AndriySvyryd added a commit that referenced this issue Dec 6, 2023
AndriySvyryd added a commit that referenced this issue Dec 6, 2023
AndriySvyryd added a commit that referenced this issue Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants