chore: use jest table tests instead of iterating directly over languages

snyk · Apr 17, 2024 · 212eb75 · 212eb75
1 parent e0fccab
commit 212eb75
Showing 1 changed file with 7 additions and 9 deletions.
diff --git a/test/jest/acceptance/woof.spec.ts b/test/jest/acceptance/woof.spec.ts
@@ -33,14 +33,12 @@ describe('woof', () => {
   });
 
   // test each supported language code
-  languages.forEach(({ langCode, expectedWoof }) => {
-    it(`Woofs in ${langCode}`, async () => {
-      const { stdout, code, stderr } = await runSnykCLI(
-        `woof --language=${langCode}`,
-      );
-      expect(stdout).toContain(expectedWoof);
-      expect(code).toBe(0);
-      expect(stderr).toBe('');
-    });
+  test.each(languages)('Woofs in %s', async ({ langCode, expectedWoof }) => {
+    const { stdout, code, stderr } = await runSnykCLI(
+      `woof --language=${langCode}`,
+    );
+    expect(stdout).toContain(expectedWoof);
+    expect(code).toBe(0);
+    expect(stderr).toBe('');
   });
 });