Tag Info

New answers tagged

0

BDD actually started at a unit level, in which the users of the classes were other classes! So it's perfectly appropriate to have one technical element being the user of another. It doesn't matter whether it's a "class" or a "module" or a "library" or a "service"; the concepts are still the same. Some of the differences between these two different types of ...


1

All software is meant to eventually serve at the behest of some human user, and a user story caters to that. Consequently, any reference in a user story to a machine or other technological item is generally going to be an implementation detail. Look at this commerce example: Story: Returns go to stock In order to keep track of stock As a store owner I ...


1

Behat is at its best when used a Behaviour Driven Development tool. Try to think of your feature files as requirements, not tests. Change the requirements first, then alter your system to get the tests passing! To answer specifically your question about languages, if you do have a multi-language site, try putting an extra step like 'Given I'm an Englishman' ...


1

Traditionally in BDD we'd start with the outside and move in, so we'd have a web page, then from there move to the actual DB connections until the scenario worked with the web page. However, your question about whether you can use the same feature file with different steps at different levels is appropriate and applicable. I don't think at the moment that ...


-1

I believe you've misunderstood a fundamental concept. Behavior Driven Development is not unit testing. If you're waiting until after you've written your code before you create your feature file, you're doing it wrong. The benefit BDD provides is that you get your business partner to tell you how they will evaluate whether or not the code meets their ...



Top 50 recent answers are included