◆ Salesforce

Test Apex with field history tracking

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 an Apex test class for the 'OpportunityStageUpdater' that specifically verifies the field…+
Write an Apex test class for the 'OpportunityStageUpdater' that specifically verifies the field history tracking for the 'StageName' field when an opportunity is closed won.
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 writing this Apex test, ensure it not only asserts the field history is recorded but also…+
When writing this Apex test, ensure it not only asserts the field history is recorded but also that the old and new values are correctly captured. I've had tests pass before where the history was there, but the values were wrong, leading to bad audit trails.
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've written an Apex test for a critical update to the 'Account' object that should track…+
My Apex test for field history tracking is failing unexpectedly.
I've written an Apex test for a critical update to the 'Account' object that should track changes to the 'AnnualRevenue' field, but the test is failing, saying no history was recorded. I'm afraid this means our audit trail won't be reliable, and I can't figure out why the test isn't seeing the history. What's the most likely cause for this test failure, and what's the best next step to diagnose it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently lose time debugging Apex tests for field history tracking, often finding that the…+
I consistently struggle to write reliable Apex tests for field history tracking.
I frequently lose time debugging Apex tests for field history tracking, often finding that the tests don't accurately reflect actual data changes or fail for unclear reasons. This undermines my confidence in our audit trails. What habit should I change to consistently write robust and accurate Apex tests for field history tracking, ensuring data integrity and reliable auditing?
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.