Frankly if you are already using cucumber and in the Ruby world, you don’t have to. If you plan to learn Test Automation using Selenium then also, you don’t need to learn as the tutorials on this website are good enough to meet your Test Automation requirements using Cucumber, Ruby and Selenium web driver.
Then why ?
Reason 1:
Well, if you already are a java programmer and have been with it for many years and you are in a java shop and your focus is to deliver solutions but NOT get into language wars…and blah blah, BUT you want to use the BDD framework offered by Cucumber, then cucumber-jvm seems to be the fastest route to get there.
Reason 2:
That is you want to have ATDD/TDD implemented – express behavior of application in terms of acceptance tests [automation code in step definitions behind the cucumber gherkin] , fail them and developers write source code to make them pass, then once again you need cucumber framework.
Reason 3:
You like Eclipse, TestNG, Junit , maven, gradle etc. tools in the Java world and want to stick with them AND want to use cucumber AND have as smooth experience as one would have with Ruby+Cucumber+RubyMine+Gems world — cucumber-jvm seems to be the answer again. More so, because you don’t want to be having to use 10 different IDE’s tools, libraries and so on. Makes life a PITA right.
No comments:
Post a Comment