Write unit test

Add a unit test that verifies the Save button calls onSave with the form values. Render the component with initial values, simulate changing the title and clicking Save, and assert the mock onSave was called once with the updated title and other fields unchanged.

Before I run the test suite, make this unit test easy to approve: keep the Arrange step minimal, name the mocked functions and expected payload clearly, avoid implementation details like internal timers, and flag where flaky behavior could occur (async validation, debounced handlers).

A unit test that asserts a callback was called flakes in CI. Locally it passes. The component uses a debounced save and a Promise in an effect. I don't know whether the flakiness is timing or environment. What is the likely cause and the smallest change to make the test deterministic and reliable in CI?

Our test suite accumulates flaky unit tests whenever components use timers, debounce, or fetches. Each fix is a one-off and the suite slows down. Which single testing habit will most reduce flakiness and speed feedback, and what concrete change should I make to the test helper library to enforce it?