It's a nice interface, and I like the idea of the environment having the test-editing inline with the context it's operating on.<p>But "UI tests - no code required!" is something I see in various places. It seems to imply the hardest part of creating and maintaining UI-level tests is writing the code.
It reminds me of "PHP was originally designed explicitly for non-programmers (and, reading between the lines, non-programs)" from <a href="https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/" rel="nofollow">https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/</a>
What's the process like when you update the UI? Does it list the interactions that broke and give you the opportunity to view/edit/delete each individually?