Skip to content

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

test(e2e): assert Settings navigation on a section-independent marker

Louis Beaumontf32c48d5c975
diff --git a/apps/screenpipe-app-tauri/e2e/specs/home-window.spec.ts b/apps/screenpipe-app-tauri/e2e/specs/home-window.spec.ts
index dce34ea07..1e6ae6727 100644
--- a/apps/screenpipe-app-tauri/e2e/specs/home-window.spec.ts
+++ b/apps/screenpipe-app-tauri/e2e/specs/home-window.spec.ts
@@ -11,7 +11,11 @@ const SECTIONS = [
{ id: 'pipes', label: 'Scheduled', sectionTestId: 'section-pipes', urlMatch: /section=pipes/ },
{ id: 'timeline', label: 'Timeline', sectionTestId: 'section-timeline', urlMatch: /section=timeline/ },
{ id: 'help', label: 'Help', sectionTestId: 'section-help', urlMatch: /section=help/ },
- { id: 'settings', label: 'Settings', sectionTestId: 'section-settings-general', urlMatch: null },
+ // Settings reopens whichever section was last visited
+ // (openSettings() -> readLastSettingsSection()), so assert on a
+ // section-independent marker. This walkthrough only proves the nav item
+ // lands on Settings, not that any particular panel rendered.
+ { id: 'settings', label: 'Settings', sectionTestId: 'settings-back-to-app', urlMatch: null },
];
describe('Home window', () => {