bdd

I currently use a simple convention for my unit tests. If I have a class named "EmployeeReader", I create a test class named "EmployeeReader.Tests. I then create all the tests for the class in the test class with names such as: Reading_Valid_Employee_Data_Correctly_Generates_Employee_Object Reading_Missing_Employee_Data_Throws_Invalid_Employee_ID_Exception and so on. I have recently been reading about a different type of naming convention used in BDD. I like the readability of this naming, to end up with a list of tests something like: When_Reading_Valid_Employee (fixture) Employee_Object_Is

For my SpecFlow tests, I want to setup an individual logging / tracing of the test progress during the execution of tests. E.g. i want to write all passed / failed steps started / ended scenarios started / ended features to the windows event log (in order to synchronize it with event log messages generated by other system components during the test). I tried to use the [BeforeFeature], [BeforeScenario], [BeforeStep] Hooks for doing that, but it turned out that I do not have all the required information within this hooks. E.g. i do not know how to get the current text line of the current step

I am trying to submit a form without button using just Capybara and Rspec (no Cucumber or Selenium, I know there is already a question about that). I've seen there is a gist to add a method to submit a form without button: module SubmitRackTestFormWithoutButton def submit_form! Capybara::RackTest::Form.new(driver, form).submit({}) end end Capybara::RackTest::Node.send :include, SubmitRackTestFormWithoutButton https://gist.github.com/989533 , but I've not gotten it to work and I left a comment on it: I get undefined method `submit_form!' for #Capybara::Node::Element:... actually by "Capybara:

I'm writing a framework for RESTful API test automation, I already decided to go with REST Assured, I'm not 100% sure about add a layer to allow define tests using a domain specific language like Gherkin, therefore adding a BDD framework like Cucumber. What is your opinion? Is a good approach to use BDD in API automation testing? I am currently using BDD for RestAPI Testing. Here is pros and cons for BDD RestAPI Automation framework. Technology We used: Cucumber,Java,Rest-Assured and junit Following pros and cons are my own comment or personal view. It is based on my experience. Pros: Easy to

Say a Chef can make Recipes, and Sous-Chefs can create Recipes that must be approved by a Head Chef. You want to test that, when a Head Chef views her homepage, she sees Recipes that she herself created. You also want to test that she sees there are Recipes awaiting her approval. I can think of two ways to do this: Test that the view contains certain words, like "Your recipes" and "Recipes awaiting your approval" Add unnecessary attributes to the html elements you're using so that you can check for an element with "id=recipe_1" or "data-for-the-sake-of-testing=1" I very much dislike both of

I can't use getMainContext() and getSubcontext($alias) in version 3 any more. What is the way to communicate between context in version 3. Are context traits the only way? # behat.yml default: suites: guest_features: paths: [ %paths.base%/features/web ] filters: { role: guest } contexts: [ GuestContext ] user_features: paths: [ %paths.base%/features/web ] filters: { role: member } contexts: [ MemberContext ] groupled_features: paths: [ %paths.base%/features/web ] filters: { role: grouplead} contexts: [ GroupleadContext ] admin_features: paths: [ %paths.base%/features/web ] filters: { role:

I am using Specflow in C# to build automatic client side browser testing with Selenium. The goal of these tests is to simulate the business scenario where a client enters our website in specific pages, and then he is directed to the right page. I Want to use parameters inside a Scenario Context, for example: When I visit url | base | page | parameter1 | parameter2 | | http://www.stackoverflow.com | questions | <questionNumber> | <questionName> | Then browser contains test <questionNumber> Examples: | <questionNumber> | <questionName> | | 123 | specflow-q1 | | 456 | specflow-q2 | | 789 |