Function initializeAndLaunchBrowser

tests/shutdown.test.ts:113–134

(child: Server)

}

async function initializeAndLaunchBrowser(child: Server): Promise<void> {
  await rpc(child, {
    method: 'initialize',
    params: {
      protocolVersion: '2024-11-05',
      capabilities: {},
      clientInfo: {name: 'shutdown-test', version: '0.0.1'},
    },
  });
  notify(child, {method: 'notifications/initialized'});
  // navigate_page forces a real Chrome launch — this is what reproduces
  // the hang in #2116. Without an active Chrome subprocess, stdin EOF
  // would close the event loop on its own and shutdown would look fine
  // even with broken handlers.
  await rpc(child, {
    method: 'tools/call',
    params: {
      name: 'navigate_page',
      arguments: {url: 'about:blank'},
    },
  });
}

describe('shutdown', () => {
  it('exits within budget on stdin EOF after Chrome launch', async () => {