Update WDIO tests for action menu-based plugin activation

[Copilot]

The frontend now uses an action menu for plugin operations instead of direct toggle buttons. WDIO tests were failing because they attempted to click non-existent toggle elements.

Changes

• Created e2e test file with action menu support for plugin activation testing
• Updated plugin activation test to open action menu before status interaction
• Changed status verification from button property check to mat-icon text content (toggle_off/toggle_on)
• Updated wdio config to reference greate-belt-settings test path

Note: Page Objects (Login, Plugin, MyEforms, Navbar, etc.) are not included in this repository as they exist in the eform-angular-frontend project. The test files are copied to the frontend during the dev/test setup process where these Page Objects are already available.

Implementation

// Before: Direct interaction (no longer works)
const plugin = await pluginPage.getFirstPluginRowObj();
await plugin.enableOrDisablePlugin();

// After: Action menu interaction
const actionMenuBtn = await $('#action-items-0').$('#actionMenu');
await actionMenuBtn.click();
await browser.pause(500);

const statusBtn = await $('#plugin-status-button0');
await statusBtn.click();

Test flow: open menu → interact with status button → close menu with Escape.

Reference: microting/eform-angular-workflow-plugin#1167

<issue_title>Update WDIO tests for action menu-based plugin activation</issue_title>
><issue_description>Use microting/eform-angular-workflow-plugin#1167 as reference as to what needs to be done</issue_description>
>
> ## Comments on the Issue (you are @copilot in this section)
>
>
>
>

• Fixes Update WDIO tests for action menu-based plugin activation #1062

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Update WDIO tests for action menu-based plugin activation</issue_title>
<issue_description>Use microting/eform-angular-workflow-plugin#1167 as reference as to what needs to be done</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Update WDIO tests for action menu-based plugin activation #1062

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[renemadsen]

@copilot don't create Page Objects, since they are coming from frontend project, only do e2e settings file and the wdio-headless-plugin-step2.conf.ts

[Copilot]

@copilot don't create Page Objects, since they are coming from frontend project, only do e2e settings file and the wdio-headless-plugin-step2.conf.ts

Done. Removed all Page Objects and Constants - they now come from the frontend project. Only the test file and wdio config remain. (f1d070a)