◆ Salesforce

Create unit tests without database interaction

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 Salesforce tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGenerate a basic unit test for the 'CaseCommentTrigger' Apex class that covers 75% of the…+
Generate a basic unit test for the 'CaseCommentTrigger' Apex class that covers 75% of the lines, without trying to insert any actual Case records into the database.
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 acceptWhen I'm creating a new Apex service class, automatically suggest and generate a robust set of…+
When I'm creating a new Apex service class, automatically suggest and generate a robust set of unit tests that simulate various scenarios, including edge cases, without performing any DML operations. The tests should focus on the logic of the code itself, ensuring high coverage and reliability.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm stuck writing unit tests for the 'FinancialCalculator' Apex class. It has complex…+
I need to write unit tests for a complex Apex utility class, but I'm struggling to isolate the logic from database interactions.
I'm stuck writing unit tests for the 'FinancialCalculator' Apex class. It has complex calculations, but no database calls. I'm finding it hard to write tests that only verify the logic without accidentally trying to save or query anything, which just complicates things and slows me down. I need to hit 90% coverage by Friday, and I'm worried about missing the mark. How can I effectively test this class's methods in isolation, focusing purely on the calculations?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently find myself writing unit tests that unnecessarily involve database operations,…+
I frequently waste time creating unit tests that unnecessarily involve database operations, making them slow and fragile.
I consistently find myself writing unit tests that unnecessarily involve database operations, even for Apex classes that are pure logic. This makes my tests slow, brittle, and harder to maintain, and it eats up valuable development time. What habit or approach should I adopt to consistently write efficient unit tests that focus solely on the code's logic, without relying on or interacting with the database?
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.