You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
This PR fixes the integration tests so they all pass. Previously,
integration testing was an optional manual process. These tests would
not always be in a working state and weren't always updated with
associated source code changes.
As the project matures, we need to rely on these tests and invest more
in them. As a follow-up to this PR, I plan to run these tests as part of
our PR pipeline to ensure they pass for all changes. This may make it
more difficult for non-dbt Labs employees to contribute, but this is
important to ensure the dbt MCP is stable and reliable.
## Checklist
- [x] I have performed a self-review of my code
- [x] I have made corresponding changes to the documentation (in
https://github.com/dbt-labs/docs.getdbt.com) if required -- Mention it
here
- [x] I have added tests that prove my fix is effective or that my
feature works
- [x] New and existing unit tests pass locally with my changes
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,19 @@ Refer to `./cursor/rules` for standards and stylistic guidelines.
30
30
31
31
## Testing
32
32
33
-
This repo has automated tests which can be run with `task test:unit`. Additionally, there is a simple CLI tool which can be used to test by running `task client`. If you would like to testin a client like Cursor or Claude, use a configuration file like this:
33
+
### Unit Testing
34
+
35
+
This repo has automated tests which can be run with `task test:unit`.
36
+
37
+
### Integration Testing
38
+
39
+
The integration tests exercise system interactions greater than just the unit tests. They require a dbt Platform environment that is setup with semantic layer, developer license, and PAT. These tests can be run with `task test:integration`.
40
+
41
+
For dbt Labs employees, a staging environment has been set up. Credentials forthis environment can be found by searching for `dbt MCP Integration Test Credentials`in 1Password.
42
+
43
+
### Manual Testing
44
+
45
+
To testin a client like Cursor or Claude, use a configuration file like this:
0 commit comments