Skip to content

🧪 [testing improvement] Add tests for NotificationService#1215

Closed
Hardonian wants to merge 1 commit into
mainfrom
jules-15345234636447373077-af345161
Closed

🧪 [testing improvement] Add tests for NotificationService#1215
Hardonian wants to merge 1 commit into
mainfrom
jules-15345234636447373077-af345161

Conversation

@Hardonian

Copy link
Copy Markdown
Owner

🎯 What: Added a comprehensive test suite for the NotificationService in packages/adapters/src/alerting/notification-service.ts which was previously untested.
📊 Coverage: Covered all functionality including loading configurations from environment variables, mocking external API calls (Resend, Slack, PagerDuty, generic Webhooks), payload data mapping and metadata merging, severity conditionals, and multi-channel fault tolerance.
Result: A robust, reliable set of unit tests ensuring the notification mechanisms correctly map alerting context without executing real network requests during testing.


PR created automatically by Jules for task 15345234636447373077 started by @Hardonian

🎯 **What:** Added a comprehensive test suite for the `NotificationService` in `packages/adapters/src/alerting/notification-service.ts` which was previously untested.
📊 **Coverage:** Covered all functionality including loading configurations from environment variables, mocking external API calls (Resend, Slack, PagerDuty, generic Webhooks), payload data mapping and metadata merging, severity conditionals, and multi-channel fault tolerance.
✨ **Result:** A robust, reliable set of unit tests ensuring the notification mechanisms correctly map alerting context without executing real network requests during testing.
@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.

@vercel

vercel Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
settler Error Error Jul 17, 2026 5:51am

@github-actions

Copy link
Copy Markdown

🔒 Release Safety Check Results

Safety Checks Passed

{"code":"NOT_FOUND","message":"Requested function was not found"}

@github-actions

Copy link
Copy Markdown

🔍 Classification Check Results

  • Total Files: 5294
  • OSS_PUBLIC: 52 ✅
  • PLATFORM_PROPRIETARY: 104
  • INTERNAL_BUSINESS: 1644
  • SECRET_RISK: 0 ✅
  • Violations: 0 ✅

No violations detected. Safe to merge!


📊 View full classification report

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9dfcbccf43

ℹ️ 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".

Comment on lines +38 to +41
afterEach(() => {
// Restore environment
process.env = originalEnv;
jest.restoreAllMocks();

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restore global.fetch after each test

In this test file, global.fetch is assigned a raw jest.fn() in beforeEach, so jest.restoreAllMocks() does not undo the assignment. The root AGENTS.md explicitly requires restoring the saved originalFetch in afterEach; when this file runs in a worker that later executes tests expecting the real fetch, those tests inherit the mock instead. Please set global.fetch = originalFetch during teardown.

Useful? React with 👍 / 👎.

@Hardonian

Copy link
Copy Markdown
Owner Author

Closed during CI cleanup: CI failed: FAILURE. No merge was performed.

@Hardonian Hardonian closed this Jul 20, 2026
auto-merge was automatically disabled July 20, 2026 02:23

Pull request was closed

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