fix: update logger tests to use console.log instead of console.warn

- Modified logger test cases to reflect that the warn method uses console.log in Node.js implementation.
- Updated expectations in feature-loader tests to align with the new logging behavior.
- Ensured consistent logging behavior across tests for improved clarity and accuracy.
This commit is contained in:
Shirone
2026-01-03 03:03:50 +01:00
parent d13a16111c
commit a6d665c4fa
3 changed files with 19 additions and 14 deletions

View File

@@ -122,7 +122,7 @@ describe('feature-loader.ts', () => {
{ name: 'feature-2', isDirectory: () => true } as any,
]);
const consoleSpy = vi.spyOn(console, 'warn').mockImplementation(() => {});
const consoleSpy = vi.spyOn(console, 'log').mockImplementation(() => {});
vi.mocked(fs.readFile)
.mockResolvedValueOnce(
@@ -183,7 +183,7 @@ describe('feature-loader.ts', () => {
{ name: 'feature-1', isDirectory: () => true } as any,
]);
const consoleSpy = vi.spyOn(console, 'warn').mockImplementation(() => {});
const consoleSpy = vi.spyOn(console, 'log').mockImplementation(() => {});
vi.mocked(fs.readFile).mockResolvedValue('invalid json{');