test: migrate stats/base/dists/pareto-type1/quantile to ULP-based assertions

[kgryte]

Description

What is the purpose of this pull request?

This pull request:

• migrates @stdlib/stats/base/dists/pareto-type1/quantile tests from relative tolerance (EPS/delta/tol) comparisons to ULP-based assertions using @stdlib/assert/is-almost-same-value, per [RFC]: Migrate math/base/special packages from relative tolerance testing to ULP difference testing (tracking issue) #11352.

Converted files:

• test/test.quantile.js
• test/test.factory.js
• test/test.native.js

test/test.js only performs exact export checks and was left unchanged.

ULP bounds

All three fixture loops (both_large.json, large_alpha.json, large_beta.json) use:

t.strictEqual( isAlmostSameValue( y, expected[ i ], 0 ), true, 'returns expected value' );

File	Previous tolerance	ULP constant	Measured minimum
test.quantile.js	1.0 * EPS * abs( expected[i] )	0	0
test.factory.js	1.0 * EPS * abs( expected[i] )	0	0
test.native.js	1.0 * EPS * abs( expected[i] )	0	0

The bound was determined empirically: the minimum ULP distance was computed for every fixture value in all three fixture files, and the maximum observed distance was 0 — i.e., every returned value is bit-identical to the Julia reference value, so 0 is the tightest possible bound. The suite was run twice at the final value 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?

The native add-on was not compiled in the environment used to measure the bound, so test/test.native.js was skipped locally and its 0 ULP bound is inferred rather than directly measured. The inference is that src/main.c computes beta / stdlib_base_pow( 1.0-p, 1.0/alpha ) using stdlib's own pow port — the same expression and same algorithm as lib/main.js — so results are expected to be bit-identical. Please confirm against a build with add-ons enabled; if native results diverge, the native bound will need to be raised.

Other

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

• Only test files are modified; no source, docs, or benchmark changes.
• Linting was verified with etc/eslint/.eslintrc.tests.js (clean). The editorconfig-checker pre-commit step could not download its binary in this environment; EditorConfig compliance (LF, tab indentation, no trailing whitespace, final newline) was verified manually instead.

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 PR was written primarily by Claude Code, which studied the prior ULP migrations in this family (e.g. stats/base/dists/chi/quantile, stats/base/dists/pareto-type1/kurtosis), applied the same idiom, and measured the minimum ULP bound over the full fixture set.

---

@stdlib-js/reviewers

---

Generated by Claude Code

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
stats/base/dists/pareto-type1/quantile	$\\color{green}319/319$ $\\color{green}+100.00\\%$	$\\color{green}25/25$ $\\color{green}+100.00\\%$	$\\color{green}4/4$ $\\color{green}+100.00\\%$	$\\color{green}319/319$ $\\color{green}+100.00\\%$

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

[Planeshifter]

⚠️ Issue Reference Review

An automated check found potentially unrelated issue/PR references in this PR:

Reference	Assessment	Reasoning
#11352	suspicious	PR migrates stats/base/dists/pareto-type1/quantile tests to ULP-based assertions, but #11352 is an RFC/tracking issue explicitly scoped to migrating math/base/special packages only (per its title and instructions), not stats/base/dists

Why this matters: GitHub automatically closes issues referenced with
closing keywords (Resolves, Closes, Fixes) when the PR is merged. Incorrect
references can accidentally close unrelated issues.

What to do:

• If the reference is correct, no action needed. This check may produce
  false positives.
• If the reference is incorrect, please update your PR description.

This assessment was generated by an AI model and is informational only.

---

Generated by Claude Code