◆ Salesforce

Write test classes for Apex RestService

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 test classes for the 'InvoiceProcessor' Apex RestService to ensure 100% code…+
Write test classes for the 'InvoiceProcessor' Apex RestService to ensure 100% code coverage.
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 deploy this to production, make sure the test classes cover both successful invoice…+
Before I deploy this to production, make sure the test classes cover both successful invoice processing and error handling for invalid invoice data. Also, include tests for different user profiles to ensure security is enforced.
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 'InvoiceProcessor' service just failed in production, halting all payments, and finance is…+
The 'InvoiceProcessor' service just failed in production, causing payment delays, and I'm getting calls from finance.
The 'InvoiceProcessor' service just failed in production, halting all payments, and finance is calling me every five minutes. I'm afraid my test classes didn't catch an edge case, but I can't pinpoint the exact failure without looking at logs. What's the most likely scenario for a production failure that wasn't caught by 100% coverage, and what's the best next step to diagnose and fix it under this pressure?
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 getting production bugs in my Apex services even though my test classes always hit 100%…+
I consistently face production issues with Apex services despite achieving 100% code coverage in my test classes.
I keep getting production bugs in my Apex services even though my test classes always hit 100% code coverage. What habit can I change in my testing approach to ensure my tests are not just covering lines, but truly validating the logic and preventing these costly failures?
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 Salesforce'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.