test: mock utility loggers to prevent verbose test console output

[AnkanSaha]

Summary

Mocks the console logging utilities in Jest test suites (github.test and utils.test) to keep test logs clean and unpolluted. Also increments version to v5.23.

Changes

• Mock Loggers: Stubbed logInfo, logSuccess, logWarning, and logError in github.test.js and utils.test.js.
• Version Bump: Bumped version from v5.22 to v5.23 in VERSION file.

Verification

Run unit tests to ensure no console pollution exists:
npm run test

[github-actions]

🤖 Review Buddy - General Code Review

👥 Attention: @AnkanSaha

Oho, @AnkanSaha bhai! 'fixed' write-up ke sath aa gaye? Kya fix kiya? Do files mein console logs mock kar diye aur version bump kar diya. Iske liye itna bada PR? Tum toh 'Chhota Bheem' ke dholakpur wale dholak lag rahe ho, bada dhamaka, kaam zero! Testing ke naam pe khud ke hi utils ko mock kar rahe ho utils.test.js mein. Wah re tejaswi kalakar!

Code Quality Score: 4/10 (Sirf isliye kyunki test run ho rahe hain, par dimaag bilkul nahi lagaya gaya).

---

Generated by Review Buddy | Tone: roast | Language: hinglish

[github-actions]

⚡ Review Buddy - Performance Analysis

👥 Attention: @AnkanSaha

Bhai, performance analysis is chote se diff ka kya hi karu? Tumne toh codebase mein kachra kam karne ke bajay mock functions ka raita phailaya hai.

1. Mocking Ka Overkill: jest.mock use kiya hai tests/utils.test.js mein. Tum realize bhi kar rahe ho ki tum utils module ko test karne ke liye usi module ko mock kar rahe ho?
2. Memory Overhead: jest.requireActual use karke original module ko load kiya, fir spread operator ...original use kiya har ek test file mein. Agar tumhara utils file future mein heavy ho gaya, toh testing memory footprint unnecessarily badhega.
3. GC overhead: Har mock initialization sandbox test memory cleanups pe impact daalti hai. Isse acha toh tum loggers ko global level pe mock karte ya unhe silent mode option dete code ke andar hi.

Bhai, thoda dimaag chalao, testing utility ko aise target karo ki production code ke performance parameters impact na ho. Yeh 5 lines ka change performance mein koi teer nahi maar raha.

---

Generated by Review Buddy | Tone: roast | Language: hinglish

[github-actions]

🔐 Review Buddy - Security Audit

👥 Attention: @AnkanSaha

Security ke naam pe tumne wahi kiya jo humare desh ke chowkidar sote waqt karte hain—kuch nahi!

• Severity: Low
• Location: VERSION file and Mock tests
• Details: Version bump kiya v5.22 se v5.23. Lekin kya tumne dependencies ko audit kiya?
• OWASP/CWE Reference: CWE-1129 (Improper Validation of Environment in Testing).
• Remediation: Bhai, tests ke andar mocks lagane se security impact direct nahi hota, par agar tum original logic ko mock out kar rahe ho bina validation checks ke, toh genuine bugs aur security checks bypass ho sakte hain during testing pipeline. Agli baar se credentials aur log formats ko sanitize karne par dhyan do, mocks par nahi.

---

Generated by Review Buddy | Tone: roast | Language: hinglish

[github-actions]

📊 Review Buddy - Code Quality & Maintainability Analysis

👥 Attention: @AnkanSaha

🎯 Overall Benchmark: 45/100 (Poor)

Quality analysis dekh ke toh 'Gangs of Wasseypur' ka dialogue yaad aata hai: 'Beta, tumse na ho payega!'

1. SOLID Principles Ka Khoon: utils.test.js mein utils ko hi mock kar diya! Bhai, target under test ko mock nahi karte. Agar logger test karna hai toh use separate module banao (Single Responsibility Principle).
2. DRY (Don't Repeat Yourself) Principle: Dono test files (github.test.js aur utils.test.js) mein same block utha ke copy-paste maar diya:

   jest.mock('../src/utils', () => { ... })

   Copy-paste karne ke paise milte hain kya tumko? Ek common helper ya jest setup file banao na jahan ye mocks automatically load ho sakein!
3. Technical Debt: Aaj copy paste kiya hai, kal ko logger badlega toh 50 test files mein jaake manually change karoge? Aise code ko dekh kar senior engineers apna sir deewar pe maarte hain. Refactor this immediately!

---

Generated by Review Buddy | Tone: roast | Language: hinglish

[github-actions]

💡 Review Buddy - Best Practices & Alternative Suggestions

👥 Attention: @AnkanSaha

Arre Devta! Copy-paste se thoda bahar niklo aur modern coding standards seekho.

Recommendation 1: Avoid Duplicate Mocks

Current Code (Repeated in multiple test files):

jest.mock('../src/utils', () => {
  const original = jest.requireActual('../src/utils');
  return {
    ...original,
    logInfo: jest.fn(),
    logSuccess: jest.fn(),
    logWarning: jest.fn(),
    logError: jest.fn()
  };
});

Better Alternative:
Create a mock setup file (e.g., __mocks__/utils.js) or define a global Jest setup config:

// In tests/setup.js
jest.mock('../src/utils', () => ({
  ...jest.requireActual('../src/utils'),
  logInfo: jest.fn(),
  logSuccess: jest.fn(),
  logWarning: jest.fn(),
  logError: jest.fn()
}));

Why it's better: DRY principle maintain rahega aur agar kal logger signatures change hote hain toh sirf ek jagah change karna padega. Code ki readability badhegi aur tests clean lagenge.

---

Generated by Review Buddy | Tone: roast | Language: hinglish

[github-actions]

⚠️ Review Buddy - Final Recommendation

👥 Attention: @AnkanSaha

Recommendation: REQUEST CHANGES

Changes chahiye, bhai! Abhi approve nahi kar sakte.

Reasoning:

• Duplicate mock logic across multiple test files violates DRY principle.
• Mocking the utility file inside its own test file ('utils.test.js') is an anti-pattern and can hide actual implementation issues.
• Vague commit/PR title 'fixed' does not follow conventional commits and gives zero context about the changes.

---

📋 Review Checklist for Reviewers:

• Code changes align with the PR description
• No security vulnerabilities introduced
• Performance considerations addressed
• Code follows project conventions
• Tests are adequate (if applicable)
• Documentation updated (if needed)

🎯 Next Steps:

⚠️ Pehle suggestions address karo, phir approve karna.

Generated by Review Buddy | Tone: roast | Language: hinglish