QA

Explain the purpose of the keywords that are used for writing a scenario in Cucumber.

"Given" keyword is used to specify a precondition for the scenario. "When" keyword is used to specify an operation to be performed. "Then" keyword is used to specify the expected result of a performed action. "And" keyword is used to join one or more statements together into a single statement.

What are the advantages of using Cucumber?

-Cucumber supports a variety of programming languages, including Java.net and Ruby. -It serves as a link between commercial and technical language. This can be done by writing a test case in plain English text. -It enables the test script to be developed without any prior knowledge of programming, as well as the participation of non-programmers. -Unlike other tools, it functions as an end-to-end test framework. -Cucumber allows for code reuse thanks to its simple test script architecture.

What are some of the prerequisites that you should consider while building a Selenium Cucumber automation application?

-Determine the type of application you'll be testing. Is it a Web app, a mobile app, or a desktop application? -Is there a need for backend testing? Databases or SDKs, for example. -Is it necessary to run the app through an internationalization test? -It must include a report that allows you to track down a problem with minimal effort. -It must be able to generate parametrization tests automatically. -Any setup-related settings or global attributes should be defined in a config file. -To segregate the functionality, use abstraction at every level.

What are the primary keywords in Cucumber?

-Feature: The Feature keyword's aim is to collect relevant scenarios and provide a high-level description of a software feature. -Rule: The Rule keyword is used to express a single business rule that should be followed. It adds to the information about a feature. -Example: This is a practical illustration of a business rule. It comprises a series of steps. -Given: The given steps are used to describe the system's initial context - the scenario's scene. It usually refers to an event that occurred in the past. -When: When describing an occurrence or an action, When is employed. It could be a user interacting with the system or an event generated by another system. -Then: Then steps are employed to indicate an anticipated outcome, or result. -Background: A background helps you to give the situations that follow it some context. It can have one or more Given steps, which are executed prior to each scenario but after any Before hooks.

The six step process with TDD

-First, all the test cases are written. Based on your requirements, you must create an automated test case. -Carry out all of the tests: Carry out these automated test cases on the code that has been developed so far. -Modify the code for that test case: You must develop the code to make that test casework as intended if it fails throughout this step. -Rerun the test cases: Now you must rerun the test cases to ensure that all of the previously developed test cases have been implemented. -Modularize your code as follows: This is a step that can be skipped. However, refactoring your code to make it more readable and reusable is recommended. That is why it is necessary. -For new test scenarios, repeat steps 1-5: This is the final phase in the process. You must now repeat the process for the remaining test cases till all of them have been implemented.

Q #31) What is the maximum number of steps that are to be written within a scenario?

Answer: 3-4 steps.

How do you comment the code in Cucumber? What is the importance of comments?

A comment is a chunk of code that is intended for documentation rather than execution. To make it more legible and clear, whether it's a step definition file or a feature file. As a result, it's critical to use/insert comments in the right places throughout the file. This is also beneficial for troubleshooting the code. Comments can be added to Cucumber feature files at any time. To add comments, simply begin the statement with the "#" sign.Different programming languages have different standards for commenting. Let's see how Cucumber handles the situation: For Step Definition File, if you're using Java as a platform, start your comments with "/." In the case of a feature file, we only need to type # before starting our comment.

In a feature file, what is the maximum number of scenarios?

A feature file in Cucumber can include a maximum of 10 scenarios. This quantity can differ from one project to the next and from one organization to the next. It's advisable to keep the number of scenarios in the feature file to a minimum.

Q #12) What is the limit for the maximum number of scenarios that can be included in the feature file?

Answer: A feature file can contain a maximum of 10 scenarios, but the number can vary from project to project and from one organization to another. But it is generally advisable to limit the number of scenarios included in the feature file.

What do you mean by feature in Cucumber

A project's feature can be described as a stand-alone unit or functionality. A list of scenarios to test for a feature is frequently included with it. The Feature File is a file in which we store features, descriptions of features, and situations to be evaluated. For each feature under test, it is recommended that a separate feature file be created. The feature file must have the extension ".feature." You can make as many feature files as you want. For an e-commerce website, we can have the following features:- User registers and signs up on the website. User tries to log in to their account using their credentials. Users add a product to their cart. User clicks on checkout now. User pays for their items. User logs out from the website. -all will have a separate feature file

What are annotations in Cucumber?

An annotation is a type of text that has been pre-defined and has a specified meaning. It tells the compiler/interpreter what to do when the program runs. The annotations on Cucumber are as follows: Given: It specifies the requirements for running the test.Example: Given I have an account on Interviewbit. When: It establishes the starting point for any test scenario.Example: When I log in to Interviewbit. Then: It contains the expected result of the test which is to be executed.Example: Then registration should be successful. And: Between any two statements, it gives the logical AND condition. AND can be combined with the GIVEN, WHEN, and THEN statements.Example: When I enter my account number AND CVV. But: It denotes a logical OR relationship between two propositions. OR can be combined with the GIVEN, WHEN, and THEN statements.Example: Then I should be logged in BUT I must enter the OTP.

Q #15) What is the purpose of Examples keyword in Cucumber?

Ans: Examples keyword is used to specify values for each parameter used in the scenario. Scenario Outline keyword must always be followed by the keyword Examples.

What is meant by a feature file?

Answer: A feature file must provide a high-level description of an Application Under Test (AUT). The first line of the feature file must start with the keyword 'Feature' followed by the description of the application under test. A feature file may include multiple scenarios within the same file. A feature file has the extension .feature.

Q #7) What is the purpose of the Step Definition file in Cucumber?

Answer: A step definition file in Cucumber is used to segregate the feature files from the underlying code. Each step of the feature file can be mapped to a corresponding method on the Step Definition file. While feature files are written in an easily understandable language like, Gherkin, Step Definition files are written in programming languages such as Java, .Net, Ruby, etc.

Q #11) What is the purpose of the Behaviour Driven Development (BDD) methodology in the real world?

Answer: BDD is a methodology to understand the functionality of an application in the simple plain text representation. The main aim of the Behavior Driven Development framework is to make various project roles such as Business Analysts, Quality Assurance, Developers, Support Teams understand the application without diving deep into the technical aspects.

Q #13) What is the use of Background keyword in Cucumber?

Answer: Background keyword is used to group multiple given statements into a single group. This is generally used when the same set of given statements are repeated in each scenario of the feature file.

Q #18) What is the purpose of the Cucumber Options tag?

Answer: Cucumber Options tag is used to provide a link between the feature files and step definition files. Each step of the feature file is mapped to a corresponding method on the step definition file. @CucumberOptions(features="Features",glue={"StepDefinition"})

How can Cucumber be integrated with Selenium WebDriver?

Answer: Cucumber can be integrated with the Selenium Webdriver by downloading the necessary JAR files.

Q #6) What programming language is used by Cucumber?

Answer: Cucumber tool provides support for multiple programming languages such as Java, .Net, Ruby etc. It can also be integrated with multiple tools such as Selenium, Capybara, etc.

Q #29) What is the use of features property under the Cucumber Options tag?

Answer: Features property is used to let the Cucumber framework identify the location of the feature files.

What language is used by Cucumber?

Answer: Gherkin is the language that is used by the Cucumber tool. It is a simple English representation of the application behavior. Gherkin language uses several keywords to describe the behavior of applications such as Feature, Scenario, Scenario Outline, Given, When, Then, etc.

Q #30) What is the use of glue property under the Cucumber Options tag?

Answer: Glue property is used to let the Cucumber framework identify the location of step definition files.

Q #28) Should any code be written within the TestRunner class?

Answer: No code should be written under the TestRunner class. It should include the tags @RunWith and @CucumberOptions.

Q #14) What symbol is used for parameterization in Cucumber?

Answer: Pipe symbol (|) is used to specify one or more parameter values in a feature file.

What is the purpose of a Scenario Outline in Cucumber?

Answer: Scenario outline is a way of parameterization of scenarios. This is ideally used when the same scenario needs to be executed for multiple sets of data, however, the test steps remain the same. Scenario Outline must be followed by the keyword 'Examples', which specify the set of values for each parameter.

Q #25) What is the meaning of the TestRunner class in Cucumber?

Answer: TestRunner class is used to provide the link between the feature file and the step definition file. The next question provides a sample representation of how the TestRunner class will look like. A TestRunner class is generally an empty class with no class definition.

Q #27) What is the starting point of execution for feature files?

Answer: When integrated with Selenium, the starting point of execution must be from the TestRunner class.

Provide an example of Background keyword in Cucumber.

Background: Given the user is on the application login page.

Explain briefly how Behavioral Driven Development works?

Behaviour Description: We list down the features of our application first in the feature file. Making the Step Definition file: The mapping between each step of the scenario defined in the feature file and a code of the function to be executed is stored in the steps definition file. Testing and running: We run the test cases to check if we pass. In general, a lot of failures are observed before achieving the final code. -------------------------------------------------------Behavior-driven development revolves around conducting behavior-specific tests, or functional specifications that outline executable scenarios for the application. This includes: Applying the 5 Whys principle or the if-then scenario to generate user stories and clearly relate application features to a business purpose.

What is the principle of Behaviour Driven Development?

Behaviour Driven Development (BDD) is a synthesis and refinement of practices stemming from Test Driven Development (TDD) and Acceptance Test-Driven Development (ATDD). BDD augments TDD and ATDD byapplying the "Five Why's" principle to each proposed user story so that its purpose is clearly related to business outcomes. Five Why's is an iterative interrogative approach for uncovering the cause-and-effect links at the root of a problem. The main purpose of this technique is to uncover the core cause of a flaw or problem by asking "Why?" repeatedly. Each response serves as the foundation for the next question.

What is the file extension for a feature file?

File Extension for a feature file is .feature. A feature file is ideally written in a notepad file and is saved with the extension feature.

What do you mean by Scenario Outline?

Consider the situation when we need to run a test scenario multiple times. Assume we need to ensure that the login feature is functional for all types of subscribers. This necessitates repeating the login functionality scenario. Gherkin adds another framework, the scenario outline, to help with this. The scenario outline is similar to scenario, with the exception that several inputs are provided. Scenario Outline - Sign In Feature for a website. Explanation: The website can have multiple users and so we need to consider all the users while implementing the sign-in functionality.

Why do we need to use Cucumber with Selenium?

Cucumber and Selenium are two widely used testing frameworks and technologies. Selenium is widely used for functional testing in many organizations. These companies use Cucumber in conjunction with Selenium because Cucumber makes the application flow easier to read and comprehend. The most important advantage of combining Cucumber and Selenium is that it allows developers to build test cases in simple feature files that managers, non-technical stakeholders, and business analysts can understand. It allows you to develop tests in Gherkin, a human-readable programming language. Java,.NET, PHP, Python, Perl, and other programming languages are supported by the Selenium-Cucumber framework.

How does the execution start in Cucumber?

Cucumber execution will begin at the support level. In support, it will first load the env.rb file, then hooks.rb, and last start executing feature file scenario steps.

What is Cucumber? Explain the need of using Cucumber.

Cucumber is a behavior-driven development (BDD) testing tool. -The BDD framework's major goal is to bring together a variety of project responsibilities, such as quality assurance, developers, and business analysts, to understand the application without diving too deeply into the technical components. -Testers use Cucumber to create test cases for evaluating program behaviour. It is an important tool to automate acceptance tests written in logical language that customers can understand. -It's primarily used to develop acceptance tests for web apps based on their features' behaviour.

Explain Cucumber shortly.

Cucumber is a tool that is based on Behavior Driven Development (BDD) methodology. The main aim of the Behavior Driven Development framework is to make various project roles such as Business Analysts, Quality Assurance, Developers, etc., understand the application without diving deep into the technical aspects.

Q #8) What are the major advantages of the Cucumber framework?

Cucumber is an open-source tool. Plain Text representation makes it easier for non-technical users to understand the scenarios. It bridges the communication gap between various project stakeholders such as Business Analysts, Developers, and Quality Assurance personnel. Automation test cases developed using the Cucumber tool are easier to maintain and understand as well. Easy to integrate with other tools such as Selenium and Capybara.

What is grouping in the context of Cucumber?

Cucumber is unconcerned about the names of your step definition files or the order in which you place them. Instead of maintaining all steps in a single file, we can create steps.rb file for each major action/feature. This is referred to as grouping.

What programming languages are used by Cucumber?

Cucumber supports a variety of programming languages, including Java,.NET, Ruby, and others. It can also be used with other tools like Capybara and Selenium.

When is Cucumber used in real-time?

Cucumber tool is generally used in real-time to write acceptance tests for an application. It is generally used by non-technical people such as Business Analysts, Functional Testers, etc.

Which language is used in Cucumber?

Cucumber understands Gherkin. It's a straightforward English representation of the app's functionality. It is used for defining test cases. It is intended to be non-technical and human-readable, and it describes use cases for a software system as a whole. It's a domain-specific (DSL), business-friendly language.

List the files needed in the Cucumber framework.

Feature File: It has plain text descriptions of single or numerous test situations. Keywords like Then, When, Background, Scenario Outline, Feature, And, But, and so on are used in the tests. As a result, it's a file that keeps track of features and their descriptions. Step Definition File: It has the extension .java. It essentially acts as a translator between the test scenario steps provided in the feature file and the automation code. Cucumber searches the step definition file and executes the relevant functions that are assigned to that step when it runs a step described in the feature file. TestRunner: .java is the file extension for this file. It connects the feature file and the step definition file. It allows the user to run one or more feature files at the same time. It contains the locations of the step definition and feature files.

What is Gherkin Language?

Gherkin is a readable business language that allows you to define business activity without getting bogged down in implementation specifics. It's a domain-specific language for defining specs tests in Cucumber format. It describes use cases in plain English and helps users to remove logic elements from behaviour testing.

Q #4) What are the various keywords that are used in Cucumber for writing a scenario?

Given When Then And

What are hooks in Cucumber?

Hooks are code blocks that execute before or after each Cucumber scenario in the execution cycle. This enables us to better control the development workflow and decrease code redundancy. Setting up the web driver and terminating the web driver session resembles a test setup. When dealing with different scenarios, it's best to do the setup and clean up only once. Hooks are used to bringing optimization. Certain preconditions, such as executing the program, creating a database connection, preparing the test data, and so on, may be required in some cases. There are also several postconditions to be fulfilled, such as ending the database connection, closing the browser, refreshing test data, and logging out of the program. Cucumber handles all of these situations with the use of hooks. The methods @Before and @After can be used to define hooks anywhere in the project or step definition layers. Before hook is executed before any other test situations, and after the hook is executed after all test scenarios have been completed.

Difference between Selenium and Cucumber.

Open-source testing tools, Selenium and Cucumber are both used for functional testing but... -Cucumber is a behavior-driven development automation tool that may be used with Selenium. Selenium is a web browser automation tool for web projects (or Appium). -Cucumber is used for acceptance testing, while Selenium is used for automated UI testing. Technical teams (SDETs/programmers) favour Selenium, while non-technical teams often choose Cucumber (business stakeholders and testers). -Cucumber isn't required for Selenium to work. Cucumber's step-definition implementation is based on Selenium or Appium. -The script creation with Selenium is complicated, whereas Cucumber is straightforward.

What is the difference between scenarios and scenario outlines

Scenario Outline is simply a scenario with a set of examples. Whenever you need to use the Examples section, you need to use the Scenario Outline instead of a Scenario. The difference is that a Scenario will be executed once while Scenario Outline is executed for each example from the table.

What do you mean by scenario in Cucumber Testing?

Scenario is a fundamental Gherkin structure. Every scenario begins with the keyword "Scenario:" (or a localized version of it) and ends with a scenario title. Every feature can have one or more scenarios, each of which has one or more steps. As an example of a scenario, consider the following: Scenario − Verify My Orders Functionality. Explanation: When a user clicks on the My Orders option he/ she should be taken to the My Orders page.

What are Step Definitions in the context of Cucumber?

Step definitions connect Gherkin steps to programming code. The mapping between each step of the scenario defined in the feature file and a code of the function to be executed is stored in the steps definition file. A step definition carries out the action that should be performed by the step. So step definitions hard-wire the specification to the implementation.

What do you mean by Test Driven Development (TDD)?

TDD is an abbreviation that stands for Test-Driven Development. This is a development practice in which the test cases are created first, followed by the code that underpins the test cases. TDD may also be used to construct automation testing. TDD takes longer to develop due to the fact that it finds fewer flaws. The TDD development practice has increased the quality of code, which is more reusable and flexible as a result. TDD also aids developers in achieving high test coverage, ranging from 90% to 100%. The sole disadvantage of TDD for developers is that they must build test cases before producing code.

How can you run Cucumber tests parallelly?

The Cucumber JVM Parallel Plugin, which may be used with Serenity BDD, can be used to conduct parallel tests in Cucumber. The plugin will look in the src/test/resources directory for feature files. After that, it will create runners for each file.

What is the use of the Options tag in the Cucumber Framework?

The Options tag is a part of the TestRunner file in the Cucumber framework, and it takes the form of an annotation named @CucumberOptions. It has two parameters: glue and feature: Feature: The path to the feature file is specified by the feature option. Glue: The glue argument is used to provide the step definition file's location.

What is Cucumber Dry Run?

The purpose of the Cucumber dry run is to verify compilation faults and compile the Step Definition and Feature files. Dry run's value might be either true or false. Dry run has the value false by default and it is present in the Test Runner Class file. If the dry run value is true, Cucumber will check all steps in the Feature file. Within the Step Definition file, it will also check the implementation code of steps in the Feature file. If any of the steps in the Feature file is missing its implementation in the Step Definition file, a message is thrown. The @CucumberOptions has a dry run parameter that is used to configure the test parameters.

What are the basic requirements to run Cucumber Web test cases?

We need the following minimum requirements to successfully run a Cucumber Web test case:- 1.The compiler and the development kit for the programming language we will be using. Example: JDK and JRE for using Java as our programming language. 2.An IDE (Integrated Development Environment) wherein we can write our code. 3. Build tools so as to do tasks such as compiling code, packaging code to a jar, creating source code. Example: Maven, Gradle.

What do you mean by profile in Cucumber?

When testing a feature, cucumber profiles make it simple to define groupings of tests in a feature file so that we can choose to execute only a subset of them rather than all of them. It was created to help people save time. In a cucumber.yml file, the user can reuse commonly used cucumber flags.

What are tags in Cucumber and why are they important?

When we only have one, two, or maybe five situations in a feature file, it appears to be simple. In reality, however, this does not occur. In a single feature file, we may have 10, 20, or even more scenarios for each feature under test. They could reflect various purposes (smoke test/regression test), perspectives (developer/QA/BA), and statuses (ready for execution/work in progress). Tags in cucumber provide a way to run scenarios in a specific sequence from a runner file. Each situation can be labeled with a useful tag. Later, in the runner file, we may specify which tag (and hence which scenario(s)) Cucumber should run. "@" is the first character in a tag. Any relevant content after "@" can be used to define your tag .Example - '@InitialTest'