Skip to content

Add E2E tests for LLM provider and proxy lifecycle, project CRUD, and… - #3035

Open
Thushani-Jayasekera wants to merge 2 commits into
wso2:mainfrom
Thushani-Jayasekera:e2e-test
Open

Add E2E tests for LLM provider and proxy lifecycle, project CRUD, and…#3035
Thushani-Jayasekera wants to merge 2 commits into
wso2:mainfrom
Thushani-Jayasekera:e2e-test

Conversation

@Thushani-Jayasekera

Copy link
Copy Markdown
Contributor

… deployment scenarios

  • Introduced Cypress tests for LLM provider lifecycle, including creation, update, and deletion with API key handling.
  • Added tests for App LLM proxy lifecycle, covering creation, update, and security settings.
  • Implemented tests for MCP proxy view and update functionalities.
  • Created project CRUD tests to validate project creation, listing, updating, and deletion processes.
  • Added deployment tests for LLM providers, ensuring proper deployment and redeployment functionality with a connected gateway.
  • Updated Cypress configuration to include a new E2E gateway name for testing purposes.
  • Introduced a new Docker Compose file for the AI gateway to facilitate E2E testing.

Purpose

Explain why this feature or fix is required. Describe the underlying problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Goals

Describe what solutions this feature or fix introduces to address the problems outlined above.

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI. Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Automation tests

  • Unit tests

    Code coverage information

  • Integration tests

    Details about the test cases and coverage

Security checks

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

… deployment scenarios

- Introduced Cypress tests for LLM provider lifecycle, including creation, update, and deletion with API key handling.
- Added tests for App LLM proxy lifecycle, covering creation, update, and security settings.
- Implemented tests for MCP proxy view and update functionalities.
- Created project CRUD tests to validate project creation, listing, updating, and deletion processes.
- Added deployment tests for LLM providers, ensuring proper deployment and redeployment functionality with a connected gateway.
- Updated Cypress configuration to include a new E2E gateway name for testing purposes.
- Introduced a new Docker Compose file for the AI gateway to facilitate E2E testing.
@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@Thushani-Jayasekera, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 53 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 6493b81f-5805-459b-9bbe-a5d534329d9e

📥 Commits

Reviewing files that changed from the base of the PR and between 080fcbe and 647393f.

📒 Files selected for processing (9)
  • portals/ai-workspace/cypress.config.js
  • portals/ai-workspace/cypress/e2e/001-providers/004-provider-lifecycle-and-config.cy.js
  • portals/ai-workspace/cypress/e2e/001-providers/005-llm-proxy-lifecycle-and-config.cy.js
  • portals/ai-workspace/cypress/e2e/002-mcp-proxies/006-mcp-proxy-view-and-update.cy.js
  • portals/ai-workspace/cypress/e2e/006-projects/001-project-crud.cy.js
  • portals/ai-workspace/cypress/e2e/007-deployments/001-provider-deployment.cy.js
  • portals/ai-workspace/cypress/support/commands.js
  • portals/ai-workspace/docker-compose.gateway.yaml
  • portals/ai-workspace/scripts/start-e2e-gateway.sh

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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