Maybe a silly suggestion but would it be possible to have a sandbox option to run, for example, an insert action but only sandbox it so the results are not actually inserted, to test complex actions prior to bulk inserting a load of test data repeatedly in to a live environment? We currently implement a dumping-ground table for this, duplicate said table and rename it accordingly (often filled with utter garbage but no harm done and an easy clean up)… That way when we are happy we truncate this table and switch the insert to the ‘production’ table. To be able to sandbox these actions for debugging would be great!
Yes, to run the action with no inserts. Essentially a test run, a sandbox event with no consequence should it go utterly Pete Tong (wrong for the non English resident).
I was thinking in something more like this: https://beeceptor.com/ where u could send the insert actions and other action steps to a testing endpoint instead of a database maybe.
Yes Jon I understand what you say, by definition sandbox is a testing environment that isolates untested code changes and outright experimentation from the production environment or repository, so I think how you can’t test an insert without saving it in a database data, then the database would have to be cloned and set up as a test. I don’t think it’s a good idea to rollback for various reasons like incremental fields.
Maybe we should open a discussion on how to create a sandbox more efficiently with Wappler
Isn’t that what a staging environment should do? Basically if you have a staging target then you can test as much as you want in a seperate db that is a replica of your production and once you are ready you push the changes to the production environment and that way you have 2 seperate databases/targets
Yes, actually what I do is send the database to production when I have a beta version. So I am left with a development and test environment (or sandbox) and a production environment. My development environment is always on the same server but with another database and another folder, since I still don’t work with Docker and I don’t want to have problems due to configuration differences between my local environment and the server.
