◆ Salesforce

Unit test code with CreatedDate logic

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 taskI've written an Apex trigger that uses the CreatedDate of a record. Give me a basic unit test…+
I've written an Apex trigger that uses the CreatedDate of a record. Give me a basic unit test example for it, so I can ensure it's covered before I deploy.
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 push this trigger to production, help me write a unit test for my Apex code that…+
Before I push this trigger to production, help me write a unit test for my Apex code that processes records based on their CreatedDate. I need to make sure it accurately handles records created at different times, especially across different days, to avoid errors in our monthly billing calculations for clients like Acme Corp.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy unit tests for a new trigger are failing, but the code seems correct when I test manually.…+
My unit tests for a new trigger are failing, but the code seems correct when I test manually.
My unit tests for a new trigger are failing, but the code seems correct when I test manually. The trigger relies on CreatedDate, and I'm struggling to set up test data with specific creation dates that accurately simulate real-world scenarios. My project manager, Tom, needs this deployed by Friday. What's the best way to mock or control CreatedDate in unit tests to properly validate my logic, and what's a common pitfall I might be hitting?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI spend too much time debugging unit tests that involve date fields like CreatedDate,…+
I spend too much time debugging unit tests that involve date fields like CreatedDate.
I spend too much time debugging unit tests that involve date fields like CreatedDate, especially when trying to simulate different timeframes. This often leads to delays in deployments and frustration. What habit should I change in how I approach testing date-dependent Apex code to ensure my tests are reliable and quick to write, so I stop losing time on setup and focus on validation?
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.