Refactor: src/setup/checkEnvFile/checkEnvFile.test.ts from Jest to Vitest

src/setup/checkEnvFile/checkEnvFile.test.ts → src/setup/checkEnvFile/checkEnvFile.spec.ts

@@ -1,25 +1,35 @@
 import fs from 'fs';
 import { checkEnvFile } from './checkEnvFile';
+import { vi } from 'vitest';
 
-jest.mock('fs');
+/**
+ * This file contains unit tests for the `checkEnvFile` function.
+ *
+ * The tests cover:
+ * - Behavior when the `.env` file is missing required keys and appending them appropriately.
+ * - Ensuring no changes are made when all keys are present in the `.env` file.
+ *
+ * These tests utilize Vitest for test execution and mock the `fs` module to simulate file operations.
+ */
+
+vi.mock('fs');
 
 describe('checkEnvFile', () => {
   beforeEach(() => {
-    jest.resetAllMocks();
+    vi.resetAllMocks();
   });
 
   it('should append missing keys to the .env file', () => {
     const envContent = 'EXISTING_KEY=existing_value\n';
     const envExampleContent =
       'EXISTING_KEY=existing_value\nNEW_KEY=default_value\n';
 
-    jest
-      .spyOn(fs, 'readFileSync')
+    vi.spyOn(fs, 'readFileSync')
       .mockReturnValueOnce(envContent)
       .mockReturnValueOnce(envExampleContent)
       .mockReturnValueOnce(envExampleContent);
 
-    jest.spyOn(fs, 'appendFileSync');
+    vi.spyOn(fs, 'appendFileSync');
 
     checkEnvFile();
 
@@ -33,12 +43,11 @@ describe('checkEnvFile', () => {
     const envContent = 'EXISTING_KEY=existing_value\n';
     const envExampleContent = 'EXISTING_KEY=existing_value\n';
 
-    jest
-      .spyOn(fs, 'readFileSync')
+    vi.spyOn(fs, 'readFileSync')
       .mockReturnValueOnce(envContent)
       .mockReturnValueOnce(envExampleContent);
 
-    jest.spyOn(fs, 'appendFileSync');
+    vi.spyOn(fs, 'appendFileSync');
 
     checkEnvFile();