mirror of
https://github.com/tiddly-gittly/TidGi-Desktop.git
synced 2026-05-30 23:52:01 -07:00
ee5b48c32a
* fix: move useState/useEffect before conditional early return to fix hooks order error in search mode * feat: hide friendLinks section from preferences * feat: add search entry in preferences sidebar that focuses the search input * feat: remove friendLinks section entirely and split Preference.Search i18n key * feat: add search entry in workspace sidebar, fix search section title key * fix: include custom items in search and render info cards in search results * feat: add missing items to sync/externalAPI/aiAgent schemas for search coverage * feat: add EmbeddingSection, wire workspace search section, remove old search result views * fix: apply dark/light palette before serving getIndex to fix startup theme race * feat: add receiveBundleAndFetch for bundle-based mobile push * track latest tiddlywiki5 prerelease * Revert "fix: apply dark/light palette before serving getIndex to fix startup theme race" This reverts commite1c096439d. * Reimplement "fix: apply dark/light palette before serving getIndex to fix startup theme race" This reverts commite1c096439d. * feat: expose runGitCommand, writeTempGitFile, deleteTempGitFile for plugins Allow TiddlyWiki plugins (like tw-mobile-sync) to run arbitrary git commands and manage temp files in the .git directory. This reduces the need to rebuild TidGi Desktop when changing git-related plugin behavior. Methods include path traversal protection for writeTempGitFile/deleteTempGitFile. * refactor: replace receiveBundleAndFetch/mergeAfterPush with generic methods - Removed receiveBundleAndFetch (logic moved to tw-mobile-sync plugin) - Removed mergeAfterPush (logic moved to tw-mobile-sync plugin) - Added readWorkspaceFile and writeWorkspaceFile for plugin file I/O - runGitCommand, writeTempGitFile, deleteTempGitFile remain for plugin git operations - All mobile-sync-specific logic now lives in the tw-mobile-sync plugin * test(e2e): deduplicate browser-view palette steps and merge palette scenarios * test(e2e): isolate palette outline examples by name * test(e2e): decouple smoke logging assertion from worker lifecycle * fix: persist workspace immediately on create to survive fast app close Workspace.create() now calls set() with immediate=true so the new workspace record is flushed to settings.json synchronously, before any before-quit handler runs. Previously, if the app was closed while git init was still running (but after workspace.create had returned), the workspace record would only be in memory and would be lost on the next launch, causing Find 0 existing wiki workspaces and a duplicate default-wiki creation attempt. Also move applyInitialPaletteBeforeIndexRender from startNodeJSWiki to IpcServerRoutes.getIndex so the palette is applied on every index render instead of only at server startup, and thread shouldUseDarkColors through ipcServerRoutes.setConfig for the same reason. Rename args param to gitArguments in GitServerService.runGitCommand to avoid shadowing the outer variable and fix the ESLint no-shadow warning. * test(e2e): fix browser-view step and wiki-worker restart timing browserView.ts: replace fixed 10-attempt backoff with a polling loop that fills the full 25 s Cucumber step budget (210 fast polls), because WebContentsView creation is async and each failed poll returns in < 1 ms (no webContents yet), making the old 10-attempt window too narrow. wiki.ts: replace WIKI_WORKER_STARTED wait before restart with VIEW_LOADED wait. WIKI_WORKER_STARTED is only written on the direct startWiki() path; when the app starts via restartWorkspaceViewService the marker is never emitted. VIEW_LOADED fires after did-stop-loading and is a reliable proxy that the wiki worker is running and the view is ready. application.ts: add launchEnvOverrides map to ApplicationWorld and thread it into the Electron launch env so scenarios can inject test-only env vars (e.g. TIDGI_E2E_MOCK_SYSTEM_PALETTE) without modifying the shared process environment. * test(e2e): fix @wiki scenario timing and assertions defaultWiki.feature: - Explicitly click workspace button before asserting browser-view in Background; without a click the WebContentsView is never activated. - Remove the VIEW_LOADED wait after workspace creation (redundant now that browser-view step polls for the full step budget). - Replace the fragile 'Test content for lazy-all' text assertion with a structural check (open tiddler + confirm element exists); in lazy-all mode TiddlyWiki renders tiddlers lazily so the body text is often the sidebar/chrome rather than the tiddler body at assertion time. - Remove the 'move back to wiki-test' tail of the move-workspace scenario; test-artifacts are wiped before every run so there is no need to restore the original location. simplifiedWiki.feature: - Wait for WORKSPACE_CREATED log marker before closing the app on first launch; git-init inside initWikiGitTransaction can take several seconds, and closing too early meant workspace.create() never ran, leaving settings.json with no wiki workspace on the second launch. windowRestore.feature: - Replace the unreliable WIKI_WORKER_STARTED + VIEW_LOADED wait in Background with WORKSPACE_CREATED + 'browser view should be loaded and visible'; the former marker is not emitted on the restartWorkspaceViewService path used at app startup. * chore: update pnpm-lock and template/wiki submodule * Update pnpm-lock.yaml * test(e2e): remove unused browser view retry constants * test(e2e): stabilize subwiki update and worker readiness wait * fix: enforce LF line endings in .gitattributes to match .editorconfig * feat(e2e): implement CPU-based dynamic timeout scaling Add cpuBenchmark.ts to measure CPU performance at suite startup and derive a performance multiplier (≥1.0) that scales all E2E timeouts. Fast machines get tight timeouts for quick bug detection; slow machines get the room they need without false timeout failures. - cpuBenchmark.ts: Run ~200ms pure CPU workload, compare to reference (120ms) - Local dev: enforce ≥1.8× floor (git I/O overhead not reflected in CPU score) - CI: keep 1.0× (dedicated runners with known performance) - timeouts.ts: Apply multiplier to CUCUMBER_GLOBAL_TIMEOUT and derived values - Print diagnostic: [Timeout Config] multiplier=1.80× step budget=45000 ms * fix(e2e): fix WorkerServicesReady marker search pattern The log marker is written as 'test-id-WorkerServicesReady' (without brackets) but tests were searching for '[test-id-WorkerServicesReady]' (with brackets). ANSI color codes in logs further broke the pattern match. Also implement proper marker clearing: wait for initial readiness, restart, clear stale markers, then wait for fresh markers after restart. Fixes 3 failing scenarios: - AI button in Git Log window uses AI-generated commit message - Plain backup button in Git Log window uses default message - Move workspace to a new location * fix(e2e): simplify isWikiRunning check to avoid TypeScript assertion in executeJavaScript Remove TypeScript type assertion from executeJavaScript string code, use runtime property checks instead to avoid script execution failure. * Revert "fix(e2e): fix WorkerServicesReady marker search pattern" This reverts commit 39f91256092d4ce402eb87b9b70d08c40a6d13fb. * feat(e2e): increase MIN_MULTIPLIER to 2.0× for local dev Increase from 1.8× to 2.0× to provide 100% timing cushion for slow machines. This gives 50s timeout budget (25s base × 2.0) which should be sufficient for browser view loading and wiki worker operations. * fix: restore lazy AI deleted test. don't delete test, otherwise I will add it back * feat(e2e): auto-calibrate timeout using @smoke scenario Remove MIN_MULTIPLIER hack and synthetic CPU benchmark. Instead: - @smoke scenario automatically measures real E2E performance - Hooks record duration and calculate multiplier vs CI baseline - Pure measurement-based scaling, no hardcoded floors - Fallback to 3.0× only if smoke hasn't run yet This captures the full stack (CPU, I/O, Electron startup, rendering) in one real-world measurement, eliminating guesswork. No separate calibration command needed - just run tests normally. * fix(e2e): exclude test files from cucumber require pattern * fix: should save $:/layout * chore: update 5.4.0 prerelease * Update test.yml * fix: Some repo is clone from github, use https to avoid ssh key issue delete the lock file and pnpm i regenerate fix this * lint * fix(ci): restore search section and precompute E2E timeout calibration Restore the missing search preferences section so schema validation passes in CI. Also move E2E timeout calibration ahead of cucumber startup so timeout values are computed before step modules freeze their constants. Use the smoke scenario as a real-world baseline and derive a heavier timeout family for restart and browser-view operations that are dominated by I/O and Electron lifecycle work on slow machines. * fix(sync): restore mobile merge-after-push hook Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai> * test(e2e): stabilize selector waits and calibration state Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai> * test(e2e): remove invalid pre-restart worker wait Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai> * fix(preferences): remove global embedding section Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai> * test(e2e): move vector search flow to workspace settings Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai> * fix(vector-search): validate sqlite row ids before storing embeddings Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai> * feat(git-log): add multi-select batch actions Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai> * fix(git-log): support multi-commit undo, fix path traversal, fix search l10n, fix sidebar divider * fix(test): use data-testid for undo button selector in E2E test UndoCommit translates to '撤回此提交' in zh-Hans, not '撤销'. Use data-testid='undo-commit-button' for reliable matching. * fix(git-log): batch undo via undoCommits, notify git log on tiddler save - Add undoCommits() to git service: undoes N commits sequentially and fires only ONE gitStateChange notification at the end, avoiding the race where rapid-fire events drop refreshes due to loadGitLogInProgress guard - CommitDetailsPanel.handleUndo now uses undoCommits() instead of looping undoCommit() - FileSystemAdaptor.saveTiddler now calls git.notifyFileChange after every save so the git log window auto-refreshes when tiddlers are created/modified, even when enableFileSystemWatch is false (the default) * fix(test): mock git.notifyFileChange in FileSystemAdaptor unit tests * fix(e2e): use BrowserWindow.id to match tidgiMiniWindow Playwright page The previous code matched the mini window's Playwright page by document.title, checking for '太记小窗', 'TidGi Mini Window', or 'TidGiMiniWindow'. But the mini window loads the same index.html as the main window (title='TidGi'), so the title-based match fails whenever React hasn't yet updated document.title. Fix: after finding the BrowserWindow by title (getTitle() contains 'Mini Window') or by dimensions as a fallback, compare each Playwright Page's underlying BrowserWindow.id to the found window's id. This is reliable regardless of document.title state. * fix(lint): remove unnecessary non-null assertion in application.ts * fix(lint): rename args to searchParams to satisfy unicorn/prevent-abbreviations * fix(lint): rename searchParams to searchParameters * fix(window): wait for isVisible() after showWindow() in test mode In E2E tests, BrowserWindow.show() is asynchronous with respect to isVisible() returning true. The IPC call to toggleTidgiMiniWindow() resolves before the OS has actually marked the window as visible, causing the subsequent 'confirm visible' step to fail. Add a poll-until-visible loop (50ms interval) after showWindow() when isTest is true, so the IPC only resolves once isVisible() is actually true. --------- Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
230 lines
16 KiB
Gherkin
230 lines
16 KiB
Gherkin
Feature: Sub-Wiki Functionality
|
|
As a user
|
|
I want sub-wikis to properly load tiddlers on startup
|
|
And I want to use tag tree filtering to organize tiddlers into sub-wikis
|
|
So that my content is automatically organized
|
|
|
|
|
|
@file-watching @subwiki
|
|
Scenario: Tiddler with tag saves to sub-wiki folder
|
|
# Setup: Create sub-wiki with tag BEFORE launching the app (fast setup)
|
|
Given I cleanup test wiki so it could create a new one on start
|
|
And I setup a sub-wiki "SubWiki" with tag "TestTag" and tiddlers:
|
|
| title | tags | content |
|
|
| TestTag | TestTag | Tag tiddler stub |
|
|
When I launch the TidGi application
|
|
And I wait for the page to load completely
|
|
Then I should see "page body and workspaces" elements with selectors:
|
|
| element description | selector |
|
|
| wiki workspace | div[data-testid^='workspace-']:has-text('wiki') |
|
|
| SubWiki workspace | div[data-testid^='workspace-']:has-text('SubWiki') |
|
|
# Enable file system watch for testing (default is false in production)
|
|
When I update workspace "wiki" settings:
|
|
| property | value |
|
|
| enableFileSystemWatch | true |
|
|
When I click on a "default wiki workspace button" element with selector "div[data-testid^='workspace-']:has-text('wiki')"
|
|
Then the browser view should be loaded and visible
|
|
And I wait for SSE and watch-fs to be ready
|
|
# Create tiddler with tag to test routing to sub-wiki folder
|
|
When I create a tiddler "TestTiddlerTitle" with tag "TestTag" in browser view
|
|
# File check will automatically wait for the file to exist
|
|
Then file "TestTiddlerTitle.tid" should exist in "{tmpDir}/SubWiki"
|
|
# Verify tiddler is NOT in main wiki tiddlers folder
|
|
Then file "TestTiddlerTitle.tid" should not exist in "{tmpDir}/wiki/tiddlers"
|
|
# Test SSE is still working - modify a main wiki tiddler
|
|
When I modify file "{tmpDir}/wiki/tiddlers/Index.tid" to contain "Main wiki content modified after SubWiki creation"
|
|
Then I wait for tiddler "Index" to be updated by watch-fs
|
|
When I open tiddler "Index" in browser view
|
|
Then I should see a "Index tiddler" element in browser view with selector "div[data-tiddler-title='Index']"
|
|
Then I should see "Main wiki content modified after SubWiki creation" in the browser view content
|
|
# Test modification in sub-wiki folder
|
|
When I modify file "{tmpDir}/SubWiki/TestTiddlerTitle.tid" to contain "Content modified in SubWiki folder"
|
|
Then I wait for tiddler "TestTiddlerTitle" to be updated by watch-fs
|
|
When I open tiddler "TestTiddlerTitle" in browser view
|
|
# Content check will automatically wait for the content to appear
|
|
Then I should see "Content modified in SubWiki folder" in the browser view content
|
|
# Also verify routing to main workspace path when main workspace has routing tag config
|
|
When I update workspace "wiki" settings:
|
|
| property | value |
|
|
| tagNames | ["MainTag"] |
|
|
And I restart workspace "wiki"
|
|
And I click on a "default wiki workspace button" element with selector "div[data-testid^='workspace-']:has-text('wiki')"
|
|
Then the browser view should be loaded and visible
|
|
And I wait for SSE and watch-fs to be ready
|
|
When I create a tiddler "MainTaggedTiddler" with tag "MainTag" in browser view
|
|
Then file "MainTaggedTiddler.tid" should exist in "{tmpDir}/wiki/tiddlers"
|
|
Then file "MainTaggedTiddler.tid" should not exist in "{tmpDir}/SubWiki"
|
|
|
|
@subwiki @subwiki-load
|
|
Scenario: Sub-wiki tiddlers are loaded on initial wiki startup
|
|
# Setup: Create sub-wiki folder and settings BEFORE launching the app
|
|
Given I cleanup test wiki so it could create a new one on start
|
|
And I setup a sub-wiki "SubWikiPreload" with tag "PreloadTag" and tiddlers:
|
|
| title | tags | content |
|
|
| PreExistingTiddler | PreloadTag | Content from pre-existing sub-wiki tiddler |
|
|
# Now launch the app - it should load both main wiki and sub-wiki tiddlers
|
|
When I launch the TidGi application
|
|
And I wait for the page to load completely
|
|
Then I should see "page body and workspaces" elements with selectors:
|
|
| element description | selector |
|
|
| wiki workspace | div[data-testid^='workspace-']:has-text('wiki') |
|
|
| SubWikiPreload workspace | div[data-testid^='workspace-']:has-text('SubWikiPreload') |
|
|
# Enable file system watch for testing (default is false in production)
|
|
When I update workspace "wiki" settings:
|
|
| property | value |
|
|
| enableFileSystemWatch | true |
|
|
When I click on a "default wiki workspace button" element with selector "div[data-testid^='workspace-']:has-text('wiki')"
|
|
Then the browser view should be loaded and visible
|
|
And I wait for SSE and watch-fs to be ready
|
|
# Open the tiddler directly using TiddlyWiki API
|
|
When I open tiddler "PreExistingTiddler" in browser view
|
|
# Content check will automatically wait for the content to appear
|
|
Then I should see "Content from pre-existing sub-wiki tiddler" in the browser view content
|
|
# Verify the tiddler has the correct tag
|
|
Then I should see a "PreloadTag tag" element in browser view with selector "[data-tiddler-title='PreExistingTiddler'] [data-tag-title='PreloadTag']"
|
|
|
|
@subwiki @subwiki-tagtree
|
|
Scenario: Tiddlers matching tag tree are routed to sub-wiki with includeTagTree enabled
|
|
# Setup: Create sub-wiki with includeTagTree enabled, and pre-existing tag hierarchy A->B
|
|
# TagTreeRoot is the sub-wiki's tagName
|
|
# TiddlerA has tag "TagTreeRoot" (direct child)
|
|
# TiddlerB has tag "TiddlerA" (grandchild via tag tree)
|
|
Given I cleanup test wiki so it could create a new one on start
|
|
And I setup a sub-wiki "SubWikiTagTree" with tag "TagTreeRoot" and includeTagTree enabled and tiddlers:
|
|
| title | tags | content |
|
|
| TiddlerA | TagTreeRoot | TiddlerA with TagTreeRoot tag |
|
|
| TiddlerB | TiddlerA | TiddlerB with TiddlerA tag |
|
|
# Now launch the app
|
|
When I launch the TidGi application
|
|
And I wait for the page to load completely
|
|
Then I should see "page body and workspaces" elements with selectors:
|
|
| element description | selector |
|
|
| wiki workspace | div[data-testid^='workspace-']:has-text('wiki') |
|
|
| SubWikiTagTree workspace | div[data-testid^='workspace-']:has-text('SubWikiTagTree') |
|
|
# Enable file system watch for testing (default is false in production)
|
|
When I update workspace "wiki" settings:
|
|
| property | value |
|
|
| enableFileSystemWatch | true |
|
|
When I click on a "default wiki workspace button" element with selector "div[data-testid^='workspace-']:has-text('wiki')"
|
|
Then the browser view should be loaded and visible
|
|
And I wait for SSE and watch-fs to be ready
|
|
# Verify TiddlerA and TiddlerB were loaded from sub-wiki by opening them
|
|
When I open tiddler "TiddlerA" in browser view
|
|
Then I should see "TiddlerA with TagTreeRoot tag" in the browser view content
|
|
When I open tiddler "TiddlerB" in browser view
|
|
Then I should see "TiddlerB with TiddlerA tag" in the browser view content
|
|
# Create TiddlerC with tag TiddlerB (testing tag tree routing: TiddlerC -> TiddlerB -> TiddlerA -> TagTreeRoot)
|
|
When I create a tiddler "TiddlerC" with tag "TiddlerB" in browser view
|
|
# File check will automatically wait for the file to exist
|
|
Then file "TiddlerC.tid" should exist in "{tmpDir}/SubWikiTagTree"
|
|
Then file "TiddlerC.tid" should not exist in "{tmpDir}/wiki/tiddlers"
|
|
|
|
@subwiki @subwiki-filter
|
|
Scenario: Tiddlers matching custom filter are routed to sub-wiki
|
|
# Setup: Create sub-wiki with custom filter that matches tiddlers with "filtertest" field
|
|
Given I cleanup test wiki so it could create a new one on start
|
|
And I setup a sub-wiki "SubWikiFilter" with tag "FilterTag" and filter "[has[filtertest]]" and tiddlers:
|
|
| title | tags | content |
|
|
| FilterTiddlerA | FilterTag | TiddlerA matched by filter |
|
|
When I launch the TidGi application
|
|
And I wait for the page to load completely
|
|
Then I should see "page body and workspaces" elements with selectors:
|
|
| element description | selector |
|
|
| wiki workspace | div[data-testid^='workspace-']:has-text('wiki') |
|
|
| SubWikiFilter workspace | div[data-testid^='workspace-']:has-text('SubWikiFilter') |
|
|
# Enable file system watch for testing (default is false in production)
|
|
When I update workspace "wiki" settings:
|
|
| property | value |
|
|
| enableFileSystemWatch | true |
|
|
When I click on a "default wiki workspace button" element with selector "div[data-testid^='workspace-']:has-text('wiki')"
|
|
Then the browser view should be loaded and visible
|
|
And I wait for SSE and watch-fs to be ready
|
|
# Create a tiddler with the "filtertest" field to test filter routing
|
|
When I create a tiddler "FilterMatchTiddler" with field "filtertest" set to "yes" in browser view
|
|
# File check will automatically wait for the file to exist
|
|
Then file "FilterMatchTiddler.tid" should exist in "{tmpDir}/SubWikiFilter"
|
|
Then file "FilterMatchTiddler.tid" should not exist in "{tmpDir}/wiki/tiddlers"
|
|
|
|
@subwiki @subwiki-settings-ui
|
|
Scenario: Sub-wiki settings UI can enable includeTagTree option
|
|
# This tests the EditWorkspace UI for setting includeTagTree via the new switch
|
|
Given I cleanup test wiki so it could create a new one on start
|
|
And I setup a sub-wiki "SubWikiSettings" with tag "SettingsTag" and tiddlers:
|
|
| title | tags | content |
|
|
| SettingsTiddler | SettingsTag | Settings test tiddler |
|
|
When I launch the TidGi application
|
|
And I wait for the page to load completely
|
|
Then I should see "page body and workspaces" elements with selectors:
|
|
| element description | selector |
|
|
| wiki workspace | div[data-testid^='workspace-']:has-text('wiki') |
|
|
| SubWikiSettings workspace | div[data-testid^='workspace-']:has-text('SubWikiSettings') |
|
|
# Main workspace should list its bound sub-workspaces and provide direct edit entry
|
|
When I open edit workspace window for workspace with name "wiki"
|
|
And I switch to "editWorkspace" window
|
|
And I wait for the page to load completely
|
|
Then I should see "main workspace sub-workspace bindings" elements with selectors:
|
|
| element description | selector |
|
|
| sub-workspace options accordion | [data-testid='preference-section-subWiki'] |
|
|
| bound sub-workspace row | [data-testid='bound-sub-workspace-row']:has-text('SubWikiSettings'):has-text('SettingsTag') |
|
|
| open sub-workspace settings button| [data-testid='open-sub-workspace-settings-button'] |
|
|
When I open edit workspace window for workspace with name "SubWikiSettings"
|
|
And I switch to "editWorkspace" window
|
|
And I wait for the page to load completely
|
|
Then I should see "sub-workspace options accordion and bindings" elements with selectors:
|
|
| element description | selector |
|
|
| sub-workspace options accordion | [data-testid='preference-section-subWiki'] |
|
|
| main workspace select | [data-testid='main-wiki-select'] |
|
|
| includeTagTree switch | [data-testid='include-tag-tree-switch'] |
|
|
# Enable includeTagTree option and save
|
|
When I click on "includeTagTree switch and save button" elements with selectors:
|
|
| element description | selector |
|
|
| includeTagTree switch | [data-testid='include-tag-tree-switch'] |
|
|
| save button | [data-testid='edit-workspace-save-button'] |
|
|
Then I should not see a "save button" element with selector "[data-testid='edit-workspace-save-button']"
|
|
# Verify the setting was saved to settings.json
|
|
Then settings.json should have workspace "SubWikiSettings" with "includeTagTree" set to "true"
|
|
|
|
@subwiki @subwiki-create-ui
|
|
Scenario: Create sub-wiki workspace via UI
|
|
# This tests creating a sub-wiki through the Add Workspace UI
|
|
Given I cleanup test wiki so it could create a new one on start
|
|
And I launch the TidGi application
|
|
And I wait for the page to load completely
|
|
Then I should see a "default wiki workspace" element with selector "div[data-testid^='workspace-']:has-text('wiki')"
|
|
# Enable file system watch for testing (default is false in production)
|
|
When I update workspace "wiki" settings:
|
|
| property | value |
|
|
| enableFileSystemWatch | true |
|
|
When I click on a "default wiki workspace button" element with selector "div[data-testid^='workspace-']:has-text('wiki')"
|
|
Then the browser view should be loaded and visible
|
|
And I wait for SSE and watch-fs to be ready
|
|
# Create sub-workspace via UI
|
|
When I click on an "add workspace button" element with selector "#add-workspace-button"
|
|
And I switch to "addWorkspace" window
|
|
# Toggle to sub-workspace mode
|
|
When I click on a "main/sub workspace switch" element with selector "[data-testid='main-sub-workspace-switch']"
|
|
# Select the first (default) wiki workspace from dropdown
|
|
And I select "wiki" from MUI Select with test id "main-wiki-select"
|
|
# Type folder name
|
|
And I type "SubWikiUI" in "sub wiki folder name input" element with selector "input[aria-describedby*='-helper-text'][value='wiki']"
|
|
# Add tag using Autocomplete - type and press Enter to add the tag
|
|
And I type "UITestTag" in "tag name input" element with selector "[data-testid='tagname-autocomplete-input']"
|
|
And I press "Enter" key
|
|
And I click on a "create sub workspace button" element with selector "button.MuiButton-colorSecondary"
|
|
And I switch to "main" window
|
|
Then I should see a "SubWikiUI workspace" element with selector "div[data-testid^='workspace-']:has-text('SubWikiUI')"
|
|
# Wait for main wiki to restart after sub-wiki creation
|
|
Then I wait for log markers:
|
|
| description | marker |
|
|
| main wiki restarted after sub-wiki creation| [test-id-MAIN_WIKI_RESTARTED_AFTER_SUBWIKI] |
|
|
| watch-fs stabilized after restart | [test-id-WATCH_FS_STABILIZED] |
|
|
| SSE ready after restart | [test-id-SSE_READY] |
|
|
| view loaded | [test-id-VIEW_LOADED] |
|
|
# Wait for TiddlyWiki to fully render the page (site title appears)
|
|
Then I wait for "site title" element in browser view with selector "h1.tc-site-title"
|
|
# Click SubWikiUI workspace to see the missing tag tiddler message
|
|
When I click on a "SubWikiUI workspace button" element with selector "div[data-testid^='workspace-']:has-text('SubWikiUI')"
|
|
# Verify UITestTag text is visible (missing tiddler message shows the title)
|
|
Then I should see "UITestTag" in the browser view content
|
|
# Verify the sub-wiki was created in settings.json
|
|
Then settings.json should have workspace "SubWikiUI" with "tagNames" containing "UITestTag"
|