Commit 7c2c0907 authored by Jimmy Lai's avatar Jimmy Lai

fix: update tests that relied on 'Starting...' message

The 'Starting...' message was removed from dev server output.
Update tests to use 'Ready in' or other patterns instead.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: 's avatarClaude Opus 4.5 <noreply@anthropic.com>
parent 055db66b
......@@ -6,7 +6,8 @@ describe('next start without next build', () => {
files: __dirname,
skipStart: true,
startCommand: `pnpm next start`,
serverReadyPattern: /✓ Starting.../,
// Match "Ready in" or the error message since there's no build
serverReadyPattern: /Ready in|Could not find a production build/,
})
await next.start()
......
......@@ -11,7 +11,10 @@ describe('instrumentation-order', () => {
await next.fetch('/')
await retry(async () => {
const serverLog = next.cliOutput.split('Starting...')[1]
// Split on "Ready in" to get the logs after server startup
const readyIndex = next.cliOutput.indexOf('Ready in')
const serverLog =
readyIndex !== -1 ? next.cliOutput.slice(readyIndex) : next.cliOutput
const cliOutputLines = serverLog.split('\n')
const ORDERED_LOGS = [
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment