bdd - Behat over Cucumber in PHP -


don't me wrong. think both projects fantastic.

but both php , ruby developer wonder if there there compelling reasons, besides possible language barrier, why 1 choose behat on cucumber (with cuke4php) bdd when working php or php framework.

i'm behat developer.

why i've developed behat instead of cucumber customization:

  1. speed. there's no simple way bootstrap/run php ruby code. means need implement wires/proxies , other things, makes tests insanely slower. , slower tests not test, it's code eats customer's money.
  2. extensibility. there few php developers know ruby. it's hard use tool, many don't understand! examples written cucumber ruby code , can't @ cucumber sources, because, let's say, don't know ruby. it's buying submarine when need taxi.

in terms of features, behat , cucumber same (i've worked hard achieve this). in terms of speed/extensibility/logic php developer's perspective - behat better, because it's fast , clean native php tool. behat not cucumber port, might think first, it's built entirely ground on php 5.3. behat trying simulate cucumber input reading (features) , output formatting (formatters), it's not cucumber port (there no ruby syntax constructions in php).


Comments

Popular posts from this blog

python - Scipy curvefit RuntimeError:Optimal parameters not found: Number of calls to function has reached maxfev = 1000 -

c# - How to add a new treeview at the selected node? -

java - netbeans "Please wait - classpath scanning in progress..." -