Skip to content

🧪 [testing improvement description] Add tests for SmsManagerEjb#3

Open
ManupaKDU wants to merge 1 commit into
developmentfrom
testing-improvement-smsmanager-2765113556006909216
Open

🧪 [testing improvement description] Add tests for SmsManagerEjb#3
ManupaKDU wants to merge 1 commit into
developmentfrom
testing-improvement-smsmanager-2765113556006909216

Conversation

@ManupaKDU

Copy link
Copy Markdown

🎯 What: The testing gap addressed in SmsManagerEjb: createSmsForCDoctorRemider by writing tests that assert string templates are formatted correctly for doctor reminder messages.
📊 Coverage: Null session instance, and completely valid instance scenarios are now covered by unit tests.
Result: Increased test coverage for SmsManagerEjb, ensuring robust and safe modifications in the future.


PR created automatically by Jules for task 2765113556006909216 started by @manupawickramasinghe

Co-authored-by: manupawickramasinghe <73810867+manupawickramasinghe@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

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

manupawickramasinghe pushed a commit that referenced this pull request Jun 10, 2026
…21347

- saveDisposalIssueDraft(): release transient stock holds via
  userStockController.retiredAllUserStockContainer() before clearBill(),
  matching the pattern in resetAll() (CodeRabbit #3)
- finalizeDisposalIssue(): add billTypeAtomic == PHARMACY_DISPOSAL_ISSUE_PRE
  and department ownership checks to prevent privilege escalation (Codex #1)
- approveDisposalIssue(): same billTypeAtomic + department ownership checks;
  track deduction failures across the stock loop and surface a warning message
  when any item had insufficient stock, while preserving the existing tmpQty=0
  pattern consistent with settleDisposalIssueBill() (Codex #1, #2)
- CodeRabbit #4 (redirect vs preview): dismissed — redirecting to the finalize
  list after save matches the established pattern in Transfer Receive and
  Direct Purchase workflows
- CodeRabbit #5/#6 (boolean re-entrancy guards): dismissed — existing
  checkedBy/isRetired/isCompleted state guards are sufficient; no other
  settle/save methods in the codebase use boolean lock flags

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant