[robertlagrant]

Hello - nice website! Draws you in well.

My standard questions as a coder for any tool like this are:

- how can I automate tests?

- how can I promote software up environments (using automation)?

- how can I use source control?

- how can I roll back a deployment?

Thanks!

[aeberhart]

I agree that once a project gets a bit more complex, these points are very important.

In our low code platform (https://github.com/dashjoin/platform), you end up writing several JSONata (https://jsonata.org/) snippets for ETL, actions, and visualizations.

These can be tested using junit. All changes to the app can be managed and deployed via GitHub. You can check out our sample app:

GitHub: https://github.com/dashjoin/dashjoin-demo Live: https://demo.my.dashjoin.com/

[antonsv]

Thanks! As for source control, we already have project snapshots (that can be taken and restored manually) and environments merging. So you can do it manually right now, but Git integration with in-ui version control is in our roadmap already.

What do you mean by automate tests? What exactly do you want to test?

[aeberhart]

> What do you mean by automate tests? What exactly do you want to test?

One of our customers in the public sector builds a Low Code app that performs automated plausibility checks on forms submitted by clients. These checks can be quite complex since they reflect legislation. In this case it is crucial that you can mock form input and validate the checks against expected results.

[robertlagrant]

Thank you - great. A follow-up on Git - is it easy to understand diffs in pull requests? Can you follow what's changed the way you would with handwritten code?

On test automation I mean being able to write some fast tests that - say - test calculations and things like that, and medium speed tests that mock out the backend and play through the UI really fast, and slower end to end tests that play through the UI with a backend connected. And being able to do all that on Git commit push via CI is really helpful.