◆ C#

Unit test C code

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 C# tasks

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_discount' function in 'pricing.c' to verify it returns the…+
Write a unit test for the 'calculate_discount' function in 'pricing.c' to verify it returns the correct discounted price for a 10% off coupon.
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 check in the new 'ParseConfigFile' function, ensure the unit tests cover all edge…+
Before I check in the new 'ParseConfigFile' function, ensure the unit tests cover all edge cases for malformed input files, empty files, and missing required fields. We need to be confident it won't crash or misinterpret critical configuration settings.
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 critical bug was found in production in the 'ProcessPayment' module, which supposedly had…+
A critical bug was found in production in a module that had 100% test coverage.
A critical bug was found in production in the 'ProcessPayment' module, which supposedly had 100% unit test coverage. The bug only manifests under a specific sequence of network timeouts and retries, which the tests didn't simulate. I'm afraid of missing other subtle interaction bugs in seemingly well-tested code. How can I identify the gaps in my unit tests that allowed this bug through, and what's the best next step to prevent similar issues?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy unit tests for C code often pass with flying colors, but real-world bugs still slip through,…+
My unit tests pass, but real-world bugs still slip through.
My unit tests for C code often pass with flying colors, but real-world bugs still slip through, especially those related to state changes, memory management, or external dependencies. I find myself writing tests that only confirm the happy path. What habit can I change to consistently write more comprehensive and effective unit tests that genuinely catch potential issues, even for complex C modules?
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 C#'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.