Custom matcher configuration for Jasmine 7.0.1

Answer to the Core Questions

• jasmine.addMatchers API: The API signature and usage have not changed between v6.3.0 and v7.0.1. You can still call jasmine.addMatchers({ … }) inside a beforeAll or beforeEach block.
• Expect extension mechanism: No breaking changes were introduced that affect custom matchers. The expect function still resolves matcher names in the same way, and the matcher object must return an object with pass (boolean) and message (string).

Likely Explanation

Jasmine 7.0.1 is largely a maintenance release (the only change from 6.3.0 is a version bump). The core matcher registration and extension logic remain identical, so a matcher written for 6.x should register and execute unchanged. The only differences you might encounter are:

• Node.js 14 is still supported, but newer Node versions may expose deprecation warnings for older APIs used internally by Jasmine.
• If your matcher contains asynchronous logic (e.g., returns a Promise or uses async), it will not be supported because Jasmine’s matcher contract is synchronous.

Steps to Verify in Your Project

1. Create a matcher file (e.g., customMatchers.js).

   const customMatchers = {
     toBeOdd: function() {
       return {
         compare: function(actual) {
           const pass = typeof actual === 'number' && actual % 2 !== 0;
           return {
             pass,
             message: pass ? 'Expected not to be odd' : 'Expected to be odd'
           };
         }
       };
     }
   };
   
   beforeAll(() => {
     jasmine.addMatchers(customMatchers);
   });
   

2. Ensure the file loads before any spec:
   • List it in jasmine.json under setupFiles or spec_files, or
   • Import it in a global setup script that runs before the test runner starts.
3. Run the suite and confirm the matcher appears in jasmine.getEnv().matchers.
   • Write a spec that uses the matcher and intentionally fails to see the failure message.

Missing Diagnostic Detail

If your current matcher uses any asynchronous operations (returns a Promise, uses async, or relies on callbacks), Jasmine 7 will not execute it correctly. In that case you would need to refactor the matcher to be synchronous or use a different testing approach. Please confirm whether your matcher contains any async logic.