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

Run tests in vendor-specific environments #206

Draft
wants to merge 17 commits into
base: main
Choose a base branch
from

Conversation

stellasia
Copy link
Contributor

@stellasia stellasia commented Oct 25, 2024

Description

Try to run tests in environements which are closer to the user env, ie where only the minimal set of extra dependencies are installed.

Type of Change

  • New feature
  • Bug fix
  • Breaking change
  • Documentation update
  • Project configuration change

Complexity

Note

Please provide an estimated complexity of this PR of either Low, Medium or High

Complexity:

How Has This Been Tested?

  • Unit tests
  • E2E tests
  • Manual tests

Checklist

The following requirements should have been met (depending on the changes in the branch):

  • Documentation has been updated
  • Unit tests have been updated
  • E2E tests have been updated
  • Examples have been updated
  • New files have copyright header
  • CLA (https://neo4j.com/developer/cla/) has been signed
  • CHANGELOG.md updated if appropriate

@stellasia stellasia changed the title Test/contextual Run tests in vendor-specific environments Oct 25, 2024
@@ -43,3 +43,29 @@ jobs:
run: |
poetry run coverage run -m pytest tests/unit
poetry run coverage report --fail-under=90
test_contextual:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Glad to update the name if you find a better one.

strategy:
matrix:
python-version: [ '3.9', '3.12' ]
vendor: ["anthropic", "cohere", "mistralai", "openai", "sentence_transformers", "vertexai"]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here, better naming proposal welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant