Hacker News Reader

Comment by ithinkso | Hacker News Reader

Maybe we used it incorrectly but for testing SW on target it's the worst thing I have ever experienced. The 'human readable' keywords are a hidden evil no one should meet. And the sheer amount of them, matched with random Setups and Teardowns, wierd syntax workarounds to do simple stuff, performance...

View on HN

Yeah this is my experience as well, I understand the appeal, hell I was even the one to frontrun/poc it 6 years ago. But in the end it's just worse dev experience, no sane Keywords autocomplete/lookup in any IDE out there(by that time).

In the end you end up programming inside english like DSL with weird quirks, that's somewhere connected to python, with different variable syntax, and not really good debugging.

I guess everyone has to pass through that stage at least once, but I will never go back to it.

Well, nowadays Robot Framework Language Server (which I develop) does have autocomplete/semantic analysis/interactive console/debugger (which can debug Python and Robot Framework at the same time) and a bunch of other things, so, I guess things did improve a bit in the meanwhile...

I suspected LSP would be awesome for it, but nothing existed like 3 years ago - kudos to you sir, I think it would make the experience 10x better.

What would you rather use for end-to-end acceptance testing? Pabot runs multiple robot tests in parallel, meaning dozens of tests can run in a few minutes. It seems acceptable if you start with the assumption that acceptance testing part of the pipeline doesn't need to be run on every commit.

Reply on news.ycombinator.com