Cucumber Tool
- 1. TOOL
- 2. CUCUMBER TOOL • Overview • How It Works • Environment • Gherkin • Feature • Feature File • Scenarios. • Annotation. • Advantages
- 3. OVER VIEW • Cucumber is a high level testing Framework which supports behavior driven development. o It runs automated acceptance testing on web applications. o It execute plain-text functional description as automated tests. o It understand Gherkin Language.
- 4. AUTOMATED TESTING • Automated testing is important due to following reasons: • Manual Testing of all work flows, all fields, all negative scenarios is time and cost consuming. • Automation does not require Human intervention. • Automation increases speed of test execution. • Automation helps increase Test Coverage. • Manual Testing can become boring and hence error prone.
- 5. BENEFITS OF AUTOMATION TESTING
- 6. HOW IT WORKS
- 7. HOW IT WORKS • Cucumber reads the code written in plain English text (Language Gherkin) in the feature file. • It finds the exact match of each step in the step definition (a code file). • The piece of code to be executed can be different software frameworks like Selenium, Ruby on Rails, etc.
- 8. ENVIRONMENT It has no specific setup but it give different libraries which can be used through • Java • Eclipse • Cucumber supports over a dozen different software platforms like − • Ruby on Rails • Selenium • Pico Container • Spring Framework • Watir
- 9. GHERKIN • Cucumber executes the test scripts, which have been defined in the feature file. • The language, in which this executable feature files is written, is known as Gherkin. • Gherkin is a plain English text language. • which helps the tool Cucumber • to interpret • execute the test scripts.
- 10. GHERKIN • Gherkin provides the common set of keywords in English text. • It can be used by people amongst the different community and yet get the same output in the form of test scripts
- 11. FEATURE • A Feature can be defined as a standalone unit or functionality of a project. • Few basic features can be determined as − • Create and remove the user from the social networking site. • User login functionality for the social networking site. • Sharing photos or videos on the social networking site. • Sending a friend request. • Logout. A feature usually contains a list of scenarios to be tested for that feature. •
- 12. FEATURE FILE • A simple feature file consists of the following keywords/parts − • Feature − Name of the feature under test. • Description (optional) − Describe about feature under test. • Scenario − What is the test scenario. • Given − Prerequisite before the test steps get executed. • When − Specific condition which should match in order to execute the next step. • Then − What should happen if the condition mentioned in WHEN is satisfied
- 13. SCENARIO • Scenario is one of the core Gherkin structures • Every scenario starts with the keyword “Scenario:” • Each feature can have one or more scenarios. • Every scenario consists of one or more steps. • One feature more scenario more steps A very simple example of scenario can be • Scenario − Verify Help Functionality.
- 14. ANNOTATION
- 16. ADVANTAGES OF CUCUMBER OVER OTHER TOOLS • Supports different languages like Java.net and Ruby. • Acts as a bridge between the business and technical language. • It allows the test script to be written without knowledge of any code. • It allows the involvement of non-programmers as well.