🚀 Feature: Added end-to-end test cases using testRigor through CI/CD

[tangencialmente]

Description

This pull request adds end-to-end test cases using testRigor.

testRigor is an AI-powered end-to-end testing platform that allows you to write tests in plain English. This setup enables automated testing of the Plane application's user interface and functionality from a user's perspective.

- 1 new workflow file that will perform a full run of this test suite when triggered.
- 1 new folders called e2etests that contains all the test cases and reusable rules being added.

Here are the results of the latest test suite run: https://app.testrigor.com/public/RMEFLdnHwGbLu265M

Why testRigor?

Test cases written in plain English: Anyone can contribute automated tests without any language-specific coding skills, broadening the contributor base and allowing a higher test coverage.

Reduced maintenance overhead: Tests are resilient to UI changes, lowering the cost of keeping the suite up to date.

Cross-platform coverage: Support across different environments and setups such as mobile, desktop and web.

How to test the changes in this Pull Request:

There are 2 ways to test these changes, either by triggering the workflow actions or by executing it manually:
Workflow actions:

Do any pull/push request to trigger the workflow file over at .github/workflows/CI-tR.yml
The workflow file will set up the test environment then run the test cases
A new test suite run will be triggered

Manual trigger:
- Set up a plane instance following these steps.
- Set up a free testRigor test suite
- Install the testRigor CLI tool
- Open the CLI then type out the following command testrigor test-suite run <SUITE_ID> --token <CI_TOKEN> --localhost --url --test-cases-path e2e-tests/testcases/**/*.txt

Replace the items between "< >" with the corresponding values:

SUITE_ID: the ID of the test suite itself, it's located in the URL (i.e. for the following test suite: https://app.testrigor.com/test-suites/245eg9BjPdToYXHNf/test-cases , the SUITE_ID is: 245eg9BjPdToYXHNf
CI_TOKEN: To get the CI token follow these steps:
    Open the test suite that has been previously set up.
    Click "CI/CD Integration" located on the sidebar.
    The auth token should be located there (refer to the image posted below).
    Copy the CI token then use it on the CLI command.

A test suite run should trigger after following these steps, executing the test cases located on the folder.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Improvement (change that would cause existing functionality to not work as expected)
• Code refactoring
• Performance improvements
• Documentation update

Test Scenarios:

For the test cases being executed, the test scenario consists in a regular self-hosted plane instance (installed following these rules) that includes 1 admin and 2 normal users.

The 10 test cases being added test, different functionalities these include:

• Validating that the search function filters work items by labels.
• Validate that quicklinks do in fact redirect to the specified website.
• Validating that you can't add an active cycle when another cycle is already active.
• Validating that cycle progress updates accordingly whenever work items are tagged as "done".
• Validating that work items can be dragged on views.
• Validating that pages can be updated be edited by other users and they update in real time.
• Validating that comments on a work ticket trigger notifications for the people being assigned to it.
• Validating that changing the project ID, updates the ID of all work items.
• Validating that it's possible to drag work items on board view and by doing so, their status gets updated.
• Validating that when guest users are added to a project they're able to see its work items.

---

Note

Adds a testRigor-based E2E workflow and tests, replaces the legacy command palette with the new Power K system, standardizes chevron/close icons via propel, and upgrades global search and issue link serialization.

• CI/CD & E2E:
  • Add /.github/workflows/tR-ci.yml to run testRigor suites in CI.
  • Add e2etests/ with README, reusable rules, and test cases.
• Command Palette (Power K):
  • Implement new Power K command system (registry, shortcuts, modal, context-based actions, navigation/preferences menus).
  • Integrate ProjectsAppPowerKProvider into app layouts; remove legacy command-palette code.
• Icons & UI:
  • Add CloseIcon and Chevron*Icon to @plane/propel/icons; refactor app/editor/ui to use them instead of lucide variants.
  • Replace command palette styles with power-k.css.
• API/Search:
  • Global search: safer query handling, entity selection via entities param, added intake results, and consistent -created_at ordering.
• Serialization:
  • IssueLinkCreateSerializer now accepts title.
• Misc:
  • Filter/display utilities tweaks; settings icons export rename; minor dependency/lock updates.

^{Written by Cursor Bugbot for commit edc0749. This will update automatically on new commits. Configure here.}

[coderabbitai]

Important

Review skipped

More than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review.

192 files out of 300 files are above the max files limit of 100. Please upgrade to Pro plan to get higher limits.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[CLAassistant]

All committers have signed the CLA.