2026-07-29 18:59:46 +08:00
|
|
|
// @vitest-environment jsdom
|
2026-08-06 13:00:14 +08:00
|
|
|
// The built-bundle boot smoke: the assembled-jsdom test that owns the boot
|
|
|
|
|
// graph itself. Other files share the same scaffolding (assembled-boot.ts) to
|
|
|
|
|
// reach a surface only the built bundles expose; this one asserts that the
|
|
|
|
|
// graph assembles at all — staged activation across the immediately tier and
|
|
|
|
|
// the inject layers, per-plugin CSS injection, and a rendered journey reaching
|
|
|
|
|
// chat content from the keyless FixtureApiClient transport.
|
test(web): shrink the assembled jsdom lane to one built-bundle boot smoke
The seven behavior-pinning snapshots (workspace-flow, slash-flow,
todo-display, session-title, session-actions, terminal-card,
code-mode-fixture) asserted per-package behavior through the whole
built app: every assertion now lives in the owning package's suite at
equal strength (SlotTestRuntime benches assemble the same plugin apply
over the production slot machinery), while the assembled layer kept
re-failing on unrelated churn at 10s-timeout debugging cost.
What only this lane can prove is the artifact plane: lib/client.js
bundles loading through the ModuleLoader path, staged boot activation
across the inject layers, per-plugin CSS injection, and a journey
reaching chat content over the fixture transport. built-boot.snapshot.ts
pins exactly that, and nothing else — behavior assertions belong to the
package suites.
2026-07-29 23:45:39 +08:00
|
|
|
//
|
2026-07-30 02:40:31 -07:00
|
|
|
// Component behavior remains owned by per-package suites (SlotTestRuntime
|
2026-08-04 17:14:58 +08:00
|
|
|
// benches over src). This smoke additionally pins the resident interaction
|
2026-08-22 21:19:39 +08:00
|
|
|
// fixture's cross-plugin projection because only the built connection,
|
|
|
|
|
// Controller, UI adapter, and Workspace graph can prove that transport-to-row
|
|
|
|
|
// path end to end.
|
2026-08-19 12:51:58 +08:00
|
|
|
import { resolve } from 'node:path'
|
test(web): pin the parallel todo plan in the assembled application
The `+N` active count rides ToolRow's non-shrinking `summarySuffix` slot,
but only jsdom package suites covered it: the ACP snapshots render no web
surface and the built-boot smoke asserts no todo row. Add
`apps/web/tests/todo-row.snapshot.ts`, which boots the built client bundles
against the keyless fixture transport and records `summary`, `suffix`, and
the plan strip's header as separate fields, so folding the count back into
the summary string changes the expected output.
The three assembled-jsdom files now share `apps/web/tests/assembled-boot.ts`
instead of each carrying its own copy of the boot entry list, bundle map,
jsdom stubs, and mount call.
Also: name the policy branch in each `allowParallelInProgress` test title so
no case asserting `true` sits under a `false` describe, reword the stale cap
comment in todo-panel.spec.tsx, and record the plan strip's real header
format in the Agent Note (per-status counts, not `<done>/<total> tasks`).
2026-08-06 12:26:27 +08:00
|
|
|
import { act, fireEvent, screen, waitFor, within } from '@testing-library/react'
|
|
|
|
|
import { expect, it } from 'vitest'
|
|
|
|
|
import { installAssembledBootEnv, mountAssembledApp } from './assembled-boot.ts'
|
2026-07-29 18:59:46 +08:00
|
|
|
|
test(web): pin the parallel todo plan in the assembled application
The `+N` active count rides ToolRow's non-shrinking `summarySuffix` slot,
but only jsdom package suites covered it: the ACP snapshots render no web
surface and the built-boot smoke asserts no todo row. Add
`apps/web/tests/todo-row.snapshot.ts`, which boots the built client bundles
against the keyless fixture transport and records `summary`, `suffix`, and
the plan strip's header as separate fields, so folding the count back into
the summary string changes the expected output.
The three assembled-jsdom files now share `apps/web/tests/assembled-boot.ts`
instead of each carrying its own copy of the boot entry list, bundle map,
jsdom stubs, and mount call.
Also: name the policy branch in each `allowParallelInProgress` test title so
no case asserting `true` sits under a `false` describe, reword the stale cap
comment in todo-panel.spec.tsx, and record the plan strip's real header
format in the Agent Note (per-status counts, not `<done>/<total> tasks`).
2026-08-06 12:26:27 +08:00
|
|
|
installAssembledBootEnv()
|
2026-07-29 18:59:46 +08:00
|
|
|
|
2026-08-19 12:51:58 +08:00
|
|
|
const buildEnvironmentModulePath = '../../../scripts/client-build-environment.ts'
|
|
|
|
|
const buildEnvironmentModule: unknown = await import(buildEnvironmentModulePath)
|
|
|
|
|
if (typeof buildEnvironmentModule !== 'object' || buildEnvironmentModule === null) {
|
|
|
|
|
throw new TypeError('client build environment module must be an object')
|
|
|
|
|
}
|
|
|
|
|
const readClientBuildRecord: unknown = Reflect.get(buildEnvironmentModule, 'readClientBuildRecord')
|
|
|
|
|
if (!isBuildRecordReader(readClientBuildRecord)) {
|
|
|
|
|
throw new TypeError('client build environment module must export readClientBuildRecord')
|
|
|
|
|
}
|
|
|
|
|
const record: unknown = readClientBuildRecord(resolve(import.meta.dirname, '../../..'))
|
|
|
|
|
if (typeof record !== 'object' || record === null) throw new TypeError('client build record must be an object')
|
2026-08-21 16:34:42 +08:00
|
|
|
const clientBuildEnvironment = requireObject(
|
|
|
|
|
Reflect.get(record, 'environment'),
|
|
|
|
|
'client build record environment must be an object',
|
|
|
|
|
)
|
2026-08-19 12:51:58 +08:00
|
|
|
|
|
|
|
|
function isBuildRecordReader(value: unknown): value is (root: string) => unknown {
|
|
|
|
|
return typeof value === 'function'
|
|
|
|
|
}
|
|
|
|
|
|
2026-08-21 16:34:42 +08:00
|
|
|
function requireObject(value: unknown, message: string): Record<string, unknown> {
|
|
|
|
|
if (!isUnknownRecord(value)) throw new TypeError(message)
|
|
|
|
|
return value
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
function isUnknownRecord(value: unknown): value is Record<string, unknown> {
|
|
|
|
|
return typeof value === 'object' && value !== null
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/** Read one optional string from the verified client build record. */
|
|
|
|
|
function clientBuildValue(name: string): string | undefined {
|
|
|
|
|
const value = clientBuildEnvironment[name]
|
|
|
|
|
if (value !== undefined && typeof value !== 'string') {
|
|
|
|
|
throw new TypeError(`client build record environment ${name} must be a string`)
|
|
|
|
|
}
|
|
|
|
|
return value
|
|
|
|
|
}
|
|
|
|
|
|
test(web): shrink the assembled jsdom lane to one built-bundle boot smoke
The seven behavior-pinning snapshots (workspace-flow, slash-flow,
todo-display, session-title, session-actions, terminal-card,
code-mode-fixture) asserted per-package behavior through the whole
built app: every assertion now lives in the owning package's suite at
equal strength (SlotTestRuntime benches assemble the same plugin apply
over the production slot machinery), while the assembled layer kept
re-failing on unrelated churn at 10s-timeout debugging cost.
What only this lane can prove is the artifact plane: lib/client.js
bundles loading through the ModuleLoader path, staged boot activation
across the inject layers, per-plugin CSS injection, and a journey
reaching chat content over the fixture transport. built-boot.snapshot.ts
pins exactly that, and nothing else — behavior assertions belong to the
package suites.
2026-07-29 23:45:39 +08:00
|
|
|
it('boots the built plugin graph and renders a fixture session end to end', async () => {
|
test(web): pin the parallel todo plan in the assembled application
The `+N` active count rides ToolRow's non-shrinking `summarySuffix` slot,
but only jsdom package suites covered it: the ACP snapshots render no web
surface and the built-boot smoke asserts no todo row. Add
`apps/web/tests/todo-row.snapshot.ts`, which boots the built client bundles
against the keyless fixture transport and records `summary`, `suffix`, and
the plan strip's header as separate fields, so folding the count back into
the summary string changes the expected output.
The three assembled-jsdom files now share `apps/web/tests/assembled-boot.ts`
instead of each carrying its own copy of the boot entry list, bundle map,
jsdom stubs, and mount call.
Also: name the policy branch in each `allowParallelInProgress` test title so
no case asserting `true` sits under a `false` describe, reword the stale cap
comment in todo-panel.spec.tsx, and record the plan strip's real header
format in the Agent Note (per-status counts, not `<done>/<total> tasks`).
2026-08-06 12:26:27 +08:00
|
|
|
mountAssembledApp()
|
2026-07-29 18:59:46 +08:00
|
|
|
|
test(web): shrink the assembled jsdom lane to one built-bundle boot smoke
The seven behavior-pinning snapshots (workspace-flow, slash-flow,
todo-display, session-title, session-actions, terminal-card,
code-mode-fixture) asserted per-package behavior through the whole
built app: every assertion now lives in the owning package's suite at
equal strength (SlotTestRuntime benches assemble the same plugin apply
over the production slot machinery), while the assembled layer kept
re-failing on unrelated churn at 10s-timeout debugging cost.
What only this lane can prove is the artifact plane: lib/client.js
bundles loading through the ModuleLoader path, staged boot activation
across the inject layers, per-plugin CSS injection, and a journey
reaching chat content over the fixture transport. built-boot.snapshot.ts
pins exactly that, and nothing else — behavior assertions belong to the
package suites.
2026-07-29 23:45:39 +08:00
|
|
|
// The sidebar renders from the boot graph: every inject layer activated.
|
|
|
|
|
const tree = await screen.findByRole('tree', { name: 'Sessions' }, { timeout: 10_000 })
|
2026-08-21 16:34:42 +08:00
|
|
|
if (clientBuildValue('DSH_CLIENT_BUILD_PROFILE') === 'official') {
|
|
|
|
|
expect(document.querySelector('svg[viewBox="26 0 156 24"]')).not.toBeNull()
|
|
|
|
|
expect(screen.queryByText('DSH Local Build')).toBeNull()
|
|
|
|
|
} else {
|
|
|
|
|
expect(document.querySelector('svg[viewBox="0 0 23.16 17.04"]')).not.toBeNull()
|
|
|
|
|
const version = clientBuildValue('DSH_CLIENT_VERSION')
|
|
|
|
|
if (version === undefined) throw new Error('default client build record must carry DSH_CLIENT_VERSION')
|
|
|
|
|
const commit = clientBuildValue('DSH_CLIENT_COMMIT_HASH')
|
|
|
|
|
const buildVersion = version
|
|
|
|
|
+ (commit === undefined ? '' : `-${commit}`)
|
|
|
|
|
+ (clientBuildValue('DSH_CLIENT_GIT_DIRTY') === 'true' ? '-dirty' : '')
|
2026-08-24 15:03:49 +08:00
|
|
|
screen.getByText('DSH Local Build')
|
2026-08-21 16:34:42 +08:00
|
|
|
screen.getByText(buildVersion)
|
|
|
|
|
}
|
2026-08-12 01:32:08 +08:00
|
|
|
// The compact layout dropped group session counts; the fixture workspace
|
|
|
|
|
// group row renders immediately with its sessions beneath it.
|
|
|
|
|
const fixtureGroup = (await within(tree).findAllByText('fixture'))
|
|
|
|
|
.map(el => el.closest<HTMLElement>('[role="treeitem"]'))
|
|
|
|
|
.find(el => el?.getAttribute('aria-expanded') !== null)
|
|
|
|
|
if (fixtureGroup === undefined) throw new Error('fixture Workspace group missing')
|
2026-07-29 18:59:46 +08:00
|
|
|
|
2026-08-04 17:14:58 +08:00
|
|
|
// The resident fixture has both a question and an approval; composer routing
|
|
|
|
|
// exposes the question first, and the assembled workspace plugin mirrors that
|
|
|
|
|
// actionable wait instead of the underlying running state.
|
2026-07-30 02:13:02 -07:00
|
|
|
const waitingTitle = await within(tree).findByText('Fixture 历史会话')
|
2026-07-30 02:40:31 -07:00
|
|
|
const waitingRow = waitingTitle.closest<HTMLElement>('[role="treeitem"]')
|
|
|
|
|
if (waitingRow === null) throw new Error('fixture Session title must belong to a tree row')
|
|
|
|
|
expect(waitingRow.querySelector('[data-state="warning"]')).not.toBeNull()
|
|
|
|
|
expect(waitingRow.querySelector('[data-state="ongoing"]')).toBeNull()
|
2026-08-04 17:14:58 +08:00
|
|
|
within(waitingRow).getByText('Waiting for answer')
|
2026-07-30 02:13:02 -07:00
|
|
|
|
test(web): shrink the assembled jsdom lane to one built-bundle boot smoke
The seven behavior-pinning snapshots (workspace-flow, slash-flow,
todo-display, session-title, session-actions, terminal-card,
code-mode-fixture) asserted per-package behavior through the whole
built app: every assertion now lives in the owning package's suite at
equal strength (SlotTestRuntime benches assemble the same plugin apply
over the production slot machinery), while the assembled layer kept
re-failing on unrelated churn at 10s-timeout debugging cost.
What only this lane can prove is the artifact plane: lib/client.js
bundles loading through the ModuleLoader path, staged boot activation
across the inject layers, per-plugin CSS injection, and a journey
reaching chat content over the fixture transport. built-boot.snapshot.ts
pins exactly that, and nothing else — behavior assertions belong to the
package suites.
2026-07-29 23:45:39 +08:00
|
|
|
// Opening a session reaches chat content through the fixture transport.
|
2026-07-30 02:40:31 -07:00
|
|
|
fireEvent.click(waitingTitle)
|
test(web): shrink the assembled jsdom lane to one built-bundle boot smoke
The seven behavior-pinning snapshots (workspace-flow, slash-flow,
todo-display, session-title, session-actions, terminal-card,
code-mode-fixture) asserted per-package behavior through the whole
built app: every assertion now lives in the owning package's suite at
equal strength (SlotTestRuntime benches assemble the same plugin apply
over the production slot machinery), while the assembled layer kept
re-failing on unrelated churn at 10s-timeout debugging cost.
What only this lane can prove is the artifact plane: lib/client.js
bundles loading through the ModuleLoader path, staged boot activation
across the inject layers, per-plugin CSS injection, and a journey
reaching chat content over the fixture transport. built-boot.snapshot.ts
pins exactly that, and nothing else — behavior assertions belong to the
package suites.
2026-07-29 23:45:39 +08:00
|
|
|
await waitFor(() => {
|
2026-07-31 10:48:50 +08:00
|
|
|
expect(document.querySelector('[data-sample="bash"]')).not.toBeNull()
|
test(web): shrink the assembled jsdom lane to one built-bundle boot smoke
The seven behavior-pinning snapshots (workspace-flow, slash-flow,
todo-display, session-title, session-actions, terminal-card,
code-mode-fixture) asserted per-package behavior through the whole
built app: every assertion now lives in the owning package's suite at
equal strength (SlotTestRuntime benches assemble the same plugin apply
over the production slot machinery), while the assembled layer kept
re-failing on unrelated churn at 10s-timeout debugging cost.
What only this lane can prove is the artifact plane: lib/client.js
bundles loading through the ModuleLoader path, staged boot activation
across the inject layers, per-plugin CSS injection, and a journey
reaching chat content over the fixture transport. built-boot.snapshot.ts
pins exactly that, and nothing else — behavior assertions belong to the
package suites.
2026-07-29 23:45:39 +08:00
|
|
|
}, { timeout: 10_000 })
|
2026-08-17 23:55:36 +08:00
|
|
|
// The generated bundle roster mounts the question UI before the approval UI.
|
|
|
|
|
// Skip the resident fixture's three questions, then resolve its approval so
|
|
|
|
|
// the ordinary composer bar (which owns ContextMeter) resumes.
|
|
|
|
|
for (let index = 0; index < 3; index += 1) {
|
|
|
|
|
fireEvent.click(await screen.findByRole('button', { name: 'Skip this question' }))
|
|
|
|
|
}
|
2026-08-06 00:21:17 +08:00
|
|
|
fireEvent.click(await screen.findByRole('button', { name: 'Allow once' }))
|
|
|
|
|
|
|
|
|
|
// The fixture mirrors all three token-meter projections, so the assembled
|
|
|
|
|
// ContextMeter reaches its composition panel instead of only the occupancy
|
|
|
|
|
// fallback path.
|
|
|
|
|
const contextTrigger = await screen.findByRole('button', { name: /of context used/ })
|
|
|
|
|
fireEvent.click(contextTrigger)
|
|
|
|
|
const contextPanel = await screen.findByRole('dialog', { name: 'of context used' })
|
|
|
|
|
within(contextPanel).getByText('System prompt')
|
|
|
|
|
within(contextPanel).getByText('Tools')
|
|
|
|
|
within(contextPanel).getByText('Messages')
|
|
|
|
|
|
2026-07-30 21:36:42 +08:00
|
|
|
// The write/edit turns render a real diff card through the assembled graph
|
2026-07-31 16:34:16 +08:00
|
|
|
// (the keyed FileMutationRow composing ToolRow + DiffBlock), not just the
|
|
|
|
|
// fixture's raw text. The card is collapsed by default, so expand each edit/
|
|
|
|
|
// write row first. The write turn's `hello fixture\n` proves the terminator
|
|
|
|
|
// rule end to end: a trailing newline terminates its line, so the footer reads
|
|
|
|
|
// `+1` (not a phantom `+2`) and one distinct file. The `+ ` prefix is a CSS
|
|
|
|
|
// ::before, so it is absent from textContent — assert on the line body and the
|
|
|
|
|
// footer.
|
|
|
|
|
const mutationRows = [...document.querySelectorAll('[data-variant="write"],[data-variant="edit"]')]
|
|
|
|
|
expect(mutationRows.length).toBeGreaterThan(0)
|
|
|
|
|
for (const row of mutationRows) {
|
|
|
|
|
const toggle = row.querySelector('[data-expandable]')
|
|
|
|
|
if (toggle !== null) act(() => { fireEvent.click(toggle) })
|
|
|
|
|
}
|
2026-07-30 21:51:27 +08:00
|
|
|
const diffCards = [...document.querySelectorAll('[data-diff]')]
|
2026-07-30 21:36:42 +08:00
|
|
|
expect(diffCards.length).toBeGreaterThan(0)
|
2026-07-30 21:51:27 +08:00
|
|
|
const footers = diffCards.map(card => card.textContent ?? '')
|
|
|
|
|
expect(footers.some(text => text.includes('hello fixture') && text.includes('+1 -0 · 1 file'))).toBe(true)
|
2026-07-30 21:36:42 +08:00
|
|
|
|
2026-07-30 20:42:29 +08:00
|
|
|
// The web render intent reaches the assembled boot graph: the fixture's
|
|
|
|
|
// web_search / web_fetch turns render their keyed WebRow cards, proving the
|
|
|
|
|
// registration, wire projection, and card rendering survive the real bundle
|
2026-07-31 16:34:16 +08:00
|
|
|
// path (not just the per-package src benches). WebRow composes ToolRow, so the
|
|
|
|
|
// card is collapsed behind the row; the keyed row is pinned by its `data-tool`
|
|
|
|
|
// (ToolRow sets it from the wire tool name).
|
|
|
|
|
const webSearchRow = await waitFor(() => {
|
|
|
|
|
const row = document.querySelector('[data-tool="web_search"]')
|
|
|
|
|
expect(row).not.toBeNull()
|
|
|
|
|
expect(document.querySelector('[data-tool="web_fetch"]')).not.toBeNull()
|
|
|
|
|
return row!
|
|
|
|
|
}, { timeout: 10_000 })
|
|
|
|
|
// Expand the web_search row to prove its WebBlock card renders end to end.
|
|
|
|
|
const webToggle = webSearchRow.querySelector('[data-expandable]')
|
|
|
|
|
if (webToggle !== null) act(() => { fireEvent.click(webToggle) })
|
2026-07-30 20:42:29 +08:00
|
|
|
await waitFor(() => {
|
2026-07-31 16:34:16 +08:00
|
|
|
expect(webSearchRow.querySelector('[data-web]')).not.toBeNull()
|
test(web): shrink the assembled jsdom lane to one built-bundle boot smoke
The seven behavior-pinning snapshots (workspace-flow, slash-flow,
todo-display, session-title, session-actions, terminal-card,
code-mode-fixture) asserted per-package behavior through the whole
built app: every assertion now lives in the owning package's suite at
equal strength (SlotTestRuntime benches assemble the same plugin apply
over the production slot machinery), while the assembled layer kept
re-failing on unrelated churn at 10s-timeout debugging cost.
What only this lane can prove is the artifact plane: lib/client.js
bundles loading through the ModuleLoader path, staged boot activation
across the inject layers, per-plugin CSS injection, and a journey
reaching chat content over the fixture transport. built-boot.snapshot.ts
pins exactly that, and nothing else — behavior assertions belong to the
package suites.
2026-07-29 23:45:39 +08:00
|
|
|
}, { timeout: 10_000 })
|
2026-07-29 18:59:46 +08:00
|
|
|
|
test(web): shrink the assembled jsdom lane to one built-bundle boot smoke
The seven behavior-pinning snapshots (workspace-flow, slash-flow,
todo-display, session-title, session-actions, terminal-card,
code-mode-fixture) asserted per-package behavior through the whole
built app: every assertion now lives in the owning package's suite at
equal strength (SlotTestRuntime benches assemble the same plugin apply
over the production slot machinery), while the assembled layer kept
re-failing on unrelated churn at 10s-timeout debugging cost.
What only this lane can prove is the artifact plane: lib/client.js
bundles loading through the ModuleLoader path, staged boot activation
across the inject layers, per-plugin CSS injection, and a journey
reaching chat content over the fixture transport. built-boot.snapshot.ts
pins exactly that, and nothing else — behavior assertions belong to the
package suites.
2026-07-29 23:45:39 +08:00
|
|
|
// Every bundle injected its plugin-owned style tag (the loader's CSS path).
|
|
|
|
|
const styleOwners = [...document.head.querySelectorAll('style[data-plugin]')]
|
|
|
|
|
.map(style => style.getAttribute('data-plugin'))
|
2026-08-08 15:29:26 +08:00
|
|
|
for (const plugin of ['@deepseek-ai/dsh-client-ui-layout', '@deepseek-ai/dsh-client-ui-sidebar', '@deepseek-ai/dsh-client-ui-conversation', '@deepseek-ai/dsh-client-ui-tool']) {
|
test(web): shrink the assembled jsdom lane to one built-bundle boot smoke
The seven behavior-pinning snapshots (workspace-flow, slash-flow,
todo-display, session-title, session-actions, terminal-card,
code-mode-fixture) asserted per-package behavior through the whole
built app: every assertion now lives in the owning package's suite at
equal strength (SlotTestRuntime benches assemble the same plugin apply
over the production slot machinery), while the assembled layer kept
re-failing on unrelated churn at 10s-timeout debugging cost.
What only this lane can prove is the artifact plane: lib/client.js
bundles loading through the ModuleLoader path, staged boot activation
across the inject layers, per-plugin CSS injection, and a journey
reaching chat content over the fixture transport. built-boot.snapshot.ts
pins exactly that, and nothing else — behavior assertions belong to the
package suites.
2026-07-29 23:45:39 +08:00
|
|
|
expect(styleOwners).toContain(plugin)
|
|
|
|
|
}
|
2026-07-29 18:59:46 +08:00
|
|
|
})
|
2026-08-22 21:19:39 +08:00
|
|
|
|
|
|
|
|
it('boots without ui-chat and does not select another conversation view implicitly', async () => {
|
|
|
|
|
mountAssembledApp('?fixture', { exclude: ['@deepseek-ai/dsh-client-ui-chat'] })
|
|
|
|
|
|
|
|
|
|
const tree = await screen.findByRole('tree', { name: 'Sessions' }, { timeout: 10_000 })
|
|
|
|
|
const boot = Reflect.get(window, '__DSH_BOOT__') as { entries: Array<{ id: string }> } | undefined
|
|
|
|
|
expect(boot?.entries.some(entry => entry.id === '@deepseek-ai/dsh-client-ui-chat')).toBe(false)
|
|
|
|
|
const sessionTitle = await within(tree).findByText('Fixture 历史会话')
|
|
|
|
|
fireEvent.click(sessionTitle)
|
|
|
|
|
await waitFor(() => {
|
|
|
|
|
expect(document.querySelector('[data-slot="conversation.session"]')).not.toBeNull()
|
|
|
|
|
}, { timeout: 10_000 })
|
|
|
|
|
expect(document.querySelector('[data-slot="conversation.view"]')).toBeNull()
|
|
|
|
|
})
|