Sure, and my issue isn’t that it’s capable of my requirements, but simple to use and meets those requirements. Simplicity is a quality all its own.
JUnit provides sufficient output to meet my requirements, so why overcomplicate it w/ Cucumber? AFAIK, cucumber tests in Java output JUinit as well (at least ours does), so what value exactly is Cucumber providing?
If you don’t want the scenarios that are readable in a business requirement format then it’s not worth the trouble. I haven’t ever seen anyone use it in that way.
Cucumber can do all of that. Except for failures over time but I’ve never used a framework for that. CI tools typically track that.
Sure, and my issue isn’t that it’s capable of my requirements, but simple to use and meets those requirements. Simplicity is a quality all its own.
JUnit provides sufficient output to meet my requirements, so why overcomplicate it w/ Cucumber? AFAIK, cucumber tests in Java output JUinit as well (at least ours does), so what value exactly is Cucumber providing?
If you don’t want the scenarios that are readable in a business requirement format then it’s not worth the trouble. I haven’t ever seen anyone use it in that way.