From 66fe9a027a019e2f920ef11d572f18f8ee8435a7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?C=C3=A9sar=20Zaragoza=20Cort=C3=A9s?=
 <cesarzc@microsoft.com>
Date: Thu, 15 Feb 2024 23:02:30 -0800
Subject: [PATCH] Modify 'getAllKatas works' test to reduce friction when
 working on new katas (#1160)

This is meant to make it easier for people authoring on new katas.
---
 npm/test/basics.js | 10 ++--------
 1 file changed, 2 insertions(+), 8 deletions(-)

diff --git a/npm/test/basics.js b/npm/test/basics.js
index fa977061ac..08543c43da 100644
--- a/npm/test/basics.js
+++ b/npm/test/basics.js
@@ -272,15 +272,9 @@ async function validateKata(
   }
 }
 
-test("all katas work", async () => {
+test("getAllKatas works", async () => {
   const katas = await getAllKatas();
-  // N.B. If you update the expected katas count, make sure to add a validation test for your newly added kata.
-  const expectedKatasCount = 9;
-  assert.equal(
-    katas.length,
-    expectedKatasCount,
-    `Expected ${expectedKatasCount} katas, but found ${katas.length} katas`,
-  );
+  assert.ok(katas.length > 0, "katas should not be empty");
 });
 
 test("getting_started kata is valid", async () => {