The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Running Apex tests locally lets new developers skip the sandbox wait (opens in a new tab)

You will learn how a committed renmy.properties file and a local Apex runtime let a new developer run the full Apex test suite on day one without an org.

Why read this

You will also see the same command reused in CI, with its trade-offs.

  1. Clone the repository
  2. Install renmy runtime
  3. Run renmy doctor
  4. Run renmy test
Day one with a local Apex runtime takes four steps, none of which needs an org

The article argues that onboarding a Salesforce developer usually means waiting days for a sandbox, a user, a Permission Set and VPN access before the first Apex test can run. It presents renmy runtime, a local Apex runtime made by Renmy UG in Berlin, as a way to skip that wait. The tool executes Apex, SOQL, DML and Salesforce Flows on the developer’s machine against an embedded PostgreSQL, ships as one binary for macOS, Linux and Windows, and needs no org, Scratch Org, Docker or JVM. The author says governor limits are enforced and each test runs in its own transaction, and cites a public benchmark in which 837 tests ran roughly 45 times faster locally than in an org.

The article walks through a four-step day one: clone the SFDX repository, install the binary with a one-line script (or let the IntelliJ plugin or VS Code extension handle it), run renmy doctor to check the project layout, and then run renmy test “” or narrow it to a class or method. The test environment lives in a renmy.properties file that the team lead generates with renmy config init and commits to the repository. That file sets org defaults such as currency, locale and timezone, seeds Custom Settings so code reading getOrgDefaults() works without @testSetup, and defines a stricter ci profile. Permission Sets load from metadata already in the repository.

Some gaps still need attention. Managed packages whose source is hidden need stubs pulled once by someone with org access and then committed, and multi-currency orgs need a feature flag. The doctor output and failure traces name missing pieces, so closing a gap in the repository helps every later developer. Org access remains necessary for deployment and browser-based work, so the access request still goes in on day one but is off the critical path. The same renmy test “” command runs in CI with the ci profile and needs no connected org, though it requires a license key secret. The Free tier costs nothing per developer for one machine, while the Team tier adds CI runs and seat management, is free during the public beta, and lists at $49 per developer per month. The article concludes that sandboxes remain the right place for UI work and deployment.

Read the original at dev.to (opens in a new tab)

Worth reading?

Must-read

Testing Salesforce Flows locally with renmy runtime before activation (opens in a new tab)

You will learn how to run Record-Triggered Flows and Apex triggers on a local machine, catch order-of-execution overlaps before activation, and what the runtime does not cover.

  1. Retrieve flow into project folder
  2. Write test creating and closing record
  3. Run renmy test locally
  4. Fix overlap, rerun in seconds
  5. Activate and review in sandbox
A local test run replaces repeated sandbox rounds for checking flow and trigger behaviour

renmy runtime, formerly called Nimbus until its October 2026 rename, is a local Salesforce Apex runtime. It executes Apex, SOQL, DML and Salesforce Flows (Autolaunched, Record-Triggered and Screen Flows) on a developer’s own computer against an embedded database, with no org, sandbox or Scratch Org involved. The article argues that testing flows in a shared sandbox is slow and risky: other people’s automation fires alongside yours, test data disappears after refreshes, and overlaps between a flow and an Apex trigger on the same object often surface only after activation. Running locally, a Record-Triggered Flow fires together with the object’s triggers in the platform’s order of execution, so overlaps show up in milliseconds.

The article walks through an example: a Record-Triggered Flow that creates a follow-up Task when an Opportunity is set to Closed Won, alongside an older Apex trigger that also creates a Task. A developer retrieves the flow file into the project folder with the Salesforce CLI. They then write a short Apex test that creates an Account and an Opportunity, moves the stage to Closed Won, and asserts that exactly one Task exists with the expected subject. The admin can read that test as an acceptance criterion. Running renmy test with the test name, or with “” for every test, reports the result. If the trigger also creates a Task, the assertion fails with two Tasks, revealing the overlap. The fix is either to remove the trigger’s logic or to add an entry condition to the flow, and the rerun takes about a second. Once the flow is ready, renmy deploy runs the local checks before anything reaches the org.

The same runtime is available through a browser-based Dev UI started with renmy dev, which offers a test runner, schema browser and coverage explorer. A VS Code extension adds run buttons above each test, and a JetBrains plugin does the same in IntelliJ IDEA, including its Community edition, and can display a flow as a graph. The article is clear about the limits. The runtime executes a Screen Flow’s logic but does not render its screens, so layout, labels and conditional visibility must be checked in a sandbox with a user. It reproduces platform rules closely but is not Salesforce itself, and permissions, page layouts and user acceptance still require an org. The Free tier includes unlimited local test runs on one machine, with no account or card required.

Read the original at dev.to (opens in a new tab)

Worth reading?