Explore topic-wise InterviewSolutions in .

We can select the target scenario from a feature FILE by PROVIDING its line number.

CUCUMBER features/test.feature:10 --FORMAT html > testfeature.html

We can select the target scenario from a feature file by providing its line number.

cucumber features/test.feature:10 --format html > testfeature.html

We run the following command to produce HTML REPORTS.

CUCUMBER <featurename&GT;.feature --format html --out report.html --format PRETTY

We run the following command to produce HTML reports.

cucumber <featurename>.feature --format html --out report.html --format pretty

1. RSpec is more successful in doing UNIT testing.
2. As you know that CUCUMBER is a behaviour-driven development tool. So you can use it for SYSTEM and INTEGRATION testing.

Please note that it’s not mandatory to write keywords in test STEPS.

For example, we can build a test step LIKE the one shown in the next line.

e.g.- We are testing USING cucumber.

Please note that it’s not mandatory to write keywords in test steps.

For example, we can build a test step like the one shown in the next line.

e.g.- We are testing using cucumber.

However, the Cucumber and JBEHAVE SHARE the same perspective, but there are few KEY DIFFERENCES.

1. Jbehave is Java-based and Cucumber is Ruby-based.
2. Jbehave is story-driven WHEREAS the Cucumber is feature-driven.

However, the Cucumber and Jbehave share the same perspective, but there are few key differences.

We USE to compile the cucumber feature files and step DEFINITIONS. If there occur any COMPILATION ERRORS, then it shows them on the CONSOLE.

We use to compile the cucumber feature files and step definitions. If there occur any compilation errors, then it shows them on the console.

Cucumber tags help in filtering the scenarios. We can tag the scenarios and then run them based on tags.

1. We can add tags to scenarios with <@> symbol.
2. We can USE the following command to run a cucumber tagged scenario.

cucumber FEATURES -t @<tag_name>

EXAMPLE: cucumber features -t @test

Cucumber tags help in filtering the scenarios. We can tag the scenarios and then run them based on tags.

cucumber features -t @<tag_name>

Example: cucumber features -t @test

You can create Cucumber profiles to run a set of features and STEP definitions. Use the following COMMAND to execute a cucumber profile.

cucumber features -p <profile_name&GT;

#EXAMPLE: cucumber features -p acceptance

You can create Cucumber profiles to run a set of features and step definitions. Use the following command to execute a cucumber profile.

cucumber features -p <profile_name>

#Example: cucumber features -p acceptance

A feature file in CUCUMBER SPECIFIES parameters and CONDITIONS for EXECUTING the test code. It can combine any of the following.

1. A feature.
2. A user SCENARIO.
3. The scenario outline.
4. A <Given> clause.
5. A <When> clause.
6. A <Then> clause.

A feature file in cucumber specifies parameters and conditions for executing the test code. It can combine any of the following.

YES, there are a few we are listing down below. Though, we recommend building ONE of your own as it gives you more freedom.

1. Selenium-Cucumber framework for testing the web and android APPS.
2. ANOTHER one is an ACCEPTANCE testing framework using Cucumber and Selenium Webdriver.

Yes, there are a few we are listing down below. Though, we recommend building one of your own as it gives you more freedom.

1. It supports SAFARI browser VIA a third-party DRIVER. It is experimental and comes with limited functionality.
2. It provides an ANDROID driver to run TESTS on its native mobile browser.

1. It’s an open source, so you save a LOT on the cost SIDE.
2. It gives you options to choose from a list of programming languages. e.g. Java, Python, C-Sharp, Ruby, and Python.
3. It offers easy and powerful dom-level testing.
4. You can use it in either of AGILE or waterfall environment.
5. Easy integration with Jenkins, Bamboo, and some other notable CI TOOLS.

You might like to consider the following facts while creating a productive and scalable test FRAMEWORK.

1. Identify the type of application you are going to test. Is it a Web app, support MOBILE devices or runs on a desktop.
2. Would it require BACKEND testing? e.g. Databases or SDK.
3. Decide on the input format. Is it static or dynamic?
4. Do you need to test the app for internationalization?
5. It must have a report which can help you trace a FAILURE with minimum efforts.
6. It must support auto-generation of parametrization tests.
7. Have a config file to define any setup related settings or the global PROPERTIES.
8. Apply abstraction at every level to separate the functionality.

You might like to consider the following facts while creating a productive and scalable test framework.

1. You can use Selenium for the functional, regression, and load TESTING of the web-based applications.
2. You can employ this tool for doing the post-release VALIDATION.
3. Integrate it with the continuous INTEGRATION tools like Jenkins, Hudson, QuickBuild or CruiseControl.

The above two questions were a little basic which SOMETIMES we miss EXPLAINING during the interview. So, we thought it was worth starting with them.

The above two questions were a little basic which sometimes we miss explaining during the interview. So, we thought it was worth starting with them.

Following are the possible benefits of using a TEST FRAMEWORK.

1. It reduces the complexity of using a VARIETY of technologies inculcated in a product.
2. It organizes the unit and functional testing efforts of a DEVELOPER and tester.
3. Provides early feedback on the quality of the code.
4. Helps in tracking test coverage as well as code coverage.
5. Results in EASY debugging and reduces chances of errors.

Following are the possible benefits of using a test framework.

In general, a framework is an ENTITY which binds several modules in a LOGICAL sequence to cover the end-to-end flows of an application. The objective of INVESTING into a framework is to test a PRODUCT which has a RECURRING roadmap and regular release cycle.

In general, a framework is an entity which binds several modules in a logical sequence to cover the end-to-end flows of an application. The objective of investing into a framework is to test a product which has a recurring roadmap and regular release cycle.