◆ Salesforce

Set up continuous integration for Apex tests

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 taskSet up continuous integration for our Apex tests so that every time a developer pushes code to…+
Set up continuous integration for our Apex tests so that every time a developer pushes code to the 'dev' branch, the tests run automatically and report success or failure to the team's Slack channel.
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 finalize this CI setup for Apex tests, what are the key metrics or thresholds I should…+
Before I finalize this CI setup for Apex tests, what are the key metrics or thresholds I should monitor to ensure the test suite is actually providing value and not just passing silently? I want to catch regressions early and ensure code quality, not just green builds.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur CI pipeline for Apex tests is failing intermittently on the 'feature/new-dashboard' branch,…+
The CI pipeline for Apex tests just started failing intermittently without any code changes.
Our CI pipeline for Apex tests is failing intermittently on the 'feature/new-dashboard' branch, but no code changes have been made to the tests themselves. I'm afraid this will erode trust in our automated testing, and I don't know if it's an environment issue, a flaky test, or a configuration problem. What's the most efficient way to pinpoint the root cause without disrupting other developers?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur Apex test suite is growing, and test failures are becoming harder to diagnose quickly,…+
Our Apex test suite is growing, and test failures are becoming harder to diagnose quickly.
Our Apex test suite is growing, and test failures are becoming harder to diagnose quickly, leading to longer merge times and developer frustration. We spend too much time sifting through logs. What habit should I change to ensure our test failures are always clear, actionable, and point directly to the problem, making our CI process more efficient?
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.