Skip to content
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions tests/e2e-playwright/TEST_PLAN.md
Original file line number Diff line number Diff line change
Expand Up @@ -673,8 +673,8 @@ The test plan is organized by feature area. Tests are grouped for parallel execu
### 7.3 Workbench Settings
| Status | Group | Test Case |
|--------|-------|-----------|
| 🔲 | main | Show editor cleanup switch |
| 🔲 | main | Show pipeline commands setting |
| | main | Show editor cleanup switch |
| | main | Show pipeline commands setting |
| 🔲 | main | Configure command timeout (N/A - per-database setting, not in settings page) |

### 7.4 Redis Cloud Settings
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
import { test, expect } from '../../../../fixtures/base';

/**
* Workbench Settings tests (TEST_PLAN.md: 7.3 Workbench Settings)
*
* Tests for the Workbench section on the Settings page.
* Verifies editor cleanup switch and pipeline commands setting are displayed.
*
* Note: "Configure command timeout" is N/A -- it's a per-database setting, not on the Settings page.
*/
test.describe('Workbench Settings', () => {
test.beforeEach(async ({ settingsPage }) => {
await settingsPage.goto();
await settingsPage.expandWorkbench();
});

test('should show editor cleanup switch', async ({ settingsPage }) => {
await expect(settingsPage.editorCleanupSwitch).toBeVisible();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

haven't tested it, but if it's easy, it makes sense to add a test that executes something in the workbench so we can validate the switch logic

});

test('should show pipeline commands setting', async ({ settingsPage }) => {
await expect(settingsPage.pipelineCommandsText).toBeVisible();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and for that one too (I imagine we can set it to 2, and validate just a single command is visible)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think these should be tested here. The test must verify that you can change and save settings. How they affect the related feature, that should be tested as part of that feautre's tests

});
});
Loading