A week or so ago I posted ForcePilot 1.5 here because I was getting tired of creating the same Salesforce test data again and again.

The idea was pretty simple:

make the changes once → record them → use them on another record.

That part is still there.

But after actually using it while testing Salesforce, I kept running into another problem. Creating the test data was only one part of the work. I still had to go through the test steps, take screenshots, keep evidence somewhere, and then put everything together at the end.

So I ended up building the next version around that.

https://preview.redd.it/vi6allw4gfth1.png?width=1080&format=png&auto=webp&s=48e445e404383bfc7f4308264c2c18b04d97cff1

What you can do now

Testing Sessions

Start a session with a test case and its steps, or just start one without a test case when you're doing exploratory testing.

Screenshots + evidence

Take screenshots while you're testing, paste screenshots from the clipboard, and keep everything together in the same session.

Autofill while testing

Use saved recordings to fill Salesforce fields instead of entering the same setup data again.

Resume testing

Stop halfway through and come back later instead of starting everything again.

Finish the session + export evidence

When you're done, you can export the evidence as a Word document or as a ZIP containing the screenshots.

Everything from 1.5 is still there too... recording field changes, replaying them, relative dates, picklists and multi-selects, retrying failed fields, editing recordings, etc.

A few other things I added:

• Alt + X to open/close ForcePilot
• Bubble / Edge / Off launcher options
• Dark mode
• Better Salesforce object and record detection when navigating
• A bunch of smaller UI and reliability improvements

The main difference for me is that it has gone from:

"make the same Salesforce data faster"

to something more like:

prepare the data → run the test → capture evidence → finish the test

I'm still building this around the way I actually do Salesforce testing, so I'd really like to hear from people who do salesforce testing.

What part of Salesforce testing do you still find unnecessarily repetitive?

GitHub: https://github.com/SamDannyl/ForcePilot

It's free and open source and still very much a work in progress. Would love to hear your suggestions.

And yes, I'm still very much a Salesforce QA guy building a Chrome extension with AI 😅

I got tired of creating the same Salesforce test data over and over, so I made a Chrome extension for it.

If you do Salesforce QA, you probably know what I mean.

You create a record, fill out like 15 fields, do some testing, then need another record with basically the exact same setup.

So I made ForcePilot.

Basically, you can record the field changes you make on a Salesforce record and then replay them on another record.

A few things it can do:

• Record field changes
• Replay them on another record
• Match fields using Salesforce metadata
• Use relative dates (Today + 7 days, etc.)
• Choose whether to fill empty fields or overwrite them
• Retry fields that failed
• Import/export recordings as JSON
• Run from a side panel inside Salesforce

So instead of doing the same setup manually every time, you can just record it once and reuse it.

It's open source and currently works with Salesforce Lightning on Chrome/Edge.

👉 GitHub: Forcepilot

https://preview.redd.it/i0hfxixaaoph1.png?width=918&format=png&auto=webp&s=93a6b3800366b5c8b653473325f9b00234e22a5b

I'm mainly looking for feedback from people who actually work with Salesforce, especially QA, admins and developers.

What part of creating test data do you guys find the most annoying/repetitive?

Also, full disclosure: this is very much vibecoded 😂. I used a lot of ChatGPT while building it. I'm a Salesforce QA guy, not an extension developer.

So please judge the idea/tool, not the quality of my code 😭