[glenjamin]

Do bear in mind that just writing tests using business language in cucumber doesn't make then run. You still have to use some sort of test library underneath it to power the steps. In my current work I'm using the selenium API to do this, which hopefully is creating readable tests which re-use test execution code that makes updating them to UI changes far easier than just using a recording tool.

[3am]

Oh, I know, I just was trying to highlight that the underlying library (as far as I know cucumber) is opaque when defining the test, where in robot it's a little less so. Separately, since you're familiar with it - does cucumber allow you to compose new actions from existing actions?

I had a longer post and pared it back... I actually think both frameworks are good in different situations, it just depends how the company is structured and what kind of QA group you have.

FWIW, I have done QA for 11 years, mostly doing automation.