refactor: remove manual try/catch because Jest covers this case

Author: Grajales-K

Sprint-3/2-practice-tdd/repeat-str.js

@@ -27,19 +27,20 @@ function repeatStr(str, count) {
 module.exports = repeatStr;
 
 
-// Case: Manual inspection of the Error object
-// We use try/catch to log the error message to the console
-// to verify it's working as expected without breaking the test suite.
-test("Should log the specific error message to the console", () => {
-  try {
-    repeatStr("hi", -3);
-  } catch (error) {
-    console.log("Verified Error Message ->", error.message);
-
-    // Check if the message is exactly what we defined
-    expect(error.message).toBe("count cannot be negative");
-  }
 
-  // Also verify that it actually throws using Jest's built-in matcher
-  expect(() => repeatStr("hi", -3)).toThrow();
-});
+
+
+// // Case: Manual inspection of the Error object
+// // We use try/catch to log the error message to the console
+// // to verify it's working as expected without breaking the test suite.
+// test("Should log the specific error message to the console", () => {
+//   try {
+//     repeatStr("hi", -3);
+//   } catch (error) {
+//     console.log("Verified Error Message ->", error.message);
+
+//     // Check if the message is exactly what we defined
+//     expect(error.message).toBe("count cannot be negative");
+//   }
+
+// });