fix: update upstream test assertions for Ironclaw branding

- Telegram pairing test: expect 'ironclaw' not 'openclaw' in CLI hint
- Status update test: expect 'ironclaw update' not 'openclaw update'

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
kumarabhirup 2026-02-21 19:12:00 -08:00
parent 45f86187ed
commit 177ce3c3e2
No known key found for this signature in database
GPG Key ID: DB7CA2289CAB0167
2 changed files with 2 additions and 2 deletions

View File

@ -141,7 +141,7 @@ describe("formatUpdateAvailableHint", () => {
});
expect(formatUpdateAvailableHint(update)).toBe(
`Update available (git behind 2 · npm ${latestVersion}). Run: openclaw update`,
`Update available (git behind 2 · npm ${latestVersion}). Run: ironclaw update`,
);
});
});

View File

@ -313,7 +313,7 @@ describe("createTelegramBot", () => {
expect(pairingText, testCase.name).toContain("Your Telegram user id: 999");
expect(pairingText, testCase.name).toContain("Pairing code:");
expect(pairingText, testCase.name).toContain("PAIRME12");
expect(pairingText, testCase.name).toContain("openclaw pairing approve telegram PAIRME12");
expect(pairingText, testCase.name).toContain("ironclaw pairing approve telegram PAIRME12");
expect(pairingText, testCase.name).not.toContain("<code>");
}
}