From 0245d8bf5b7d31a3311da2fa878974fb4caa2c10 Mon Sep 17 00:00:00 2001
From: James Garbutt <43081j@users.noreply.github.com>
Date: Wed, 8 May 2024 16:55:49 +0100
Subject: [PATCH] test(core-common): migrate to vitest test functions

One of the `get-renderer-name` tests is failing, but this goes uncaught
since vitest does not understand node's test runner output.

This basically moves to using `it` from vitest rather than `node:test`,
thus introducing a failing test. The failing test has then been fixed.
---
 code/lib/core-common/src/utils/get-renderer-name.test.ts | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/code/lib/core-common/src/utils/get-renderer-name.test.ts b/code/lib/core-common/src/utils/get-renderer-name.test.ts
index f5d10959405c..09c31f36b4f1 100644
--- a/code/lib/core-common/src/utils/get-renderer-name.test.ts
+++ b/code/lib/core-common/src/utils/get-renderer-name.test.ts
@@ -1,15 +1,14 @@
-import { it } from 'node:test';
-import { describe, expect } from 'vitest';
+import { describe, expect, test } from 'vitest';
 import { extractProperRendererNameFromFramework } from './get-renderer-name';
 
 describe('get-renderer-name', () => {
   describe('extractProperRendererNameFromFramework', () => {
-    it('should return the renderer name for a known framework', async () => {
-      const renderer = await extractProperRendererNameFromFramework('@storybook/react');
+    test('should return the renderer name for a known framework', async () => {
+      const renderer = await extractProperRendererNameFromFramework('@storybook/react-vite');
       expect(renderer).toEqual('react');
     });
 
-    it('should return null for an unknown framework', async () => {
+    test('should return null for an unknown framework', async () => {
       const renderer = await extractProperRendererNameFromFramework('@third-party/framework');
       expect(renderer).toBeNull();
     });