Why would you say that? Majority of code is repetitive. Why still focus on writing it for every project? I agree that you cannot have 100% of tests without actual code, but a significant percentage can just be feature files only.
Where I come from we do such revolutionary things as writing libraries and defining abstractions to avoid repetitive code. Why introducing a new tool with its own language for this seems like a good idea to anyone utterly baffles me.
Also, I should add, where I've seen karate used on teams it's deepened the division between devs and testers. So in addition to being questionable engineering, it's sociologically toxic.
Comments
Why would you say that? Majority of code is repetitive. Why still focus on writing it for every project? I agree that you cannot have 100% of tests without actual code, but a significant percentage can just be feature files only.
Where I come from we do such revolutionary things as writing libraries and defining abstractions to avoid repetitive code. Why introducing a new tool with its own language for this seems like a good idea to anyone utterly baffles me.
Also, I should add, where I've seen karate used on teams it's deepened the division between devs and testers. So in addition to being questionable engineering, it's sociologically toxic.