[kgryte]

Resolves a part of #11352.

Description

What is the purpose of this pull request?

This pull request:

• migrates the tests for stats/incr/mpe from relative tolerance (EPS-scaled) assertions to ULP-based assertions using @stdlib/assert/is-almost-same-value.

Details:

• test/test.js is the only test file in the package containing computed-tolerance assertions; no test.native.js exists.
• Replaced the abs/EPS delta <= tol comparisons (and the associated delta/tol locals and requires) with t.strictEqual( isAlmostSameValue( actual, expected, N ), true, 'returns expected value' );.
• ULP bounds were tightened to the measured minimum by starting from N = 64 and lowering N until the smallest integer which still passes across every fixture value:
  • the accumulator function incrementally computes the mean percentage error: 11 ULP (passes at 11, fails at 10; previous tolerance was 10.0 * EPS).
  • if not provided an input value, the accumulator function returns the current mean percentage error: 1 ULP (passes at 1, fails at 0; previous tolerance was 1.0 * EPS).
• The suite was run twice at the final bounds to confirm determinism: 11/11 passing on both runs.
• make lint-javascript-tests TESTS_FILTER=".*/stats/incr/mpe/.*" is clean, and the only changed file is lib/node_modules/@stdlib/stats/incr/mpe/test/test.js.

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.

No.

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, which studied prior ULP migrations in this repository, applied the same idiom here, and empirically searched for the minimum passing ULP bounds.

---

@stdlib-js/reviewers

---

Generated by Claude Code

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
stats/incr/mpe	$\\color{green}122/122$ $\\color{green}+100.00\\%$	$\\color{green}6/6$ $\\color{green}+100.00\\%$	$\\color{green}2/2$ $\\color{green}+100.00\\%$	$\\color{green}122/122$ $\\color{green}+100.00\\%$

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