-
Notifications
You must be signed in to change notification settings - Fork 437
RI-8039 [E2E] 7.3 Settings -> Workbench Settings #5593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 1 commit
08bc78f
c0ee55c
31acf48
cec6055
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| 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(); | ||
| }); | ||
|
|
||
| test('should show pipeline commands setting', async ({ settingsPage }) => { | ||
| await expect(settingsPage.pipelineCommandsText).toBeVisible(); | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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)
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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 |
||
| }); | ||
| }); | ||
There was a problem hiding this comment.
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