3 ms·
why? i know that 99% is badly written sure. but bdd cucumber style testing if done right can be good. problem i saw people just incapable.
by dlahoda 3y ago
why?
i know that 99% is badly written sure.
but bdd cucumber style testing if done right can be good. problem i saw people just incapable.
- ljm 3y ago“If done right” is carrying a lot of weight there. I don’t mind it if you use cucumber and it still serves the purpose of describing your code’s behaviour, so the output is readable. RSpec’s documentation is a nice example of that. The problem is if people just use it as a syntax over a webdriver, which means that your test behaviour and logic is arbitrarily split into two different languages, the cucumber output is useless, the tests are needlessly slow, and it’s really hard to debug. Cucumber itself is not able to add value there. But that’s not unique to cucumber either. I don’t think many people realise that test writing and architecture is its own skill in programming and so many suites turn into write-only cludges that take 12 hours to run on a cluster of 50 CI workers.
- drewcoo 3y ago> The problem is if people just use it as a syntax over a webdriver Cucumber and WebDriver? Two problematic frameworks does not equal a sane one.
- throwbadubadu 3y agoAren't incapable people the norm and usual problem? ;D Found it quite neutral, not too bad, but also not really helpful.. some nice ideas especially that cross functional collaboration, but in the end the engineers had overhead and hated to write the wrappers, and the other stakeholders still couldn't or didn't want to read/write docs/test, or however it was intended. Admitted, maybe I belong to that incapable crowd as well ;)