Follow-up from #763.
When fixing selectivity display formatting we found that some tests were asserting locale-specific strings (e.g. "5.0%", "0.1%") that would fail on systems with a non-en-US default locale.
Task: audit the test suite for other places where numeric or date strings are asserted as hard-coded literals and update them to either:
- compute the expected value using the same locale-aware call as production code, or
- pin the locale explicitly in the test setup.
Look especially for toFixed, toLocaleString, Intl.NumberFormat, and date formatting.
Follow-up from #763.
When fixing selectivity display formatting we found that some tests were asserting locale-specific strings (e.g.
"5.0%","0.1%") that would fail on systems with a non-en-USdefault locale.Task: audit the test suite for other places where numeric or date strings are asserted as hard-coded literals and update them to either:
Look especially for
toFixed,toLocaleString,Intl.NumberFormat, and date formatting.