test(client): distinguish variant test cases

[jason-ha]

Several test suites run with varying environments, but report tests the same way (most meaningfully by name) that are tracked as the same by infrastructure.

Update default setup to prefix test case names by variance when it is present.

Reconfigure CommonJS testing as a variant and replace MOCHA_SPEC using new FLUID_TEST_MODULE_SYSTEM environment variable. CommonJS test cases and report file are prefixed by [CJS]. ESM tests remain unprefixed.

• This "adds" 773 test cases.
• The 130 test cases from @fluidframework/routerlicious-driver are effectively renamed as it only tests CommonJS.

Correct @fluid-internal/devtools-browser-extension mocha configuration also use @fluid-internal/mocha-test-setup specified modules instead of ignoring them with complete require property override. Will now report package tests in telemetry and suppress console output by default (in addition to respecting the test case variant renaming).

@fluidframework/core-interfaces which is unable to leverage @fluid-internal/mocha-test-setup has a cloned subset of logic and now generates reports. (Its test spec was restored to *.spec.*js which allowed src/test/types/fluidObjectTypes.ts to be restored from #25292 changes.)

• This adds 770 test cases to tracking.

Note: packages @fluidframework/driver-definitions and @fluid-internal/test-driver-definitions are also used by @fluid-internal/mocha-test-setup. They were not updated like @fluidframework/core-interfaces as they have no runtime tests.

[Copilot]

Pull Request Overview

This PR standardizes test case identification by introducing a new environment variable FLUID_TEST_MODULE_SYSTEM to replace MOCHA_SPEC for CommonJS testing and implementing test case prefixing to distinguish test variants in reporting infrastructure.

Key changes:

• Replace MOCHA_SPEC=dist/test with FLUID_TEST_MODULE_SYSTEM=CJS across all package.json files
• Add automatic [CJS] prefixing to CommonJS test case names
• Configure @fluidframework/core-interfaces to generate test reports with variant tracking

Reviewed Changes

Copilot reviewed 70 out of 70 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
packages/test/mocha-test-setup/src/mochaHooks.ts	Add logic to prefix test titles with variant when FLUID_TEST_MODULE_SYSTEM is set
packages/test/mocha-test-setup/mocharc-common.cjs	Implement CJS detection and automatic spec/prefix configuration
packages/test/mocha-test-setup/README.md	Document new FLUID_TEST_MODULE_SYSTEM environment variable
packages/common/core-interfaces/.mocharc.cjs	Add mocha configuration for test reporting with variant support
packages/common/core-interfaces/src/test/mochaHooks.ts	Add minimal hook for CJS test prefixing
packages/common/core-interfaces/test-config.json	Add test reporter configuration
packages/common/core-interfaces/src/test/types/fluidObjectTypes.ts	Remove unnecessary conditional wrapper around type tests
packages/common/core-interfaces/package.json	Update test scripts to use new environment variable pattern
Multiple package.json files	Replace MOCHA_SPEC with FLUID_TEST_MODULE_SYSTEM=CJS in test:mocha:cjs scripts

[github-actions]

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output

> fluid-framework-docs-site@0.0.0 ci:check-links /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test "npm run serve -- --no-open" 3000 check-links

1: starting server using command "npm run serve -- --no-open"
and when url "[ 'http://127.0.0.1:3000' ]" is responding with HTTP status code 200
running tests using command "npm run check-links"


> fluid-framework-docs-site@0.0.0 serve
> docusaurus serve --no-open

[SUCCESS] Serving "build" directory at: http://localhost:3000/

> fluid-framework-docs-site@0.0.0 check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

Crawling...

Stats:
  236987 links
    1726 destination URLs
    1962 URLs ignored
       0 warnings
       0 errors

[jason-ha]

I made silly mistake of trying to run performance pipeline against the test branch which gets picked up by our checks. It is failing per current dependency issues.