Skip to content

fix: DDP method calls returning 404 for void methods#40057

Merged
dionisio-bot[bot] merged 3 commits intodevelopfrom
fix/ddp-method-call
Apr 9, 2026
Merged

fix: DDP method calls returning 404 for void methods#40057
dionisio-bot[bot] merged 3 commits intodevelopfrom
fix/ddp-method-call

Conversation

@abhinavkrin
Copy link
Copy Markdown
Member

@abhinavkrin abhinavkrin commented Apr 7, 2026

Proposed changes (including videos or screenshots)

This PR fixes an issue in the DDP method call handling within the ddp-streamer where valid method calls could incorrectly return a 404 method not found response.

Root cause

The issue was caused by incorrect method resolution in the DDP execution flow within the ddp-streamer. Since the ddp-streamer module is only active in Enterprise environments with microservice deployment, the issue was isolated to this setup.

In Server.ts of ddp-streamer, the call() method used a truthiness check on the return value of MeteorService.callMethodWithToken :

// BUG: treats void/undefined/null/0/false/"" as "method not found"
if (result?.result) {
    return this.result(client, packet, result.result);
}
throw new MeteorError(404, `Method '${packet.method}' not found`);

A method returns void → result.result is undefined → falsy → false 404 thrown. The method could have been executed successfully, but the client received an error.

This mismatch between execution and resolution led to false-negative error responses being propagated to clients.

Fix

Always return result?.result to the client. If the method truly doesn't exist, Meteor.callAsync inside callMethodWithToken throws its own error, caught by the outer catch block.

Issue(s)

Steps to test or reproduce

Further comments

CORE-1867

Summary by CodeRabbit

  • Bug Fixes

    • Prevented incorrect 404 responses for certain DDP method calls so successful executions no longer surface as not-found errors.
  • Tests

    • Added unit tests covering method delegation, local method handling, error propagation, and closed-client behavior.
  • Chores

    • Introduced test configuration, enabled Jest-based test scripts, updated TypeScript test types, and added a changeset for a patch release.

Signed-off-by: Abhinav Kumar <abhinav@avitechlab.com>
Signed-off-by: Abhinav Kumar <abhinav@avitechlab.com>
@dionisio-bot
Copy link
Copy Markdown
Contributor

dionisio-bot Bot commented Apr 7, 2026

Looks like this PR is ready to merge! 🎉
If you have any trouble, please check the PR guidelines

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Apr 7, 2026

🦋 Changeset detected

Latest commit: 2537811

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@rocket.chat/ddp-streamer Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 7, 2026

Walkthrough

Removes a conditional that threw a 404 for falsy Meteor fallback results in the DDP Streamer and forwards Meteor call results (including undefined) unconditionally. Adds Jest config, tests, and test-related TypeScript and package.json updates for the ddp-streamer package, plus a changeset declaring a patch release.

Changes

Cohort / File(s) Summary
Changeset
\.changeset/empty-spiders-vanish.md
Adds a changeset declaring a patch release for @rocket.chat/ddp-streamer documenting a 404-fix.
Server runtime change
ee/apps/ddp-streamer/src/Server.ts
Alters Meteor fallback in Server.call to stop checking result?.result and to stop throwing MeteorError(404, ...); now forwards result.result regardless of truthiness.
Tests & test configuration
ee/apps/ddp-streamer/src/Server.spec.ts, ee/apps/ddp-streamer/jest.config.ts, ee/apps/ddp-streamer/tsconfig.json, ee/apps/ddp-streamer/package.json
Adds Server.call unit tests; introduces Jest config and enables Jest/Node types in tsconfig; replaces placeholder test script and adds Jest dev dependencies and scripts in package.json.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested labels

type: bug

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title clearly summarizes the main fix: addressing incorrect 404 errors for DDP method calls returning void/falsy values, which aligns with the changeset and the core problem being solved.
Linked Issues check ✅ Passed The PR successfully addresses the requirements from CORE-1867 by fixing the backend regression where DDP method calls incorrectly returned 404 errors for methods returning void or falsy values, with comprehensive test coverage added.
Out of Scope Changes check ✅ Passed All changes are directly scoped to fixing the DDP method call issue: the core fix in Server.ts, comprehensive test coverage, Jest configuration setup for testing, and TypeScript configuration updates—nothing is extraneous to the stated objectives.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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

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

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 7, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.51%. Comparing base (44938fd) to head (2537811).
⚠️ Report is 37 commits behind head on develop.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop   #40057      +/-   ##
===========================================
- Coverage    70.55%   70.51%   -0.05%     
===========================================
  Files         3271     3274       +3     
  Lines       116782   116936     +154     
  Branches     21090    21122      +32     
===========================================
+ Hits         82393    82452      +59     
- Misses       32338    32432      +94     
- Partials      2051     2052       +1     
Flag Coverage Δ
e2e 60.46% <ø> (-0.06%) ⬇️
e2e-api 49.02% <ø> (+0.89%) ⬆️
unit 70.92% <100.00%> (-0.06%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

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

No issues found across 2 files

Signed-off-by: Abhinav Kumar <abhinav@avitechlab.com>
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
ee/apps/ddp-streamer/src/Server.spec.ts (1)

54-94: Add explicit regression cases for false, 0, and '' return values.

The suite currently protects the undefined branch, but the reported regression scope includes all falsy results. Covering all four values keeps this fix protected against future truthiness regressions.

Proposed test hardening
-		it('does not return an error when the method returns void', async () => {
-			mockCallMethodWithToken.mockResolvedValue({ result: undefined } as any);
-			const client = makeClient();
-			const resultSpy = jest.spyOn(server, 'result');
-
-			await server.call(client, makePacket('setAvatarFromService'));
-
-			expect(resultSpy).toHaveBeenCalledWith(client, expect.objectContaining({ id: 'test-id' }), undefined);
-		});
+		it.each([undefined, false, 0, ''])(
+			'does not return an error when MeteorService returns %p',
+			async (value) => {
+				mockCallMethodWithToken.mockResolvedValue({ result: value } as any);
+				const client = makeClient();
+				const resultSpy = jest.spyOn(server, 'result');
+
+				await server.call(client, makePacket('setAvatarFromService'));
+
+				expect(resultSpy).toHaveBeenCalledWith(client, expect.objectContaining({ id: 'test-id' }), value);
+			},
+		);
@@
-		it('does not return an error when the local method returns void', async () => {
-			server.methods({ voidMethod: async () => undefined });
-			const client = makeClient();
-			const resultSpy = jest.spyOn(server, 'result');
-
-			await server.call(client, makePacket('voidMethod'));
-
-			expect(resultSpy).toHaveBeenCalledWith(client, expect.objectContaining({ id: 'test-id' }), undefined);
-		});
+		it.each([undefined, false, 0, ''])(
+			'does not return an error when a local method returns %p',
+			async (value) => {
+				server.methods({ voidMethod: async () => value });
+				const client = makeClient();
+				const resultSpy = jest.spyOn(server, 'result');
+
+				await server.call(client, makePacket('voidMethod'));
+
+				expect(resultSpy).toHaveBeenCalledWith(client, expect.objectContaining({ id: 'test-id' }), value);
+			},
+		);
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@ee/apps/ddp-streamer/src/Server.spec.ts` around lines 54 - 94, Add explicit
test cases to assert that falsy but defined return values (false, 0, and '') are
forwarded to server.result rather than treated like errors or undefined; for
both remote/Meteor-method path (where mockCallMethodWithToken resolves) and
local registered methods (server.methods), add tests that call server.call with
packets made by makePacket for method names returning false, 0, and '' and
assert resultSpy (jest.spyOn(server, 'result')) is called with the client, the
expected packet id (expect.objectContaining({ id: 'test-id' })), and the exact
falsy value (expect.anything matching false / 0 / ''), mirroring the existing
void/defined tests so regressions around truthiness are covered.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@ee/apps/ddp-streamer/src/Server.spec.ts`:
- Around line 54-94: Add explicit test cases to assert that falsy but defined
return values (false, 0, and '') are forwarded to server.result rather than
treated like errors or undefined; for both remote/Meteor-method path (where
mockCallMethodWithToken resolves) and local registered methods (server.methods),
add tests that call server.call with packets made by makePacket for method names
returning false, 0, and '' and assert resultSpy (jest.spyOn(server, 'result'))
is called with the client, the expected packet id (expect.objectContaining({ id:
'test-id' })), and the exact falsy value (expect.anything matching false / 0 /
''), mirroring the existing void/defined tests so regressions around truthiness
are covered.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fbd1cc64-b19b-4dc3-9374-cce3013679fc

📥 Commits

Reviewing files that changed from the base of the PR and between 9dbc2b0 and 2537811.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (4)
  • ee/apps/ddp-streamer/jest.config.ts
  • ee/apps/ddp-streamer/package.json
  • ee/apps/ddp-streamer/src/Server.spec.ts
  • ee/apps/ddp-streamer/tsconfig.json
✅ Files skipped from review due to trivial changes (1)
  • ee/apps/ddp-streamer/tsconfig.json
📜 Review details
⏰ 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). (4)
  • GitHub Check: 📦 Build Packages
  • GitHub Check: cubic · AI code reviewer
  • GitHub Check: CodeQL-Build
  • GitHub Check: CodeQL-Build
🧰 Additional context used
📓 Path-based instructions (2)
**/*.{ts,tsx,js}

📄 CodeRabbit inference engine (.cursor/rules/playwright.mdc)

**/*.{ts,tsx,js}: Write concise, technical TypeScript/JavaScript with accurate typing in Playwright tests
Avoid code comments in the implementation

Files:

  • ee/apps/ddp-streamer/jest.config.ts
  • ee/apps/ddp-streamer/src/Server.spec.ts
**/*.spec.ts

📄 CodeRabbit inference engine (.cursor/rules/playwright.mdc)

**/*.spec.ts: Use descriptive test names that clearly communicate expected behavior in Playwright tests
Use .spec.ts extension for test files (e.g., login.spec.ts)

Files:

  • ee/apps/ddp-streamer/src/Server.spec.ts
🧠 Learnings (24)
📓 Common learnings
Learnt from: smirk-dev
Repo: RocketChat/Rocket.Chat PR: 39625
File: apps/meteor/app/api/server/v1/push.ts:85-97
Timestamp: 2026-03-14T14:58:58.834Z
Learning: In RocketChat/Rocket.Chat, the `push.token` POST/DELETE endpoints in `apps/meteor/app/api/server/v1/push.ts` were already migrated to the chained router API pattern on `develop` prior to PR `#39625`. `cleanTokenResult` (which strips `authToken` and returns `PushTokenResult`) and `isPushTokenPOSTProps`/`isPushTokenDELETEProps` validators already exist on `develop`. PR `#39625` only migrates `push.get` and `push.info` to the chained pattern. Do not flag `cleanTokenResult` or `PushTokenResult` as newly introduced behavior-breaking changes when reviewing this PR.
Learnt from: ggazzo
Repo: RocketChat/Rocket.Chat PR: 39553
File: apps/meteor/app/integrations/server/methods/incoming/updateIncomingIntegration.ts:179-181
Timestamp: 2026-03-20T13:51:23.302Z
Learning: In `apps/meteor/app/integrations/server/methods/incoming/updateIncomingIntegration.ts`, the truthiness guards `...(integration.avatar && { avatar })`, `...(integration.emoji && { emoji })`, `...(integration.alias && { alias })`, and `...(integration.script && { script })` in the `$set` payload of `updateIncomingIntegration` are intentional. Empty-string values for these fields should NOT overwrite the stored value — only truthy values are persisted. Do not flag these as bugs preventing explicit clears.
Learnt from: ahmed-n-abdeltwab
Repo: RocketChat/Rocket.Chat PR: 38913
File: packages/ddp-client/src/legacy/types/SDKLegacy.ts:34-34
Timestamp: 2026-02-25T20:10:16.987Z
Learning: In the RocketChat/Rocket.Chat monorepo, packages/ddp-client and apps/meteor do not use TypeScript project references. Module augmentations in apps/meteor (e.g., declare module 'rocket.chat/rest-typings') are not visible when compiling packages/ddp-client in isolation, which is why legacy SDK methods that depend on OperationResult types for OpenAPI-migrated endpoints must remain commented out.
Learnt from: ahmed-n-abdeltwab
Repo: RocketChat/Rocket.Chat PR: 38974
File: apps/meteor/app/api/server/v1/im.ts:220-221
Timestamp: 2026-02-24T19:09:09.561Z
Learning: In RocketChat/Rocket.Chat OpenAPI migration PRs for apps/meteor/app/api/server/v1 endpoints, maintainers prefer to avoid any logic changes; style-only cleanups (like removing inline comments) may be deferred to follow-ups to keep scope tight.
Learnt from: ggazzo
Repo: RocketChat/Rocket.Chat PR: 35995
File: apps/meteor/app/api/server/v1/rooms.ts:1107-1112
Timestamp: 2026-02-23T17:53:18.785Z
Learning: In Rocket.Chat PR reviews, maintain strict scope boundaries—when a PR is focused on a specific endpoint (e.g., rooms.favorite), avoid reviewing or suggesting changes to other endpoints that were incidentally refactored (e.g., rooms.invite) unless explicitly requested by maintainers.
Learnt from: tassoevan
Repo: RocketChat/Rocket.Chat PR: 39397
File: packages/gazzodown/src/elements/Timestamp/DateTimeFormats.spec.tsx:20-23
Timestamp: 2026-03-06T18:09:17.867Z
Learning: In the RocketChat/Rocket.Chat gazzodown package (`packages/gazzodown`), tests are intended to run under the UTC timezone, but as of PR `#39397` this is NOT yet explicitly enforced in `jest.config.ts` or the `package.json` test scripts (which just run `jest` without `TZ=UTC`). To make timezone-sensitive snapshot tests reliable across all environments, `TZ=UTC` should be added to the test scripts in `package.json` or to `jest.config.ts` via `testEnvironmentOptions.timezone`. Without explicit UTC enforcement, snapshot tests involving date-fns formatted output or `toLocaleString()` will fail for contributors in non-UTC timezones.
Learnt from: CR
Repo: RocketChat/Rocket.Chat PR: 0
File: .cursor/rules/playwright.mdc:0-0
Timestamp: 2025-11-24T17:08:17.065Z
Learning: Applies to apps/meteor/tests/e2e/**/*.spec.ts : Ensure tests run reliably in parallel without shared state conflicts
📚 Learning: 2025-12-10T21:00:54.909Z
Learnt from: KevLehman
Repo: RocketChat/Rocket.Chat PR: 37091
File: ee/packages/abac/jest.config.ts:4-7
Timestamp: 2025-12-10T21:00:54.909Z
Learning: Rocket.Chat monorepo: Jest testMatch pattern '<rootDir>/src/**/*.spec.(ts|js|mjs)' is valid in this repo and used across multiple packages (e.g., packages/tools, ee/packages/omnichannel-services). Do not flag it as invalid in future reviews.

Applied to files:

  • ee/apps/ddp-streamer/package.json
  • ee/apps/ddp-streamer/jest.config.ts
📚 Learning: 2026-03-06T18:09:17.867Z
Learnt from: tassoevan
Repo: RocketChat/Rocket.Chat PR: 39397
File: packages/gazzodown/src/elements/Timestamp/DateTimeFormats.spec.tsx:20-23
Timestamp: 2026-03-06T18:09:17.867Z
Learning: In the RocketChat/Rocket.Chat gazzodown package (`packages/gazzodown`), tests are intended to run under the UTC timezone, but as of PR `#39397` this is NOT yet explicitly enforced in `jest.config.ts` or the `package.json` test scripts (which just run `jest` without `TZ=UTC`). To make timezone-sensitive snapshot tests reliable across all environments, `TZ=UTC` should be added to the test scripts in `package.json` or to `jest.config.ts` via `testEnvironmentOptions.timezone`. Without explicit UTC enforcement, snapshot tests involving date-fns formatted output or `toLocaleString()` will fail for contributors in non-UTC timezones.

Applied to files:

  • ee/apps/ddp-streamer/package.json
  • ee/apps/ddp-streamer/jest.config.ts
📚 Learning: 2026-02-25T20:10:16.987Z
Learnt from: ahmed-n-abdeltwab
Repo: RocketChat/Rocket.Chat PR: 38913
File: packages/ddp-client/src/legacy/types/SDKLegacy.ts:34-34
Timestamp: 2026-02-25T20:10:16.987Z
Learning: In the RocketChat/Rocket.Chat monorepo, packages/ddp-client and apps/meteor do not use TypeScript project references. Module augmentations in apps/meteor (e.g., declare module 'rocket.chat/rest-typings') are not visible when compiling packages/ddp-client in isolation, which is why legacy SDK methods that depend on OperationResult types for OpenAPI-migrated endpoints must remain commented out.

Applied to files:

  • ee/apps/ddp-streamer/package.json
  • ee/apps/ddp-streamer/jest.config.ts
  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2026-03-17T16:08:37.572Z
Learnt from: cardoso
Repo: RocketChat/Rocket.Chat PR: 39690
File: packages/ui-voip/package.json:11-11
Timestamp: 2026-03-17T16:08:37.572Z
Learning: In `packages/ui-voip/package.json` (RocketChat/Rocket.Chat), the team deliberately chose to use `rm -rf dist` directly in the `"build"` script instead of `rimraf`, as they decided against introducing the `rimraf` dependency for this package. Do not flag `rm -rf dist` in the ui-voip build script as a cross-platform issue requiring rimraf.

Applied to files:

  • ee/apps/ddp-streamer/package.json
📚 Learning: 2026-02-24T19:05:56.710Z
Learnt from: ahmed-n-abdeltwab
Repo: RocketChat/Rocket.Chat PR: 0
File: :0-0
Timestamp: 2026-02-24T19:05:56.710Z
Learning: Rocket.Chat repo context: When a workspace manifest on develop already pins a dependency version (e.g., packages/web-ui-registration → "rocket.chat/ui-contexts": "27.0.1"), a lockfile change in a feature PR that upgrades only that dependency’s resolution is considered a manifest-driven sync and can be kept, preferably as a small "chore: sync yarn.lock with manifests" commit.

Applied to files:

  • ee/apps/ddp-streamer/package.json
📚 Learning: 2025-11-24T17:08:17.065Z
Learnt from: CR
Repo: RocketChat/Rocket.Chat PR: 0
File: .cursor/rules/playwright.mdc:0-0
Timestamp: 2025-11-24T17:08:17.065Z
Learning: Applies to apps/meteor/tests/e2e/**/*.spec.ts : Utilize Playwright fixtures (`test`, `page`, `expect`) for consistency in test files

Applied to files:

  • ee/apps/ddp-streamer/package.json
  • ee/apps/ddp-streamer/jest.config.ts
  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2025-11-24T17:08:17.065Z
Learnt from: CR
Repo: RocketChat/Rocket.Chat PR: 0
File: .cursor/rules/playwright.mdc:0-0
Timestamp: 2025-11-24T17:08:17.065Z
Learning: Applies to apps/meteor/tests/e2e/**/*.spec.ts : All test files must be created in `apps/meteor/tests/e2e/` directory

Applied to files:

  • ee/apps/ddp-streamer/package.json
  • ee/apps/ddp-streamer/jest.config.ts
  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2025-11-24T17:08:17.065Z
Learnt from: CR
Repo: RocketChat/Rocket.Chat PR: 0
File: .cursor/rules/playwright.mdc:0-0
Timestamp: 2025-11-24T17:08:17.065Z
Learning: Applies to **/*.{ts,tsx,js} : Write concise, technical TypeScript/JavaScript with accurate typing in Playwright tests

Applied to files:

  • ee/apps/ddp-streamer/package.json
  • ee/apps/ddp-streamer/jest.config.ts
📚 Learning: 2025-11-24T17:08:17.065Z
Learnt from: CR
Repo: RocketChat/Rocket.Chat PR: 0
File: .cursor/rules/playwright.mdc:0-0
Timestamp: 2025-11-24T17:08:17.065Z
Learning: Applies to apps/meteor/tests/e2e/**/*.spec.ts : Ensure tests run reliably in parallel without shared state conflicts

Applied to files:

  • ee/apps/ddp-streamer/package.json
  • ee/apps/ddp-streamer/jest.config.ts
  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2025-11-24T17:08:17.065Z
Learnt from: CR
Repo: RocketChat/Rocket.Chat PR: 0
File: .cursor/rules/playwright.mdc:0-0
Timestamp: 2025-11-24T17:08:17.065Z
Learning: Applies to apps/meteor/tests/e2e/**/*.spec.ts : Use `test.step()` for complex test scenarios to improve organization in Playwright tests

Applied to files:

  • ee/apps/ddp-streamer/package.json
  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2026-02-24T19:05:56.710Z
Learnt from: ahmed-n-abdeltwab
Repo: RocketChat/Rocket.Chat PR: 0
File: :0-0
Timestamp: 2026-02-24T19:05:56.710Z
Learning: In Rocket.Chat PRs, keep feature PRs free of unrelated lockfile-only dependency bumps; prefer reverting lockfile drift or isolating such bumps into a separate "chore" commit/PR, and always use yarn install --immutable with the Yarn version pinned in package.json via Corepack.

Applied to files:

  • ee/apps/ddp-streamer/package.json
📚 Learning: 2025-11-24T17:08:17.065Z
Learnt from: CR
Repo: RocketChat/Rocket.Chat PR: 0
File: .cursor/rules/playwright.mdc:0-0
Timestamp: 2025-11-24T17:08:17.065Z
Learning: Applies to apps/meteor/tests/e2e/**/*.spec.ts : Group related tests in the same file

Applied to files:

  • ee/apps/ddp-streamer/jest.config.ts
  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2025-12-16T17:29:45.163Z
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 37834
File: apps/meteor/tests/e2e/page-objects/fragments/admin-flextab-emoji.ts:12-22
Timestamp: 2025-12-16T17:29:45.163Z
Learning: In page object files under `apps/meteor/tests/e2e/page-objects/`, always import `expect` from `../../utils/test` (Playwright's async expect), not from Jest. Jest's `expect` has a synchronous signature and will cause TypeScript errors when used with web-first assertions like `toBeVisible()`.

Applied to files:

  • ee/apps/ddp-streamer/jest.config.ts
📚 Learning: 2025-11-24T17:08:17.065Z
Learnt from: CR
Repo: RocketChat/Rocket.Chat PR: 0
File: .cursor/rules/playwright.mdc:0-0
Timestamp: 2025-11-24T17:08:17.065Z
Learning: Applies to apps/meteor/tests/e2e/**/*.spec.ts : Use `expect` matchers for assertions (`toEqual`, `toContain`, `toBeTruthy`, `toHaveLength`, etc.) instead of `assert` statements in Playwright tests

Applied to files:

  • ee/apps/ddp-streamer/jest.config.ts
  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2025-11-24T17:08:17.065Z
Learnt from: CR
Repo: RocketChat/Rocket.Chat PR: 0
File: .cursor/rules/playwright.mdc:0-0
Timestamp: 2025-11-24T17:08:17.065Z
Learning: Applies to apps/meteor/tests/e2e/page-objects/**/*.ts : Utilize existing page objects pattern from `apps/meteor/tests/e2e/page-objects/`

Applied to files:

  • ee/apps/ddp-streamer/jest.config.ts
📚 Learning: 2025-11-24T17:08:17.065Z
Learnt from: CR
Repo: RocketChat/Rocket.Chat PR: 0
File: .cursor/rules/playwright.mdc:0-0
Timestamp: 2025-11-24T17:08:17.065Z
Learning: Applies to **/*.spec.ts : Use `.spec.ts` extension for test files (e.g., `login.spec.ts`)

Applied to files:

  • ee/apps/ddp-streamer/jest.config.ts
📚 Learning: 2026-02-26T19:25:44.063Z
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 38778
File: packages/ui-voip/src/providers/useMediaSession.ts:192-192
Timestamp: 2026-02-26T19:25:44.063Z
Learning: In the Rocket.Chat repository, do not reference Biome lint rules in code review feedback. Biome is not used even if biome.json exists; only reference Biome rules if there is explicit, project-wide usage documented. For TypeScript files, review lint implications without Biome guidance unless the project enables Biome rules.

Applied to files:

  • ee/apps/ddp-streamer/jest.config.ts
  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2026-02-26T19:25:44.063Z
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 38778
File: packages/ui-voip/src/providers/useMediaSession.ts:192-192
Timestamp: 2026-02-26T19:25:44.063Z
Learning: In this repository (RocketChat/Rocket.Chat), Biome lint rules are not used even if a biome.json exists. When reviewing TypeScript files (e.g., packages/ui-voip/src/providers/useMediaSession.ts), ensure lint suggestions do not reference Biome-specific rules. Rely on general ESLint/TypeScript lint rules and project conventions instead.

Applied to files:

  • ee/apps/ddp-streamer/jest.config.ts
  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2025-12-10T21:00:43.645Z
Learnt from: KevLehman
Repo: RocketChat/Rocket.Chat PR: 37091
File: ee/packages/abac/jest.config.ts:4-7
Timestamp: 2025-12-10T21:00:43.645Z
Learning: Adopt the monorepo-wide Jest testMatch pattern: <rootDir>/src/**/*.spec.{ts,js,mjs} (represented here as '**/src/**/*.spec.{ts,js,mjs}') to ensure spec files under any package's src directory are picked up consistently across all packages in the Rocket.Chat monorepo. Apply this pattern in jest.config.ts for all relevant packages to maintain uniform test discovery.

Applied to files:

  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2025-11-24T17:08:17.065Z
Learnt from: CR
Repo: RocketChat/Rocket.Chat PR: 0
File: .cursor/rules/playwright.mdc:0-0
Timestamp: 2025-11-24T17:08:17.065Z
Learning: Applies to apps/meteor/tests/e2e/**/*.spec.ts : Maintain test isolation between test cases in Playwright tests

Applied to files:

  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2025-10-06T20:30:45.540Z
Learnt from: d-gubert
Repo: RocketChat/Rocket.Chat PR: 37152
File: packages/apps-engine/tests/test-data/storage/storage.ts:101-122
Timestamp: 2025-10-06T20:30:45.540Z
Learning: In `packages/apps-engine/tests/test-data/storage/storage.ts`, the stub methods (updatePartialAndReturnDocument, updateStatus, updateSetting, updateAppInfo, updateMarketplaceInfo) intentionally throw "Method not implemented." Tests using these methods must stub them using `SpyOn` from the test library rather than relying on actual implementations.

Applied to files:

  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2026-02-24T19:22:48.358Z
Learnt from: juliajforesti
Repo: RocketChat/Rocket.Chat PR: 38493
File: apps/meteor/tests/e2e/omnichannel/omnichannel-send-pdf-transcript.spec.ts:66-67
Timestamp: 2026-02-24T19:22:48.358Z
Learning: In Playwright end-to-end tests (e.g., under apps/meteor/tests/e2e/...), prefer locating elements by translated text (getByText) and ARIA roles (getByRole) over data-qa attributes. If translation values change, update the corresponding test locators accordingly. Never use data-qa locators. This guideline applies to all Playwright e2e test specs in the repository and helps keep tests robust to UI text changes and accessible semantics.

Applied to files:

  • ee/apps/ddp-streamer/src/Server.spec.ts
📚 Learning: 2026-03-06T18:10:15.268Z
Learnt from: tassoevan
Repo: RocketChat/Rocket.Chat PR: 39397
File: packages/gazzodown/src/code/CodeBlock.spec.tsx:47-68
Timestamp: 2026-03-06T18:10:15.268Z
Learning: In tests (especially those using testing-library/dom/jsdom) for Rocket.Chat components, the HTML <code> element has an implicit ARIA role of 'code'. Therefore, screen.getByRole('code') or screen.findByRole('code') will locate <code> elements even without a role attribute. Do not flag findByRole('code') as invalid in reviews; prefer using the implicit role instead of adding role="code" unless necessary for accessibility.

Applied to files:

  • ee/apps/ddp-streamer/src/Server.spec.ts
🔇 Additional comments (3)
ee/apps/ddp-streamer/package.json (1)

18-20: Jest wiring in scripts and devDependencies looks consistent.

This update cleanly enables package-level unit testing and matches the new jest.config.ts + spec additions.

Also applies to: 54-64

ee/apps/ddp-streamer/jest.config.ts (1)

4-7: Jest config is correctly scoped and aligned with monorepo conventions.

preset + testMatch are set appropriately for package-local specs under src/.

Based on learnings: "Rocket.Chat monorepo: Jest testMatch pattern '/src/**/*.spec.(ts|js|mjs)' is valid in this repo and used across multiple packages."

ee/apps/ddp-streamer/src/Server.spec.ts (1)

97-106: Closed-socket guard test is solid.

Good coverage for the no-op path when WebSocket is not open; it prevents accidental side effects.

@alfredodelfabro alfredodelfabro added this to the 8.4.0 milestone Apr 7, 2026
@abhinavkrin abhinavkrin added stat: QA assured Means it has been tested and approved by a company insider labels Apr 9, 2026
@dionisio-bot dionisio-bot Bot added the stat: ready to merge PR tested and approved waiting for merge label Apr 9, 2026
@dionisio-bot dionisio-bot Bot added this pull request to the merge queue Apr 9, 2026
Merged via the queue into develop with commit eb78ae4 Apr 9, 2026
80 of 82 checks passed
@dionisio-bot dionisio-bot Bot deleted the fix/ddp-method-call branch April 9, 2026 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stat: QA assured Means it has been tested and approved by a company insider stat: ready to merge PR tested and approved waiting for merge type: bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants