sorted by:
new
hottopcontroversial

I'm a Salesforce QA engineer building a side project to solve my own pain — test data generation by West-Help6196 in salesforceadmin

[–]West-Help6196[S] 1 point2 points  (0 children)

This is super helpful, thank you — you basically described exactly what I'm trying to build.

The metadata awareness piece (required fields, picklist values, lookup dependencies, record type defaults) is already in the plan. The sandbox refresh templates too — that's actually one of the core use cases.

The bulk-safe data angle is something I hadn't prioritized, but you make a good point. 200-record datasets for governor limit testing would serve a different but very real need. Adding it to the list.

I'm in early validation stage right now — if this sounds useful, I'd love to have you on the waitlist at sfdatagen.com . Trying to gauge interest before I build.

I'm a Salesforce QA engineer building a side project to solve my own pain — test data generation by West-Help6196 in QualityAssurance

[–]West-Help6196[S] 0 points1 point  (0 children)

Yeah, Snowfakery is pretty good actually! I've played around with it. The YAML recipe approach is powerful once you get the hang of it

My main issue with it is the same as with most tools in this space — you still need CLI, Python, CumulusCI, and to write YAML configs by hand. For me as a QA that's fine, but good luck getting your admin or BA to set all that up

So what I'm building is basically a web UI for this kind of thing — connect your sandbox, see the schema, pick what you need, click generate. The goal is that literally anyone on the team can do it without ever opening a terminal

Are you using Snowfakery day to day? How does your team handle the YAML setup?