fusion-framework-testing

fusion-framework-testing is a skill for Claude Code, Codex from equinor/fusion-skills. It costs 169 tokens per session (1,869 once invoked), scanned A, original, MIT.

A testing guide for Fusion Framework React applications using Vitest, a JavaScript test runner, and Browser Mode, which runs tests in a real browser environment. It covers tests for hooks, components, routes, and complete apps.

In plain words
What is it for?
Use it to configure Vitest, render Fusion app components and hooks, share fixtures, test routes or full applications, and migrate tests away from Testing Library or jsdom.
Why use it?
It helps choose the right testing level and resolve setup problems such as hanging tests, unwanted network access, or incorrect app-file resolution.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/equinor/fusion-skills/fusion-framework-testing
Any agent
npx skills add equinor/fusion-skills --skill fusion-framework-testing
Clone the repo
git clone --depth 1 https://github.com/equinor/fusion-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for fusion-framework-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-framework-testing.svg)](https://agentmods.dev/skills/equinor/fusion-skills/fusion-framework-testing)
Your own site
<a href="https://agentmods.dev/skills/equinor/fusion-skills/fusion-framework-testing"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-framework-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 169 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,869 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00169 $0.01869
Opus 5 $0.00084 $0.00934
Sonnet 5 $0.00034 $0.00374
Haiku 4.5 $0.00017 $0.00187

Measured 5d ago against content hash 0e6d6a6bbf69, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

fusion-framework-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/.experimental/fusion-framework-testing/SKILL.md · 166 lines

How it starts

The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fusion Framework Testing

When to use

Use when writing or running a Vitest test for a Fusion Framework React app — a hook, component, route, or complete app — or when setting up/troubleshooting the test project itself.

Typical triggers:

  • "Write a test for this component / hook / route"
  • "Set up vitest.config.ts for this app"
  • "Why does this test hang / hit the network / fail to resolve the app?"
  • "Should this be a hook test or a component test?"
  • "Share seeded fixtures across a test file"
  • "Migrate this suite off Testing Library / jsdom"

Implicit triggers:

  • A test file imports @equinor/fusion-framework-vitest-plugin-react-app (or its /test, /config sub-paths)
  • vitest.config.ts needs Browser Mode, Playwright, or app-file resolution configured
  • A test renders a component/hook that reads useAppModule, useFramework, or similar

When not to use

  • Seeding module-specific state (a signed-in user, current context, feature flags, HTTP responses) — use fusion-framework-mocking; this skill only covers rendering/running the test
  • dev-server.config.ts API mocking/proxying for local ffc app dev — dev-time only, see fusion-developer-app
  • Non-Fusion test suites, or backend/service-repo tests

Required inputs

Mandatory

  • What is under test: pure function, hook, component, route, or complete app
  • Whether the project already has vitest.config.ts configured for this package

Conditional

  • Whether the test needs a specific signed-in user, seeded context, or faked HTTP response (then hand off to fusion-framework-mocking for the seeding details)
  • Whether several test files need the same fixture defaults

Instructions

Step 1 — Choose the smallest layer for the behavior under test

Fusion test utilities substitute external boundaries only; Vitest still owns the runner, assertions, lifecycle hooks, spies, timers, and coverage.

Testing intent Start with Import
Pure function or framework-independent hook Standard Vitest vitest
React hook that consumes app modules renderAppHook @equinor/fusion-framework-vitest-plugin-react-app
React component, route, or complete app test/render fixture @equinor/fusion-framework-vitest-plugin-react-app/test
Reusable app fixture without automatic app-file resolution testApp @equinor/fusion-framework-vitest-plugin-react-app
App module configuration without React mockAppModules see fusion-framework-mocking
Parent framework or portal-level modules mockFramework see fusion-framework-mocking
One method call, timer, global, or JS module Vitest's vi APIs vitest

Read the full file on GitHub · 166 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 166 lines · 169 tokens per session scan A 0e6d6a6bbf69

Subscribe to this mod's changes

fusion-framework-testing is a skill published in the GitHub repository equinor/fusion-skills (1 stars, last pushed 3d ago), licensed MIT. It adds 169 tokens to every session and 1,869 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens