[Planeshifter]

Description

What is the purpose of this pull request?

This pull request:

• migrates the tests of blas/base/scasum (test.scasum.js, test.ndarray.js and their .native.js counterparts) from the EPS/relative-tolerance isApprox helper to isAlmostSameValuef from @stdlib/number/float32/base/assert/is-almost-same-value.
• passes the ULP count inline as an integer literal. Every call site uses 1 (all fixtures in all four files). Measured minimum: 0 fails, 1 passes at every call site (checked per call site against test.scasum.js and test.ndarray.js; two consecutive runs gave identical results). The .native.js files use the same value but were skipped locally because the native addon is not built in this environment.
• removes the now-unused EPS/abs requires and the isApprox helper.

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

Reference Packages

Did the content of this pull request follow one or more existing packages? Answering is optional.

This pull request followed these packages:

• blas/base/snrm2

What carried over from the reference(s)?

• Assertion shape (t.strictEqual( isAlmostSameValuef( actual, expected, N ), true, 'returns expected value' )) and removal of the isApprox helper.

What differed, or what did you have to work out yourself?

• Nothing beyond finding the minimum ULP per call site.

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.

Native tests were not run (addon unavailable); please confirm in CI. Pre-commit hooks could not run locally (incomplete node_modules); eslint was run manually on the test directory and was clean.

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

This PR was written primarily by Claude Code as an automated scheduled routine.

---

@stdlib-js/reviewers

---

Generated by Claude Code

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
blas/base/scasum	$\\color{green}369/369$ $\\color{green}+0.00\\%$	$\\color{green}17/17$ $\\color{green}+0.00\\%$	$\\color{green}4/4$ $\\color{green}+0.00\\%$	$\\color{green}369/369$ $\\color{green}+0.00\\%$

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

[kgryte]

LGTM