◆ MATLAB

Develop unit tests

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWrite a unit test for the 'calculate_stress' function in 'beam_analysis.m' that checks its…+
Write a unit test for the 'calculate_stress' function in 'beam_analysis.m' that checks its output for a zero-load condition, ensuring it returns zero stress. The test should run in the current test framework.
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 commit the new 'thermal_model.m' function, help me improve its unit tests. I need to…+
Before I commit the new 'thermal_model.m' function, help me improve its unit tests. I need to ensure they cover edge cases like extreme temperatures and material property discontinuities, and that they clearly report which specific conditions fail, not just a pass/fail. Also, make sure the tests run quickly.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'control_algorithm.m' function is failing its unit tests intermittently on the build…+
The new 'control_algorithm.m' function is failing its unit tests intermittently, but only on the build server, not on my local machine.
The 'control_algorithm.m' function is failing its unit tests intermittently on the build server, but passes every time on my local machine. My deadline for integrating this into the system is end of day Friday, and Mark in integration is already asking for it. I'm afraid I've introduced a race condition or a dependency I can't see, and I can't tell Mark it's not ready. What's the likely diagnosis for this flaky server-side failure, and what's the best next move to stabilize these tests?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep finding critical bugs in my simulations only after they've been deployed, despite having…+
I keep finding critical bugs in my simulations only after they've been deployed, despite having unit tests.
I keep finding critical bugs in my simulations only after they've been deployed, despite having unit tests. It feels like my tests are too narrow, missing the real-world interactions. I'm losing credibility with the project lead, Dr. Evans, and it's costing us time. What habit should I change in how I approach writing unit tests to catch these broader integration issues earlier?
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 MATLAB'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.