🧪 test: add tests for blog controller

[Adityavanjre]

🎯 What: This PR introduces a unit test suite for the agency/server/controllers/blogController.js and fixes a mass assignment vulnerability in updateBlog.
📊 Coverage: The test suite provides 100% statement coverage for the controller, covering all major CRUD endpoints (getBlogs, getBlogById, createBlog, updateBlog, deleteBlog), handling both success scenarios and error paths (e.g., MongoDB rejections, not found documents, role-based constraints).
✨ Result: Increased testing reliability and security for the blog controller.

---

PR created automatically by Jules for task 656758565419885959 started by @Adityavanjre

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Rate limit exceeded

@Adityavanjre has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 14 minutes and 17 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Free

Run ID: 000a4e55-e69c-4958-b2b5-e30d136b07fc

📥 Commits

Reviewing files that changed from the base of the PR and between 6051811 and 9626b57.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (7)

• agency/server/controllers/blogController.js
• agency/server/package.json
• agency/server/tests/blogController.test.js
• nexus/backend/package.json
• nexus/frontend/src/app/(dashboard)/manufacturing/machines/page.tsx
• nexus/frontend/src/lib/api.ts
• package.json

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2253bdf118

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update the lockfiles for the new test dependencies

Adding jest/supertest here without regenerating the npm lockfiles leaves the clean-install metadata stale: agency/server/package-lock.json still lists only nodemon for this package, and the root lock entry for agency/server also lacks these new devDependencies. In CI or any workflow that uses npm ci (the npm help describes it as a clean install from the lockfile), this can fail or install from dependency data that does not match package.json, so the newly added npm test script may not be reproducible until the lockfiles are updated with these dependencies.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.