[ig42]

I guess we're talking about two different approaches to solving the same problem (code-based tests can't be used by non-technical people). So we can:

1. Substitute writing code with a visual editor. This is, essentially, what Screenster does.

2. Make scripting abstract enough to a point where it starts to resemble plain English. That's, in a nutshell, the approach of Cucumber.

Each of the two has its pros and cons. In my opinion, the key strength of tools like Screenster in this context is how they address visual/css regression testing (specifically, things like text or image formatting issues, layout issues and other things that typically get broken by CSS updates): http://screenster.io/a-better-way-to-do-visual-regression-te...