Remove unused function parameter update_fields from save method in test class

[swastikiscoding]

Proposed change

Remove unused function parameter update_fields from save method in test class

Resolves #3020

This change simplifies the test code by removing an unused parameter, improving clarity.

Checklist

• Required: I read and followed the contributing guidelines
• Required: I ran make check-test locally and all tests passed
• I used AI for code, documentation, or tests in this PR

[coderabbitai]

Summary by CodeRabbit

• Tests
  • Added code quality annotation to test file.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

Added an inline comment marking an unused parameter in a test mock's save method; no change to the method signature or runtime behavior.

Changes

Cohort / File(s)	Summary
Test file — inline annotation backend/tests/apps/common/management/commands/add_project_custom_tags_test.py	Added inline comment # NOSONAR unused parameter on the existing def save(self, update_fields=None) line. No functional changes or signature edits.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR does not actually remove the parameter as required by issue #3020; instead, it only adds a NOSONAR comment inline, leaving the unused parameter in place.	Remove the update_fields parameter from the save method signature as specified in issue #3020, rather than just adding a suppression comment.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: removing the unused update_fields parameter from the save method in a test class.
Description check	✅ Passed	The description is related to the changeset, explaining that the change removes an unused parameter to simplify test code and improve clarity.
Out of Scope Changes check	✅ Passed	The change is in scope with the linked issue, targeting the correct file and method mentioned in the requirements.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e28965c and 1a4c12b.

📒 Files selected for processing (1)

• backend/tests/apps/common/management/commands/add_project_custom_tags_test.py

🚧 Files skipped from review as they are similar to previous changes (1)

• backend/tests/apps/common/management/commands/add_project_custom_tags_test.py

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Run frontend e2e tests
• GitHub Check: Run backend tests
• GitHub Check: Run frontend unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7e38d6a and e28965c.

📒 Files selected for processing (1)

• backend/tests/apps/common/management/commands/add_project_custom_tags_test.py

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-12-18T05:39:42.678Z

Learnt from: rudransh-shrivastava
Repo: OWASP/Nest PR: 2948
File: backend/apps/owasp/management/commands/owasp_generate_community_snapshot_video.py:40-40
Timestamp: 2025-12-18T05:39:42.678Z
Learning: In Django management commands, prefer using self.stdout.write(...) over print(...) for user-facing stdout output. This aligns with Django conventions and improves testability. When emitting messages, consider using self.stdout.write and, for styled messages, use self.style.SUCCESS/ERROR as appropriate to maintain consistent command output formatting. Apply this guideline to all Python files within any project's management/commands directory.

Applied to files:

• backend/tests/apps/common/management/commands/add_project_custom_tags_test.py

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud