My startup [0] works with a lot of companies that are non-traditional, as you put it, and gives you the tools to design a CRM (and other business tools) that actually suit your business, if you want to check it out
Good question, these are definitely on our radar and very possible with how it's currently setup.
For us, we're trying to strike the balance of nocode and lowcode so a lot of the advanced features of version control and approval flows are not a priority for a lot of our users. I imagine this will change as we grow though
I see what you mean, I guess the best and only way to do that would be to write integration like tests with something like Cypress, as you could with any web-app.
If you want to verify that it works how you want vs how it's setup to work, then you would be better leaning on existing tools that can do that.
My point about not needing to test it was about the implicit trust you would put in a platform like this, just like you would trust that a library you import behaves how it describes. It's not expected that you should write unit tests and integration tests to verify the behaviour of an external library
Thanks! Definitely somewhat (after being a play on no/lo code obviously). I'd be lying if I said that scene wasn't one of the first things I thought of after coming up with the name.
That's not something we currently offer, but it's certainly something I've thought about a lot.
One of the benefits of no-code tools like Noloco is that you define, very explicitly, what your app should do, display and how it behaves under certain conditions. This really does allow for completely automated integration tests. such as verifying that a filter in the UI does filter the data, verify that when User X logs in, that the permissions for that user are respected, verify that when a record meets certain conditions, a tab isn't accessible.
Defining the rules for the app could (and will) allow you to programmatically verify that it's still working as expected.
However, I think another large appeal for no-code/low-code solutions is not having to worry about testing. You can assume that because you're building your application within the rules of the platform, that everything will function as you tell it to.