SQS-393 | E2E Tests: Compute liquidity with CoinGecko

[deividaspetraitis]

This PR adds COINGECKO_API_KEY env variable to enable computing liquidity with CoinGecko instead of Numia

Summary by CodeRabbit

• New Features

  • Integration tests now include access to the CoinGecko API, enhancing their ability to validate cryptocurrency data.

• Bug Fixes

  • Improved reliability of integration tests by utilizing an external API for validation.

[coderabbitai]

Walkthrough

The changes involve the addition of a new environment variable, COINGECKO_API_KEY, to the .github/workflows/integration-test.yml file. This variable is now included in two job definitions for integration tests, indicating that the tests will interact with the CoinGecko API. This modification allows the integration tests to access external cryptocurrency data, which is essential for their execution.

Changes

File	Change Summary
.github/workflows/integration-test.yml	Added COINGECKO_API_KEY to environment variables for integration test jobs.

Poem

In the garden where bunnies play,
A new key hops in, brightening the day.
With CoinGecko's data, tests will soar,
Validating crypto, oh, what a score!
So let’s dance and cheer with glee,
For a future of tests, as fine as can be! 🐇✨

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ef402b6 and f8a0ffb.

Files selected for processing (1)

• .github/workflows/integration-test.yml (2 hunks)

Additional comments not posted (2)

.github/workflows/integration-test.yml (2)

46-46: LGTM!

The addition of the COINGECKO_API_KEY environment variable is consistent with the PR objectives and follows secure practices by sourcing the value from the repository's secrets. This change enhances the functionality of the integration tests by allowing them to interact with the CoinGecko API.

---

77-77: LGTM!

The addition of the COINGECKO_API_KEY environment variable to the scheduled integration tests is consistent with the PR objectives and follows secure practices by sourcing the value from the repository's secrets. This change enhances the functionality of the scheduled integration tests by allowing them to interact with the CoinGecko API.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai generate interesting stats about this repository and render them as a table.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud