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
{{ message }}
This repository was archived by the owner on Jun 5, 2025. It is now read-only.
Remove redundancy and differences between README and Development Guide
- Removed information from README that repeated or conflicted with the Development Guide (docs/development.md).
- Moved development guidance that was only in the README into the Development Guide
- Added a note to clarify context needed for running integration tests.
source venv/bin/activate # On Windows: venv\Scripts\activate
46
+
```
47
+
48
+
4. Install project dependencies:
42
49
43
50
```bash
44
51
poetry install --with dev
@@ -147,7 +154,8 @@ The project uses several tools to maintain code quality:
147
154
148
155
### 3. Testing
149
156
150
-
Run the test suite with coverage:
157
+
#### Unit Tests
158
+
To run the unit test suite with coverage:
151
159
152
160
```bash
153
161
poetry run pytest
@@ -156,6 +164,25 @@ poetry run pytest
156
164
Tests are located in the `tests/` directory and follow the same structure as the
157
165
source code.
158
166
167
+
#### Integration Tests
168
+
To run the integration tests, create a `.env` file in the repo root directory and add the
169
+
following properties to it:
170
+
```
171
+
ENV_OPENAI_KEY=<YOUR_KEY>
172
+
ENV_VLLM_KEY=<YOUR_KEY>
173
+
ENV_ANTHROPIC_KEY=<YOUR_KEY>
174
+
```
175
+
176
+
Then the integration tests can be executed by running:
177
+
```bash
178
+
python tests/integration/integration_tests.py
179
+
```
180
+
181
+
You can include additional properties to specify test scope and other information. For instance, to execute the tests for Copilot providers, for instance, run:
0 commit comments