Repository metrics
- Stars
- (17,486 stars)
- PR merge metrics
- (PR metrics pending)
Description
Required prerequisites
- I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
- Consider asking first in a Discussion.
Motivation
discussion raised by @coolbeevip https://github.com/orgs/camel-ai/discussions/1151
Currently, the project's test cases are in the camel/test directory. Some tests need a Google API key or an OpenAI API key to run correctly.
If a contributor hasn't set up these keys in their forked repo, their tests will fail when submitting a PR. But these keys aren’t free.
Could we organize the test cases into two categories: unit_tests and integration_tests? It would look like this:
camel/tests/unit_tests (for essential tests) camel/tests/integration_tests (for tests that connect to external APIs) This would make it easier for contributors to submit PRs during the CI/CD process while still keeping the necessary integration tests functional after merging.
Solution
No response
Alternatives
No response
Additional context
No response