test: Add firecrawl test

[vblagoje]

Why:

The changes focus on refining and enhancing the testing suite associated with an API client library. By utilizing more specific providers and handling error scenarios in tests, the updates aim to increase the robustness of client interactions and reliability of integrations, particularly under scenarios where API usage limitations might generate errors. The changes are necessary to ensure accurate testing and validation of different API endpoints and error conditions across services.

What:

• Updated Provider Usage: Replaced the generic LLMProvider.COHERE with a more specific CohereProvider() class in test cases.
• Enhanced Error Handling: Improved test logic for Firecrawl's integration. Tests now account for HTTP errors, specifically handling 402 Payment Required errors as valid test outcomes.
• Test Descriptions and Logic: Refined test descriptions and added clearer logic for handling integration tests that require specific environment variables.

How can it be used:

• Provider Selection: Utilize specific provider classes (like CohereProvider) to tie directly into the corresponding API, enabling the use of updated or new functionalities from such providers.

• Error Handling in Tests: Implement error handling logic that acknowledges and validates expected HTTP error responses, contributing to more resilient test cases. Example usage:

  try:
      ...
  except HttpClientError as e:
      assert "402" in str(e) or "Payment Required" in str(e),

How did you test it:

• Unit and Integration Tests: Changes were validated through a series of modified and new test cases, ensuring that each API call and response handling reflects accurate and meaningful results.
• Error Scenario Validations: Tests included simulations for typical HTTP error responses, confirming that such scenarios are captured and processed as intended, thereby maintaining test robustness across varying conditions.

Notes for the reviewer:

• Pay attention to the updated usage of provider classes, ensuring that this specificity aligns with the intended test goals and API interactions.
• Verify the logic handling and implications of HTTP error responses, particularly the acceptance of 402 errors, as it affects how the test suite interprets API call results.
• Confirm that any environment-specific settings, such as API keys, are appropriately set for tests that require them.

[coveralls]

Pull Request Test Coverage Report for Build 12337837098

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 81.293%

---

Totals
Change from base Build 12337815901:	0.0%
Covered Lines:	352
Relevant Lines:	433

---

💛 - Coveralls