[rgbrgb]

Congrats on the launch, neat idea!

You guys have thoughts on automated testing? My experience with visual programming in the wild (zapier, iterable, mailchimp) is that you end up with a lot of orphan and broken "scripts" deployed only to the production environment by well-meaning operators who can't really test or maintain them. It's interesting that this is geared towards devs, but I worry that you'd have a bunch of the same problems as the system grows unless there's a good way to rig up functional/e2e/integration tests the way we usually with cypress, capybara, etc.

Seems like there must be a solution, but my first idea of just setting up a "test" environment that points to other test services seems really costly if it's running on every commit that gets pushes like we often do with CI.

[ishmaelsamuel]

Heya! We have given some thought to implementing CI, reviews, and a sandbox environment.

We've built out some testing functionality that allows users to test their workflows and steps, and we're going to continue down this road to eventually provide our users version control and sandbox environments. It's currently seen as a "nice-to-have" for even our production users, so the timing of when it's implemented is still unclear.