Stephen made a point to me in a dev meet-up at FOSDEM that he likes Cucumber in that tests are more readable (even to developers), even though he was sympathetic to the overhead for authors of tests.
So I think I am going to leave them alone. Cucumber has another nice characteristic that tests that depend on not-yet-ported steps will be marked as pending, so I can see how far off I am from getting back to the parity. And yes, you will get the ability to write tests in plain-old JUnit4 tests (which I consider the porting from writing tests in rspec.) Personally, I'd be writing tests in plain-old JUnit4 tests on Groovy. I'm curious to hear from other users on their take on BDD/Cucumber vs JUnit. 2014-02-28 11:06 GMT-08:00 oliver gondža <[email protected]>: > Mostly same story here with the exception I have never felt comfortable or > productive working in ruby. > > Btw, you have expressed dislike towards Cucumber/BDD style features in the > past. Can we take this opportunity to get rid of it as well? It should not > mean significantly more work and if it can bring new people in, I think it > might be worth to try. > > -- > oliver > -- Kohsuke Kawaguchi -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
