test/chart/BarChart.spec.tsx (1)

2487-2492: ⚠️ Potential issue | 🔴 Critical

Bug: y attribute not updated to match the new d path.

The d attribute starts at y=27.79 and height was updated to 11.21, but y on line 2492 still reads '24.9875' (the old value). This mismatch will cause the test assertion to fail.

Proposed fix

         d: 'M 12.2571,27.79 h 90 v 11.21 h -90 Z',
         height: '11.21',
         radius: '0',
         width: '90',
         x: '12.2571',
-        y: '24.9875',
+        y: '27.79',

test/state/selectors/radarSelectors.spec.tsx (1)

407-455: ⚠️ Potential issue | 🟡 Minor

Add fake timers setup for this suite.

This spec doesn’t enable vi.useFakeTimers(), which the test guidelines require for consistent RAF/autoBatch behavior.

As per coding guidelines, "Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame".

test/state/selectors/scatterSelectors.spec.tsx (1)

371-416: ⚠️ Potential issue | 🟡 Minor

Add fake timers setup for this selector test.

This spec doesn’t enable vi.useFakeTimers(), which the test guidelines require for consistent RAF/autoBatch behavior.

As per coding guidelines, "Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame".

test/cartesian/Line.spec.tsx (1)

32-39: ⚠️ Potential issue | 🟡 Minor

Add fake timers setup for this suite.

This spec doesn’t enable vi.useFakeTimers(), which the test guidelines require for consistent RAF/autoBatch behavior.

As per coding guidelines, "Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame".

test/cartesian/ReferenceLine/ReferenceLine.spec.tsx (1)

293-299: ⚠️ Potential issue | 🟡 Minor

Add fake timers setup for this suite.

This spec doesn’t enable vi.useFakeTimers(), which the test guidelines require for consistent RAF/autoBatch behavior.

As per coding guidelines, "Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame".

test/polar/Radar.animation.spec.tsx (1)

203-211: ⚠️ Potential issue | 🟡 Minor

Enable fake timers for animation tests.

This spec doesn’t enable vi.useFakeTimers(), which the test guidelines require for consistent RAF/autoBatch behavior.

As per coding guidelines, "Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame".

test/cartesian/Scatter.spec.tsx (1)

34-42: ⚠️ Potential issue | 🔴 Critical

cy and transform.y mismatch in first scatter point expectation

The first scatter point has cy: '470.5' (line 37) but transform: 'translate(54, 467.77777777777777)' (line 40). Since the Symbols component renders both from the same coordinate value, they must match. All other scatter points in this expectation correctly have consistent values. Update the transform to 'translate(54, 470.5)' to align with the cy value.

test/chart/ScatterChart.spec.tsx (4)

874-882: ⚠️ Potential issue | 🔴 Critical

Bug: cy value doesn't match the transform y-coordinate.

Line 877 sets cy: '135' but line 880 still has transform: 'translate(120, 125)'. The transform y=125 doesn't match cy='135'. Same mismatch pattern as the previous scatter point issue.

🐛 Proposed fix — align cy and transform

-          cy: '135',
+          cy: '125',

or

-          transform: 'translate(120, 125)',
+          transform: 'translate(120, 135)',

---

1253-1261: ⚠️ Potential issue | 🔴 Critical

Bug: cx value doesn't match the transform x-coordinate.

Line 1255 sets cx: '160' but line 1259 still has transform: 'translate(186.66666666666669, 185)'. The transform x=186.66666666666669 doesn't match cx='160'.

🐛 Proposed fix — align cx and transform

-        cx: '160',
+        cx: '186.66666666666669',

or

-        transform: 'translate(186.66666666666669, 185)',
+        transform: 'translate(160, 185)',

---

796-803: ⚠️ Potential issue | 🔴 Critical

Bug: duplicate index: 2 — likely should remain index: 3.

Lines 798 and 799 both have index: 2, creating the sequence 0, 1, 2, 2, 4, 5, 6 (missing index 3). Compare with the similar test at lines 937–943 which has sequential indices 0, 1, 2, 3, 4. Line 799 was likely meant to keep index: 3.

🐛 Proposed fix

-        { index: 2, coordinate: 85, value: 300, offset: 0 },
+        { index: 3, coordinate: 85, value: 300, offset: 0 },

---

308-316: ⚠️ Potential issue | 🔴 Critical

Three cx/cy–transform coordinate mismatches in test expectations.

The expectScatterPoints helper compares SVG element attributes directly using toEqual(). In the current test expectations:

• Line 310: cx: '91.5' but transform: 'translate(109.16666666666666, 338)' — cx doesn't match the x in transform
• Line 877: cy: '135' but transform: 'translate(120, 125)' — cy doesn't match the y in transform
• Line 1255: cx: '160' but transform: 'translate(186.66666666666669, 185)' — cx doesn't match the x in transform

In all other scatter point expectations throughout the file, cx matches transform x and cy matches transform y. These three inconsistencies will cause test failures if the component renders the correct values.

Mismatched expectations requiring fixes

Fix by aligning cx/cy with their corresponding transform coordinates, or vice versa. Choose the value that matches what the component actually renders:

1. Line 310–314: Align cx: '91.5' with transform or update transform to 'translate(91.5, 338)'
2. Line 877–880: Align cy: '135' with transform or update transform to 'translate(120, 135)'
3. Line 1255–1259: Align cx: '160' with transform or update transform to 'translate(160, 185)'

test/cartesian/XAxis/XAxis.padding.spec.tsx (1)

665-691: ⚠️ Potential issue | 🔴 Critical

Fix non-monotonic tick sequence and remove duplicate test case.

The "Render Bars with padding on the right" test (lines 665-691) has incorrect tick expectations producing the sequence 110, 90, 90, 150, 170:

• Ticks are non-monotonic (110 → 90 is a decrease)
• Value 90 appears twice at different positions
• The first tick has y: '253' while all others have y: '273', indicating a layout anomaly

All other padding tests with the same domain [90, 170] correctly produce 90, 110, 130, 150, 170 with consistent y-positioning. Align this test to match the expected pattern.

Additionally, lines 701–702 contain a duplicate test case: both specify { providedTickCount: 9, expectedTickCount: 9 }. Remove the redundant entry.

test/polar/PolarGrid.spec.tsx (1)

854-861: ⚠️ Potential issue | 🔴 Critical

Fix invalid coordinate value with two decimal points in test expectation.

Line 858 contains y2: '250.45894683899488.00000000000003' — a value with two decimal points that is mathematically invalid. In a polar grid, angle 0° and angle 360° represent the same direction and should produce identical line coordinates. The first grid line (angle 0°) correctly has y2: '150', so the last grid line (angle 360°) should also have y2: '150'. The current value appears to be an accidental string concatenation.

-          y2: '250.45894683899488.00000000000003',
+          y2: '150',

test/cartesian/YAxis/YAxis.ticks.spec.tsx (1)

249-271: ⚠️ Potential issue | 🔴 Critical

Verify test expectations for domain [0, 200] with tickCount=4 and allowDecimals=false.

The test expectations appear to be incomplete or incorrect. Investigation reveals:

1. Algorithm mismatch: With domain [0, 200] fixed and tickCount=4, getTickValuesFixedDomain uses step=100, which produces only 3 ticks: [0, 100, 200]. The test expects 4 ticks [0, 100, 140, 200], but the algorithm cannot generate this set.

2. Duplicate coordinates in selector test: Lines 259-260 show both value 140 and value 200 mapped to coordinate 5, which is impossible—each value can only have one coordinate.

3. Linear scale verification failure: For scale domain [0, 200] → range [5, 265]:

   • Value 100 should map to coordinate 135 (correct in selector; rendered shows 174)
   • Value 140 should map to coordinate 83 (selector shows 5; rendered shows 135)

4. Non-uniform spacing: The niceTicks [0, 100, 140, 200] have gaps of 100, 40, 60—unusual for a tick algorithm. The getTickValuesFixedDomain with step=100 would naturally produce uniform spacing.

These inconsistencies suggest the test expectations were not properly updated during the recent "improved nice tick values" commit (b546890), which acknowledged ~190 remaining manual test failures.

test/cartesian/XAxis/XAxis.vertical.spec.tsx (1)

198-228: ⚠️ Potential issue | 🟡 Minor

Use expectLastCalledWith for last-call assertions.

Please replace the last-call assertion in this block (and keep the file consistent) with the helper to match the test guidelines.

♻️ Suggested update

-import { describe, expect, it, vi } from 'vitest';
+import { describe, expect, it, vi } from 'vitest';
+import { expectLastCalledWith } from '../../helper/expectLastCalledWith';
...
-      expect(axisSettingsSpy).toHaveBeenLastCalledWith(expectedSettings);
+      expectLastCalledWith(axisSettingsSpy, expectedSettings);

As per coding guidelines: Use the expectLastCalledWith helper function instead of expect(spy).toHaveBeenLastCalledWith(...) for better typing and autocompletion.

src/util/scale/getNiceTickValues.ts (2)

152-169: ⚠️ Potential issue | 🟡 Minor

Update calculateStep JSDoc for the new stepFn parameter.

The signature now accepts stepFn, but the JSDoc doesn’t document it. Please add it so omnidoc stays correct.

📚 Suggested doc update

- * `@param`  correctionFactor A correction factor
+ * `@param`  correctionFactor A correction factor
+ * `@param`  stepFn           Function to compute the step size

As per coding guidelines: JSDoc comments and TypeScript definitions in source files must be kept up-to-date as they are used to autogenerate API documentation via 'npm run omnidoc'.

---

220-276: ⚠️ Potential issue | 🟡 Minor

Document the new useNiceTicks parameter.

Both tick helpers now accept useNiceTicks, but it’s missing from their JSDoc blocks. Please add it for accurate API docs.

📚 Suggested doc update

  * `@param` tickCount     The count of ticks
  * `@param` allowDecimals Allow the ticks to be decimals or not
+ * `@param` useNiceTicks  When true, snap steps to nice numbers
  * `@return` array of ticks

  * `@param` tickCount     The count of ticks. This function may return less than tickCount ticks if the interval is too small.
  * `@param` allowDecimals Allow the ticks to be decimals or not
+ * `@param` useNiceTicks  When true, snap steps to nice numbers
  * `@return` array of ticks

As per coding guidelines: JSDoc comments and TypeScript definitions in source files must be kept up-to-date as they are used to autogenerate API documentation via 'npm run omnidoc'.

test/util/scale/getNiceTickValues.spec.ts (1)

1-11: ⚠️ Potential issue | 🟡 Minor

Initialize fake timers for this spec.

This file doesn’t call vi.useFakeTimers(), which is required for tests in this repo.

⏱️ Suggested update

-import { describe } from 'vitest';
+import { afterEach, beforeEach, describe, vi } from 'vitest';
...
+beforeEach(() => {
+  vi.useFakeTimers();
+});
+
+afterEach(() => {
+  vi.useRealTimers();
+});

As per coding guidelines: Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame.

test/chart/RadarChart.spec.tsx (1)

156-173: ⚠️ Potential issue | 🟡 Minor

Switch to expectLastCalledWith for last-call assertions

These assertions still use toHaveBeenLastCalledWith; please use the helper for consistency and better typings.

Suggested update

-    expect(angleAxisSettingsSpy).toHaveBeenLastCalledWith({
+    expectLastCalledWith(angleAxisSettingsSpy, {
       allowDataOverflow: false,
       allowDecimals: false,
       allowDuplicatedCategory: false,
       dataKey: undefined,
       domain: undefined,
       id: 0,
       includeHidden: false,
       name: undefined,
       reversed: false,
       useNiceTicks: false,
       scale: 'auto',
       tick: true,
       tickCount: undefined,
       ticks: undefined,
       type: 'category',
       unit: undefined,
-    });
+    });

-    expect(angleAxisSettingsSpy).toHaveBeenLastCalledWith({
+    expectLastCalledWith(angleAxisSettingsSpy, {
       allowDataOverflow: false,
       allowDecimals: false,
       allowDuplicatedCategory: false,
       dataKey: undefined,
       domain: undefined,
       id: 0,
       includeHidden: false,
       name: undefined,
       reversed: false,
       useNiceTicks: false,
       scale: 'auto',
       tick: true,
       tickCount: undefined,
       ticks: undefined,
       type: 'category',
       unit: undefined,
-    });
+    });

As per coding guidelines, "Use the expectLastCalledWith helper function instead of expect(spy).toHaveBeenLastCalledWith(...) for better typing and autocompletion".

Also applies to: 206-223

test/state/selectors/axisSelectors.spec.tsx (1)

2286-2316: ⚠️ Potential issue | 🟡 Minor

Use expectLastCalledWith for last-call assertions

This block still uses toHaveBeenLastCalledWith. Please switch to the helper.

Suggested update

-    expect(xAxisSpy).toHaveBeenLastCalledWith({
+    expectLastCalledWith(xAxisSpy, {
       allowDataOverflow: false,
       allowDecimals: true,
       allowDuplicatedCategory: true,
       angle: 0,
       dataKey: undefined,
       domain: undefined,
       height: 30,
       hide: true,
       id: 0,
       includeHidden: false,
       interval: 'preserveEnd',
       minTickGap: 5,
       mirror: false,
       name: undefined,
       orientation: 'bottom',
       padding: {
         left: 0,
         right: 0,
       },
       reversed: false,
       useNiceTicks: false,
       scale: expect.toBeRechartsScale({ domain: [0, 1, 2, 3, 4, 5], range: [5, 95] }),
       tick: true,
       tickCount: 5,
       tickFormatter: undefined,
       ticks: undefined,
       type: 'category',
       unit: undefined,
-    });
-    expect(yAxisSpy).toHaveBeenLastCalledWith(undefined);
+    });
+    expectLastCalledWith(yAxisSpy, undefined);

As per coding guidelines, "Use the expectLastCalledWith helper function instead of expect(spy).toHaveBeenLastCalledWith(...) for better typing and autocompletion".

test/polar/PolarRadiusAxis.spec.tsx (2)

1189-1207: ⚠️ Potential issue | 🟡 Minor

Use expectLastCalledWith for the state integration assertion.

The expected axis settings check should use the helper for typing consistency.

Suggested fix

-      expect(radiusAxisSpy).toHaveBeenLastCalledWith(expectedAxis);
+      expectLastCalledWith(radiusAxisSpy, expectedAxis);

As per coding guidelines "Use the expectLastCalledWith helper function instead of expect(spy).toHaveBeenLastCalledWith(...) for better typing and autocompletion".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@test/polar/PolarRadiusAxis.spec.tsx` around lines 1189 - 1207, Replace the
direct Jest assertion that uses toHaveBeenLastCalledWith with the typed helper
expectLastCalledWith: update the test assertion that currently calls
expect(radiusAxisSpy).toHaveBeenLastCalledWith(expectedAxis) to use
expectLastCalledWith(radiusAxisSpy, expectedAxis) so typing and autocompletion
are preserved; this change should be made where radiusAxisSpy and expectedAxis
are referenced in PolarRadiusAxis.spec.tsx and ensure the expectLastCalledWith
helper is imported/available in the test file.

---

1-4: ⚠️ Potential issue | 🟡 Minor

Add fake timers for this test file.

The suite runs React tests without enabling fake timers, which is required by repo guidelines.

Suggested fix

-import { describe, expect, it, vi } from 'vitest';
+import { afterEach, beforeEach, describe, expect, it, vi } from 'vitest';
 ...
 describe('<PolarRadiusAxis />', () => {
+  beforeEach(() => {
+    vi.useFakeTimers();
+  });
+  afterEach(() => {
+    vi.useRealTimers();
+  });

As per coding guidelines "Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@test/polar/PolarRadiusAxis.spec.tsx` around lines 1 - 4, The test suite in
PolarRadiusAxis.spec.tsx must enable fake timers; call vi.useFakeTimers() before
the tests run (e.g., in a top-level beforeAll or immediately after imports) and
restore timers with vi.useRealTimers() in afterAll to satisfy the repo guideline
about Redux autoBatchEnhancer and requestAnimationFrame; update the file where
describe/it/vi are used to ensure vi.useFakeTimers() is active for the suite and
vi.useRealTimers() is called in teardown.

test/polar/PolarAngleAxis/PolarAngleAxis.spec.tsx (2)

858-878: ⚠️ Potential issue | 🟡 Minor

Use expectLastCalledWith for the spy assertions here.

Line 858 and Line 877 use toHaveBeenLastCalledWith, which the test guidelines discourage.

Suggested fix

-      expect(angleAxisSettingsSpy).toHaveBeenLastCalledWith({
+      expectLastCalledWith(angleAxisSettingsSpy, {
         allowDataOverflow: false,
         allowDecimals: false,
         allowDuplicatedCategory: false,
         dataKey: 'angle',
         domain: [0, 360],
         id: 0,
         includeHidden: false,
         name: undefined,
         reversed: false,
         niceTicks: false,
         scale: 'auto',
         tick: true,
         tickCount: 9,
         ticks: undefined,
         type: 'number',
         unit: undefined,
-      });
+      });
 
-      expect(niceTicksSpy).toHaveBeenLastCalledWith([0, 45, 90, 135, 180, 225, 270, 315, 360]);
+      expectLastCalledWith(niceTicksSpy, [0, 45, 90, 135, 180, 225, 270, 315, 360]);

As per coding guidelines "Use the expectLastCalledWith helper function instead of expect(spy).toHaveBeenLastCalledWith(...) for better typing and autocompletion".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@test/polar/PolarAngleAxis/PolarAngleAxis.spec.tsx` around lines 858 - 878,
Replace the two assertions that call toHaveBeenLastCalledWith on the spies with
the project's expectLastCalledWith helper: locate the assertions against
angleAxisSettingsSpy and niceTicksSpy in PolarAngleAxis.spec.tsx and change them
to use expectLastCalledWith(angleAxisSettingsSpy, { ...expected settings... })
and expectLastCalledWith(niceTicksSpy, [0,45,90,135,180,225,270,315,360])
respectively so the tests follow the guideline and gain the improved
typing/autocomplete behavior.

---

117-120: ⚠️ Potential issue | 🟡 Minor

Add fake timers for this test file.

The current suite doesn’t enable fake timers, which is required here.

Suggested fix

-import { describe, expect, it, Mock, test, vi } from 'vitest';
+import { afterEach, beforeEach, describe, expect, it, Mock, test, vi } from 'vitest';
 ...
 describe('<PolarAngleAxis />', () => {
+  beforeEach(() => {
+    vi.useFakeTimers();
+  });
+  afterEach(() => {
+    vi.useRealTimers();
+  });

As per coding guidelines "Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@test/polar/PolarAngleAxis/PolarAngleAxis.spec.tsx` around lines 117 - 120,
The test suite in PolarAngleAxis.spec.tsx needs fake timers enabled; add a
vi.useFakeTimers() call at the start of the suite (e.g., inside the outer
describe('<PolarAngleAxis />') or a beforeAll block) and pair it with
vi.useRealTimers() in an afterAll/afterEach cleanup to avoid leaking timers;
update the file where createSelectorTestCase/renderTestCase are defined so the
fake timers are active for tests that depend on requestAnimationFrame/Redux
autoBatchEnhancer.

test/component/Tooltip/Tooltip.payload.spec.tsx (1)

443-446: ⚠️ Potential issue | 🟡 Minor

Add fake timers to the shared test setup.

This file’s tests should enable fake timers per repository guidelines.

Suggested fix

-import { beforeEach, describe, expect, it } from 'vitest';
+import { beforeEach, describe, expect, it, vi } from 'vitest';
 ...
   beforeEach(() => {
+    vi.useFakeTimers();
     mockGetBoundingClientRect({ width: 100, height: 100 });
   });

As per coding guidelines "Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@test/component/Tooltip/Tooltip.payload.spec.tsx` around lines 443 - 446, Add
fake timers to the test suite by invoking vi.useFakeTimers() in the shared setup
and cleaning up with vi.useRealTimers() afterwards; update the describe('Tooltip
payload') setup by adding vi.useFakeTimers() inside the beforeEach handler
(where mockGetBoundingClientRect is called) and add an afterEach that calls
vi.useRealTimers() to restore real timers so tests using
requestAnimationFrame/Redux autoBatchEnhancer behave deterministically.

src/util/scale/getNiceTickValues.ts (1)

152-170: ⚠️ Potential issue | 🟡 Minor

Update JSDoc to cover the new parameters.

stepFn and niceTicks were added but are missing from the function docs.

Suggested fix

 /**
  * Calculate the step
  *
  * `@param`  min              The minimum value of an interval
  * `@param`  max              The maximum value of an interval
  * `@param`  tickCount        The count of ticks
  * `@param`  allowDecimals    Allow the ticks to be decimals or not
  * `@param`  correctionFactor A correction factor
+ * `@param`  stepFn           Step function used to round the rough step
  * `@return` The step, minimum value of ticks, maximum value of ticks
  */

 /**
  * Calculate the ticks of an interval. Ticks can appear outside the interval
  * if it makes them more rounded and nice.
  *
  * `@param` tuple of [min,max] min: The minimum value, max: The maximum value
  * `@param` tickCount     The count of ticks
  * `@param` allowDecimals Allow the ticks to be decimals or not
+ * `@param` niceTicks     When true, use nice-number step snapping
  * `@return` array of ticks
  */

 /**
  * Calculate the ticks of an interval.
  * Ticks will be constrained to the interval [min, max] even if it makes them less rounded and nice.
  *
  * `@param` tuple of [min,max] min: The minimum value, max: The maximum value
  * `@param` tickCount     The count of ticks. This function may return less than tickCount ticks if the interval is too small.
  * `@param` allowDecimals Allow the ticks to be decimals or not
+ * `@param` niceTicks     When true, use nice-number step snapping
  * `@return` array of ticks
  */

As per coding guidelines "JSDoc comments and TypeScript definitions in source files must be kept up-to-date as they are used to autogenerate API documentation via 'npm run omnidoc'".

Also applies to: 220-276

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/util/scale/getNiceTickValues.ts` around lines 152 - 170, The JSDoc for
calculateStep is out of date: add entries for the new parameters stepFn
(StepFunction used to compute/formats steps) and niceTicks (boolean controlling
whether tick extents are adjusted to "nice" values) and update the
`@return/description` if the returned shape changed; locate the calculateStep
function and its signature with parameters min, max, tickCount, allowDecimals,
correctionFactor, stepFn and any use of niceTicks, then add clear JSDoc `@param`
lines for stepFn and niceTicks (briefly describing purpose and types) and ensure
the `@return` block matches the actual returned object shape.

test/cartesian/XAxis/XAxis.vertical.spec.tsx (2)

198-230: ⚠️ Potential issue | 🟡 Minor

Use expectLastCalledWith for the axis settings assertion.

Line 228 still uses toHaveBeenLastCalledWith, which the test guidelines discourage for typing reasons.

Suggested fix

 import { ExpectAxisDomain, expectXAxisTicks } from '../../helper/expectAxisTicks';
+import { expectLastCalledWith } from '../../helper/expectLastCalledWith';
 ...
-      expect(axisSettingsSpy).toHaveBeenLastCalledWith(expectedSettings);
+      expectLastCalledWith(axisSettingsSpy, expectedSettings);

As per coding guidelines "Use the expectLastCalledWith helper function instead of expect(spy).toHaveBeenLastCalledWith(...) for better typing and autocompletion".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@test/cartesian/XAxis/XAxis.vertical.spec.tsx` around lines 198 - 230, Replace
the typed assertion that uses Jest's toHaveBeenLastCalledWith with the project
helper expectLastCalledWith: change the call that currently reads
expect(axisSettingsSpy).toHaveBeenLastCalledWith(expectedSettings) to use
expectLastCalledWith(axisSettingsSpy, expectedSettings). Keep the remaining
assertions for itemDataSpy unchanged; if the test helper expectLastCalledWith is
not already imported in the test file, add the import so the helper is
available.

---

16-27: ⚠️ Potential issue | 🟡 Minor

Add fake timers to the test setup.

This file runs React tests but does not enable fake timers, which is required in this repo’s test guidelines.

Suggested fix

-import { describe, expect, it, vi } from 'vitest';
+import { afterEach, beforeEach, describe, expect, it, vi } from 'vitest';
 ...
 describe('<XAxis />', () => {
+  beforeEach(() => {
+    vi.useFakeTimers();
+  });
+  afterEach(() => {
+    vi.useRealTimers();
+  });

As per coding guidelines "Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@test/cartesian/XAxis/XAxis.vertical.spec.tsx` around lines 16 - 27, The test
suite for XAxis (describe('<XAxis />') / inner describe('layout=vertical'))
lacks fake timers; add vi.useFakeTimers() at the start of the test setup (e.g.,
in a beforeAll or beforeEach inside the describe('<XAxis />') block) and restore
real timers after tests with vi.useRealTimers() in afterAll/afterEach to satisfy
the repo guideline about Redux autoBatchEnhancer and requestAnimationFrame;
update the test file XAxis.vertical.spec.tsx by locating the top-level
describe('<XAxis />') and adding these setup/teardown calls.

test/util/scale/getNiceTickValues.spec.ts (1)

1-3: ⚠️ Potential issue | 🟡 Minor

Add fake timers for this test suite.

The repo’s test guidelines require fake timers for all tests.

Suggested fix

-import { describe } from 'vitest';
+import { afterEach, beforeEach, describe, vi } from 'vitest';
 ...
+beforeEach(() => {
+  vi.useFakeTimers();
+});
+
+afterEach(() => {
+  vi.useRealTimers();
+});

As per coding guidelines "Use vi.useFakeTimers() in all tests due to Redux autoBatchEnhancer dependency on timers and requestAnimationFrame".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@test/util/scale/getNiceTickValues.spec.ts` around lines 1 - 3, The test suite
in getNiceTickValues.spec.ts must enable fake timers per repo guidelines: inside
the top-level describe block for this file, add setup/teardown to call
vi.useFakeTimers() before tests (e.g., in beforeAll or beforeEach) and
vi.useRealTimers() after tests (afterAll or afterEach) so timers and
requestAnimationFrame are stubbed during tests; locate the describe(...) block
in the file and add the before/after hooks referencing vi.useFakeTimers and
vi.useRealTimers.