fix: Align Jasmine typing + support jasmine asymetrics matchers + other types fixes

[dprevost-LMI]

Fixes #1893
Fixes #1407 for real

Highlights:

• jasmine-expect-global.test-d provides proper Jasmine typing to use expect asynchronously with wdio/jasmine-framework
  • withContext is support for sync & async matchers
  • sync matchers are also async, following the hack of adding all sync matchers on expect forced to be expectAsync
  • Later to move into wdio/jasmine-framework
• jasmine.stringContaining now working with any text-based wdio matcher

TODOs

• Check and/or document if supporting Jasmine asymetrics matcher under expec-wdio import is needed

Waiting

• merge of: fix: Jasmine augmentation withContext and add Playgrounds for Jasmine, Jest & Mocha #2010
• merge of fix: Global wait not working with toBeDisplayed #2023

[christian-bromann]

@dprevost-LMI thanks for this effort, let me know the status of this and when I can review.

[dprevost-LMI]

@dprevost-LMI thanks for this effort, let me know the status of this and when I can review.

@christian-bromann I reviewed it thoroughly following the latest release and ensured it works with the latest wdio, so it's fully ready for you to review!

[greptile-apps]

Greptile Summary

This PR aligns the Jasmine framework typing with the actual runtime behavior of @wdio/jasmine-framework, adds support for Jasmine asymmetric matchers (e.g. jasmine.stringContaining) in WDIO matchers, and resolves a large number of previously suppressed @ts-expect-error comments across the Jasmine playground and type-test files.

• src/utils.ts: Removes the $$typeof Symbol check from isAsymmetricMatcher, adds isJasmineAsymmetricMatcher, isStringContainingMatcherLike, isStrictlyStringContainingMatcher, and getAsymmetricMatcherValue to unify Wdio and Jasmine matcher handling; compareText updated to use the new helpers, but compareTextWithArray still accesses .sample directly in its ignoreCase branch.
• jasmine-wdio-expect-async.d.ts: Introduces JasmineExpect, JasmineSyncMatchers, and withContext chaining so the global expect under @wdio/jasmine-framework is correctly typed as fully asynchronous.
• playgrounds/package-lock.json: The node_modules/jest-diff lock entry is corrupted — its resolved URL and integrity now point to jest-changed-files, which will break npm ci in the playground.

Confidence Score: 3/5

The runtime logic change in compareTextWithArray leaves Jasmine StringContaining matchers broken under ignoreCase, and the playground lock file is corrupted in a way that would install the wrong npm package.

Two independent defects are introduced: compareTextWithArray silently uses undefined as the matcher sample for any Jasmine StringContaining in the array when ignoreCase: true, and the playground package-lock.json maps jest-diff to the jest-changed-files tarball, causing a broken install. Both need to be fixed before merging.

src/utils.ts (the compareTextWithArray ignoreCase branch) and playgrounds/package-lock.json (the node_modules/jest-diff entry) need attention before this is merged.

Important Files Changed

Filename	Overview
src/utils.ts	Adds Jasmine asymmetric matcher support via new helper functions; compareText updated correctly, but compareTextWithArray still accesses .sample directly for the ignoreCase path, breaking Jasmine matchers in array comparisons.
jasmine-wdio-expect-async.d.ts	Adds JasmineExpect interface, JasmineSyncMatchers mapped type, and withContext support; correctly replaces old Expect augmentation with the new Jasmine-specific type structure.
jasmine.d.ts	Simplified to only augment AsyncMatchers with WDIO custom matchers; snapshot matcher overrides removed.
types/expect-webdriverio.d.ts	Adds JasmineAsymmetricMatcher<R> global type; separates Matchers from ExpectLibMatchers in MatchersAndInverse to prevent Jest-only matchers from bleeding into the Jasmine augmentation.
playgrounds/package-lock.json	Corrupted lock file: the node_modules/jest-diff entry now resolves to the jest-changed-files package URL/integrity, breaking npm ci in the playground.
types-checks-filter-out-node_modules.js	Suppresses TS2304 for unresolved Expected<T> type; silences a genuine consumer-visible gap rather than fixing the underlying type reference.
test/utils.test.ts	Adds comprehensive unit tests for new asymmetric-matcher utility functions using a mock Jasmine StringContaining class.
test-types/jasmine-global-expect-async/jasmine-expect-global.test-d.ts	Uncomments all previously-skipped type tests for the Jasmine global expect; adds coverage for withContext, promise matchers, and asymmetric matchers.
playgrounds/mocha/wdio.conf.ts	Adds four commented-out spec globs that appear to be leftover development artifacts.
playgrounds/jasmine/test/specs/expect-wdioImport/network-matchers.test.ts	New playground test for network matchers with Jasmine and expect asymmetric matchers; last it block has cosmetic 8-space indent instead of 4.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[asymmetric matcher passed to compareText / compareTextWithArray] --> B{isAsymmetricMatcher?}
    B -- No --> C[string / RegExp path]
    B -- Yes --> D{isStringContainingMatcherLike?}
    D -- Yes, ignoreCase --> E{isWdioAsymmetricMatcher?}
    E -- Yes: Wdio --> F[getAsymmetricMatcherValue → .sample]
    E -- No: Jasmine --> G[getAsymmetricMatcherValue → .expected]
    F --> H[isStrictlyStringContainingMatcher?]
    G --> H
    H -- Yes --> I[expect.stringContaining lower]
    H -- No --> J[expect.not.stringContaining lower]
    D -- No --> K[asymmetricMatch directly]
    I --> K
    J --> K
    subgraph BUG in compareTextWithArray
        L[item in expectedArray] --> M{isStringContainingMatcherLike?}
        M -- Yes --> N[item.sample?.toString - undefined for Jasmine!]
    end

Loading

Comments Outside Diff (5)

1. src/utils.ts, line 276-282 (link)

   compareTextWithArray still uses .sample instead of getAsymmetricMatcherValue

   compareText was updated to call getAsymmetricMatcherValue to support both Wdio (sample) and Jasmine (expected) matchers under ignoreCase. However, the parallel ignoreCase branch in compareTextWithArray was NOT updated and still accesses item.sample?.toString() directly. For any Jasmine StringContaining matcher passed in an array (which uses .expected, not .sample), item.sample is undefined, so expect.stringContaining(undefined) is called, producing silent incorrect results instead of a case-folded match.

2. src/utils.ts, line 276-280 (link)

   Use getAsymmetricMatcherValue here, consistent with compareText, to correctly extract the sample value from both Wdio (.sample) and Jasmine (.expected) matchers. The current item.sample?.toString() call returns undefined for Jasmine matchers, causing expect.stringContaining(undefined) to be created silently.

3. playgrounds/package-lock.json, line 7988-8003 (link)

   node_modules/jest-diff entry resolves to the wrong package

   The node_modules/jest-diff entry's resolved URL and integrity now point to jest-changed-files instead of jest-diff, and its dependencies are jest-changed-files's (execa, jest-util, p-limit) rather than jest-diff's (@jest/diff-sequences, chalk, pretty-format). Running npm ci in the playgrounds directory will install jest-changed-files under the node_modules/jest-diff path, breaking jest-matcher-utils and any other package that imports from jest-diff. The lock file should be regenerated from a clean state.

4. playgrounds/mocha/wdio.conf.ts, line 48-52 (link)

   Leftover development artifacts in specs array

   Four commented-out spec globs (basic-matchers.test.ts, soft-expect.test.ts, snapshot.test.ts, wdio-matchers.test.ts) were added alongside the existing wildcard. These look like temporary dev-time overrides used to run individual suites during development and should be removed before merging.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

5. playgrounds/jasmine/test/specs/expect-wdioImport/network-matchers.test.ts, line 513-521 (link)

   Misaligned indentation on the last it block

   The final it('should support wdio expect asymmetric matchers') is indented with 8 spaces instead of 4, unlike every other it in the file. JavaScript ignores indentation so the test still runs correctly, but the inconsistency makes the code harder to read.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

_{Reviews (1): Last reviewed commit: "Fix typing with `toBeResolvedTo` & `toBe..." | Re-trigger Greptile}

[greptile-apps]

Silencing Expected<T> type error hides a genuine resolution gap

Expected<T> is a @types/jasmine utility type used in jasmine-wdio-expect-async.d.ts to type toBeResolvedTo. Because @types/jasmine is excluded from tsconfig.types.json, the type is unresolved and the error is suppressed here. Consumers who add expect-webdriverio/jasmine-wdio-expect-async to their types without @types/jasmine will see the same TS2304 in their own project. Substituting the concrete type directly would keep the type check clean without a filter entry.