test: tag two chat-toggle pad_settings specs with @feature:chat (#7655)

Surfaced by ep_disable_chat#75 — the disables-aware test runner ran
pass 1 (regression) and these two tests failed because they click
label[for="options-disablechat"], which ep_disable_chat hides as
intended. Tagging them brings them into pass 2 (honesty) where
they're expected to fail under the plugin, instead of pass 1 where
they shouldn't run.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
John McLear 2026-05-02 19:45:14 +08:00 committed by GitHub
parent ea3032c079
commit 983aec5b2f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -143,7 +143,9 @@ test.describe('creator-owned pad settings', () => {
await expect(page.locator('#options-colorscheck')).not.toBeChecked();
});
test('disabling chat suppresses chat gritter notifications', async ({page, browser}) => {
test('disabling chat suppresses chat gritter notifications', {
tag: '@feature:chat',
}, async ({page, browser}) => {
const padId = await goToNewPad(page);
const context2 = await browser.newContext();
const page2 = await context2.newPage();
@ -164,7 +166,9 @@ test.describe('creator-owned pad settings', () => {
// #7592: ticking "Disable chat" must visibly disable the dependent
// "Chat always on screen" / "Show Chat and Users" toggles, not just
// make the underlying inputs non-interactive.
test('disabling chat disables and visually greys the dependent chat toggles', async ({page}) => {
test('disabling chat disables and visually greys the dependent chat toggles', {
tag: '@feature:chat',
}, async ({page}) => {
await goToNewPad(page);
await showSettings(page);