src/polar/Pie.tsx (1)

356-360: 🏗️ Heavy lift

Add direct tests for Pie/Funnel/Scatter/RadialBar formatter paths

The formatter wiring is added across multiple components, but the current test coverage described in this PR validates only Bar/Line behavior. Please add component-level assertions (or a shared parametrized suite) for Pie/Funnel/Scatter/RadialBar tooltip payload + rendered value paths to prevent regressions in component-specific payload shapes.

As per coding guidelines src/**/*.{ts,tsx}: Aim for 100% unit test code coverage when writing new code.

Also applies to: 424-487, 1012-1025

🤖 Prompt for AI Agents

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

In `@src/polar/Pie.tsx` around lines 356 - 360, Add unit tests that cover the
tooltip formatter wiring for Pie, Funnel, Scatter and RadialBar components: for
each component (Pie component's formatter prop, Funnel, Scatter, RadialBar)
write tests that render the component with a mock Tooltip.formatter function and
assert both the payload shape passed into the formatter and the final rendered
tooltip value; you can implement a shared parametrized test suite that iterates
over component constructors/names and checks (1) that the formatter is called
with the expected payload shape and fields, and (2) that the formatted string is
rendered in the Tooltip output, targeting the Tooltip component’s formatter prop
used by each component to prevent regressions in component-specific payload
shapes.

test/component/Tooltip/graphicalItem.formatter.spec.tsx (2)

34-42: ⚡ Quick win

Assert selector call counts for createSelectorTestCase spy.

Please add spy call-count checks in selector-based tests to catch accidental extra rerenders in tooltip state selection.

Based on learnings: "Applies to test/**/*.{test,spec}.{ts,tsx} : Verify the number of selector calls using the spy object from createSelectorTestCase to spot unnecessary re-renders and improve performance."

Also applies to: 95-101, 117-125

🤖 Prompt for AI Agents

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

In `@test/component/Tooltip/graphicalItem.formatter.spec.tsx` around lines 34 -
42, Add assertions that verify the spy returned from createSelectorTestCase (the
spy variable used in the selector-based tests) was called the expected number of
times to catch extra selector invocations; for example, after rendering in the
test that calls renderTestCase(state => selectTooltipPayload(...)) add an
assertion like expect(spy).toHaveBeenCalledTimes(1) (or the correct expected
count) immediately before or after the existing expectLastCalledWith check, and
apply the same pattern to the other selector-based tests that use the spy so
each test asserts the spy call count.

---

16-134: ⚡ Quick win

Add at least one Area formatter test in this suite.

This suite validates Bar/Line well, but the PR also wires formatter into Area; adding one payload+render assertion for Area would close the regression gap on changed source behavior.

As per coding guidelines "src/**/*.{ts,tsx}: Aim for 100% unit test code coverage when writing new code."

🤖 Prompt for AI Agents

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

In `@test/component/Tooltip/graphicalItem.formatter.spec.tsx` around lines 16 -
134, Add a new test block mirroring the existing "Line with formatter" or "Bar
with formatter" cases but using Area/AreaChart: create an areaFormatter vi.fn(()
=> 'AREA_FORMATTED'), render via createSelectorTestCase with <AreaChart
...><Tooltip /><Area dataKey="pv" id="area-pv" formatter={areaFormatter}
/></AreaChart>, then (1) assert selectTooltipPayload(state, 'axis', 'hover',
'1') contains an entry with dataKey: 'pv' and formatter: areaFormatter and (2)
render and use showTooltip with areaChartMouseHoverTooltipSelector and
expectTooltipPayload to show 'pv : AREA_FORMATTED'; reference Area, AreaChart,
areaFormatter, selectTooltipPayload, createSelectorTestCase, showTooltip,
expectTooltipPayload.