◆ JavaScript

Write unit test

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskAdd a unit test that verifies the Save button calls onSave with the form values. Render the…+
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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I run the test suite, make this unit test easy to approve: keep the Arrange step…+
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).
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA unit test that asserts a callback was called flakes in CI. Locally it passes. The component…+
Test intermittently fails in CI but passes locally
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?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur test suite accumulates flaky unit tests whenever components use timers, debounce, or…+
many flaky tests around async UI behavior
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?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from JavaScript's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.