## Description As we are have been seeing contributors are adding new cypress tests we want to execute it using `ci-test-limit`. We need to always make a change to limited-tests file to run new test now we will trigger `ci-test-limit` directly to save efforts. Fyi: we need to revert `limited-tests.txt` after everything looks good on PR. this step to reduce one step effort from our side Fixes #`Issue Number` _or_ Fixes `Issue URL` > [!WARNING] > _If no issue exists, please create an issue first, and check with the maintainers if the issue is valid._ ## Automation /ok-to-test tags="@tag.Sanity" ### 🔍 Cypress test results <!-- This is an auto-generated comment: Cypress test results --> > [!TIP] > 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉 > Workflow run: <https://github.com/appsmithorg/appsmith/actions/runs/9804245011> > Commit: 8384096f415124619b17aac586b4a98ccd3717a5 > <a href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=9804245011&attempt=1" target="_blank">Cypress dashboard</a>. > Tags: `@tag.Sanity` > <hr>Fri, 05 Jul 2024 07:03:52 UTC <!-- end of auto-generated comment: Cypress test results --> ## Communication Should the DevRel and Marketing teams inform users about this change? - [ ] Yes - [ ] No |
||
|---|---|---|
| .. | ||
| assets | ||
| docs | ||
| images | ||
| ServerCodeContributionsGuidelines | ||
| AppsmithWidgetDevelopmentGuide.md | ||
| ClientSetup.md | ||
| CodeContributionsGuidelines.md | ||
| CustomJsLibrary.md | ||
| ServerSetup.md | ||