Test cases for Token queue api

[nandkishorr]

Merge Checklist

• Tests added/fixed
• Update docs in /docs
• Linting Complete
• Any other necessary step

Only PR's with test cases included and passing lint and test pipelines will be reviewed

@ohcnetwork/care-backend-maintainers @ohcnetwork/care-backend-admins

Summary by CodeRabbit

• Bug Fixes
  • Corrected error message when users lack permission to update token queues, ensuring accurate feedback is provided.

[coderabbitai]

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

💤 Files selected but had no reviewable changes (1)

• care/emr/tests/test_token_queue_api.py

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

📝 Walkthrough

Walkthrough

A single error message correction in the token queue authorization logic. The permission denied error text for the update operation was corrected from referencing "create" to "update," ensuring the message accurately reflects the attempted action.

Changes

Cohort / File(s)	Change Summary
Error Message Correction care/emr/api/viewsets/scheduling/token_queue.py	Updated PermissionDenied error message in authorize_update from "You do not have permission to create token queue" to "You do not have permission to update token queue" for accuracy

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

• Single-line error message text correction with no logic or control flow changes

Pre-merge checks and finishing touches

❌ Failed checks (3 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title claims to add test cases, but the actual change only fixes error messaging in the token queue update permission check.	Update the title to accurately reflect the actual change, such as 'Fix permission error message for token queue updates' or 'Update error text in token queue authorization'.
Description check	⚠️ Warning	The PR description is missing critical sections: no 'Proposed Changes', 'Associated Issue', or explanation of what was actually changed.	Add the missing sections including a brief description of the changes made and link to the associated issue explaining how this addresses it.
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.

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.96%. Comparing base (e98e3cd) to head (844418b).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3349      +/-   ##
===========================================
+ Coverage    73.19%   73.96%   +0.76%     
===========================================
  Files          435      435              
  Lines        19729    19729              
  Branches      2132     2132              
===========================================
+ Hits         14441    14592     +151     
+ Misses        4849     4691     -158     
- Partials       439      446       +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.