Sha256: 34b179949f465a2f4663122268359aefcdb8ad7762bccc1356dbeaa92236c62a
Contents?: true
Size: 1.8 KB
Versions: 1
Compression:
Stored size: 1.8 KB
Contents
@customer Feature: Customer Logout Feature As a customer of the product I am able to logout Background: Given this undefined step definition @bvt Scenario: Customer that is logged in is able to log out Given that a customer is a valid customer And a customer logs in as username 'frank' with password 'default' And I expect them to have logged in successfully When the customer logs out Then I expect the customer to be shown the logout page Scenario: Customers with a complete profile are allowed to post Given that a customer is a valid customer And the customer has the following details: | Name | Email | Age | | Roger | r@email.com | 22 | And the customer has the following details: | Name | Email | Age | | Roger | r@email.com | 22 | When a customer logs in as username 'frank' with password 'default' And visits the customer update page Then I expect the customer is able able to post to their profile @optional_parameters Scenario: Optional Parameter Step Definition # This step definition has some optional parameters Given a project And an inactive project And a project with the name 'optional', start date 10/26/2010, nicknamed 'norman' @highlighting Scenario: Highlighting Given a duck that has a bill Then I expect the duck to quack @product Scenario Outline: Customers that bought a product are included in their product groups Given that <Customer> is a valid customer And that the product, named '<Product>', is a valid product When the customer has purchased the product Then I expect the customer to be a member of the '<Product>' group Examples: | Customer | Product | | Customer A | Product A | | Customer A | Product B | | Customer A | Product C |
Version data entries
1 entries across 1 versions & 1 rubygems
Version | Path |
---|---|
cucumber-in-the-yard-1.5.3 | example/second_example.feature |