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
Reorganize test structure: move integration tests into subdirectory
Consolidates integration tests under tests/integration/ with updated paths
in documentation, CI workflows, and configuration files. Improves project
organization by clearly separating integration test artifacts.
uv run python tests/run_mcp_tests.py "uv run teradata-mcp-server"
36
+
uv run python tests/integration/run_mcp_tests.py "uv run teradata-mcp-server"
37
37
38
38
# Docker
39
39
docker compose up teradata-mcp-server
@@ -104,7 +104,7 @@ For stdio transport, logs go to file only (to avoid polluting MCP stdout). Log l
104
104
105
105
### Testing
106
106
107
-
Tests require a live Teradata database. Test cases are JSON files in `tests/cases/` (e.g., `core_test_cases.json`). The test runner (`tests/run_mcp_tests.py`) dynamically discovers available tools and only runs matching test cases. Results are saved as timestamped JSON in `var/test-reports/`.
107
+
Tests require a live Teradata database. Test cases are JSON files in `tests/integration/cases/` (e.g., `core_test_cases.json`). The test runner (`tests/integration/run_mcp_tests.py`) dynamically discovers available tools and only runs matching test cases. Results are saved as timestamped JSON in `var/test-reports/`.
Copy file name to clipboardExpand all lines: docs/developer_guide/CONTRIBUTING.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,8 @@ Make sure you have setup your environment based on the Developer Guide in this r
7
7
## Development Guidelines
8
8
- Always engage on the discussion board or create an issue before creating a PR.
9
9
- All PRs must have at least one issue associated.
10
-
- Run the full pre-push checklist before opening a PR, and copy/paste the test report output in the PR: lint (`uv run ruff check src/`), type check (`uv run mypy src/`), HTTP smoke test (`uv run python tests/smoke_http.py`), and integration tests over both stdio and HTTP (`uv run python tests/run_mcp_tests.py "uv run teradata-mcp-server"` and `... --transport streamable-http`). See the [Developer Guide](./DEVELOPER_GUIDE.md) for the full ordered checklist.
11
-
- Create a new test case if you add a new tool. For more information see [our testing guide](/tests/README.md)
10
+
- Run the full pre-push checklist before opening a PR, and copy/paste the test report output in the PR: lint (`uv run ruff check src/`), type check (`uv run mypy src/`), HTTP smoke test (`uv run python tests/integration/smoke_http.py`), and integration tests over both stdio and HTTP (`uv run python tests/integration/run_mcp_tests.py "uv run teradata-mcp-server"` and `... --transport streamable-http`). See the [Developer Guide](./DEVELOPER_GUIDE.md) for the full ordered checklist.
11
+
- Create a new test case if you add a new tool. For more information see [our testing guide](/tests/integration/README.md)
12
12
- All code must be reviewed via a pull request. Before anything can be merged, it must be reviewed by at least 2 others. [Contributing to a project step by step instuctions](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project)
13
13
- Squash commits into a single commit for your PR. We want to keep a clean git history.
14
14
- Code should adhere to lint and codestyle tests. While you can commit code that doesn't validate but still works, it is encouraged to validate your code. It saves other's headaches down the road.
uv run python tests/run_mcp_tests.py "uv run teradata-mcp-server" --transport streamable-http
62
+
uv run python tests/integration/run_mcp_tests.py "uv run teradata-mcp-server" --transport streamable-http
63
63
```
64
64
65
65
Steps 1–3 have no database dependency and are quick — run them on every change. Steps 4–5 require VPN and credentials; run them when you have changed tool handlers, middleware, or connection logic.
@@ -650,18 +650,18 @@ Use the provided testing tool to run tests, add tests if you add a new tool.
650
650
651
651
We have a "core" test suite for all the core tools provided with this server, separate ones for the add-ons (eg. Enterprise Feature Store, Enterprise Vector Store) and you can add more for your custom tools.
652
652
653
-
See guidelines and details in [our testing guide](/tests/README.md)
653
+
See guidelines and details in [our testing guide](/tests/integration/README.md)
654
654
655
655
Run testing before PR, and copy/paste the test report status in the PR.
656
656
657
657
**Development testing:**
658
658
```bash
659
-
python tests/run_mcp_tests.py "uv run teradata-mcp-server"
659
+
python tests/integration/run_mcp_tests.py "uv run teradata-mcp-server"
0 commit comments