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

[CT-236] Design for new version of dbt-adapter-tests #4730

Closed
leahwicz opened this issue Feb 15, 2022 · 0 comments · Fixed by #4846
Closed

[CT-236] Design for new version of dbt-adapter-tests #4730

leahwicz opened this issue Feb 15, 2022 · 0 comments · Fixed by #4846
Assignees
Labels
tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality
Milestone

Comments

@leahwicz
Copy link
Contributor

We want to revamp the dbt-adapter-tests framework. This issue is to do the discovery work and come up with a design on how we want to do the following:

  • The new framework should take the place of [pytest-dbt-adapter](https://github.com/dbt-labs/dbt-adapter-tests), which is currently used by a few dozen community- and vendors/partner-maintained adapter plugins
  • “Standard” functionality comes out of the box, so new adapter developers can know whether their adapter works in the standard ways dbt would expect
  • It’s easy to extend / add tests for custom, database-specific functionality (e.g. different incremental strategies, model configs)
@leahwicz leahwicz added the tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality label Feb 15, 2022
@github-actions github-actions bot changed the title Design for new version of dbt-adapter-tests [CT-236] Design for new version of dbt-adapter-tests Feb 15, 2022
@jtcohen6 jtcohen6 added this to the v1.1 milestone Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants