bdd

Does anyone have an example of a cucumber project with sbt 0.13 and Scala 2.11? Do I need both the cucumber-scala_2.11 and the sbt-cucumber-plugin" % "0.8.0" (is that plugin up to date)? Where does the plugin go now? Where do the .feature files go? Where do the cucumber tests go? How do I run the tests from sbt? (optional) How can I run the tests from IntellJ (15)? Ok, I figured out a solution with the following caveat: I'm not using sbt. Idea We will write cucumber features and steps first. Then we will write a "Runner" class, that will be run by JUnit runner (which will be oblivious to the

I'm just starting with BDD and I'm trying to build a small app, so I can see it working in a real environment, but I'm having trouble deciding what should be a feature. I'm building a tiny shop. I decided that "Compare products" will be a feature and "User can checkout as guest" will be one, but to get to that, I first need to list products. My question is, should "There should be a list of products" be a feature? Thanks! It should probably be a feature, but try wording it from a user's point of view. What does this list of product offer him? User should be able to get an overview of offered

I've been thinking about switching from nose to behave for testing (mocha/chai etc have spoiled me). So far so good, but I can't seem to figure out any way of testing for exceptions besides: @then("It throws a KeyError exception") def step_impl(context): try: konfigure.load_env_mapping("baz", context.configs) except KeyError, e: assert (e.message == "No baz configuration found") With nose I can annotate a test with @raises(KeyError) I can't find anything like this in behave (not in the source, not in the examples, not here). It sure would be grand to be able to specify exceptions that might be

I am new to jasmine here is my src file in which i create Auth class function Auth() { } Auth.prototype.isEmpty = function(str) { return (!str || 0 === str.length); } Auth.prototype.Login = function (username , password) { if (this.isEmpty(username) || this.isEmpty(password)) { return "Username or Password cann't be blank "; } else { return "Logged In !"; } } now i want to test jasmine's toHaveBeenCalled() matcher . Here is what i write it("should be able to Login", function () { spyOn(authobj); expect(authobj.Login('abc', 'abc')).toHaveBeenCalled(); }); but it says that undefined() method

I have a BDD feature containing multiple scenarios. Should each scenario be completely self contained and runnable individually? Should be , yes. It is generally good practise in all forms of TDD (BDD included) to make sure that each "test" can run independently, and isn't coupled with or have a dependency on another test having been run first. This will help avoid creating a brittle test suite (i.e. one that is prone to breaking). That's not to say that you cannot chain readability together. For a very cheap/quick example: Feature: Users can register and log in Scenario: Should be able to

I've just installed cucumber into a new rails project (first time setting it up from scratch) and it works wonderfully when running all tests ( bundle exec cucumber ) but can't find any of my steps when I run a single feature file. How might I start to debug this? rails (3.2.13) cucumber-rails (1.3.1) cucumber (>= 1.2.0) # file listing features/ ├── campaigns │ ├── donating_campaigns.feature │ └── viewing_campaigns.feature ├── step_definitions │ └── campaign_steps.rb └── support └── env.rb It will only find files at the same level or lower in the features directory tree. So if you try to run