jasmine-core 7.x

Use jasmine-core ^7.0.0 directly from Node: install its globals into a chosen object, inspect the core version, reset shared state, and define Jasmine specs, expectations, spies, and not-applicable specs. It is not the Jasmine CLI or test runner.

For

jasmine-core@7.0.2

Verified

2026-09-08, 5 examples executed

Package

@modootoday/pmcp-jasmine-core@7.0.0

What it covers

• What this package is
• Import and booting in 7.x
• State and version
• Defining specs and expectations
• Spies
• Pending versus not applicable
• 6.x shapes that are wrong in 7.x
• Configuration and integration migration notes
• Does not cover

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

import assert from "node:assert/strict";
import jasmineCore from "jasmine-core";

const target: Record<string, unknown> = {};
jasmineCore.installGlobals(target);

for (const name of ["describe", "it", "expect", "spyOn", "notApplicable"]) {
  assert.equal(typeof target[name], "function", `${name} should be installed`);
}
assert.equal(typeof (globalThis as any).describe, "undefined");

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-jasmine-core

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.