test: migrate stats/incr/hmean to ULP-based assertions

[kgryte]

Resolves a part of #11352.

Description

What is the purpose of this pull request?

This pull request:

• migrates the tests for @stdlib/stats/incr/hmean from relative tolerance testing to ULP difference testing.
• replaces the abs/@stdlib/constants/float64/eps requires with @stdlib/assert/is-almost-same-value.
• removes the delta/tol computation and the actual === expected branch in favor of a single t.strictEqual( isAlmostSameValue( actual, expected, 1 ), true, 'returns expected value' ); assertion.

The package has a single test file (test/test.js); there is no test/test.native.js.

Measured ULP bound: the maximum ULP difference across the test data ([ 2.0, 3.0, 2.0, 4.0, 3.0, 4.0 ]) is 1, arising from the final accumulated value (2.769230769230769 vs. 2.7692307692307696). All other iterations are bit-for-bit exact. Accordingly, the assertion uses a bound of 1, which is the minimum passing value: re-running the suite with 0 fails one assertion, while 1 passes all 11 assertions. The suite was run twice at the final bound to confirm determinism.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• [RFC]: Migrate math/base/special packages from relative tolerance testing to ULP difference testing (tracking issue) #11352

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

• Tests pass locally via make test TESTS_FILTER=".*/stats/incr/hmean/.*" (11/11).
• Linting is clean via make lint-javascript-tests TESTS_FILTER=".*/stats/incr/hmean/.*".
• Only lib/node_modules/@stdlib/stats/incr/hmean/test/test.js is modified.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

This PR was authored by Claude Code running as an unattended scheduled task. It studied the prior ULP migrations in the same package family (e.g. stats/incr/nanhmean, stats/incr/mstdev) to mirror the established idiom, applied the test conversion, and determined the minimum passing ULP bound empirically by measuring per-iteration ULP differences and then verifying that 0 fails and 1 passes.

---

@stdlib-js/reviewers

🤖 Generated with Claude Code

https://claude.ai/code/session_01VAFLtSGuZB4wkzEqGU9r1n

---

Generated by Claude Code

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
stats/incr/hmean	$\\color{green}142/142$ $\\color{green}+100.00\\%$	$\\color{green}8/8$ $\\color{green}+100.00\\%$	$\\color{green}2/2$ $\\color{green}+100.00\\%$	$\\color{green}142/142$ $\\color{green}+100.00\\%$

The above coverage report was generated for the changes in this PR.