Cucumber 面接の質問と回答
質問 26. What is the purpose of the 'Dry Run' option in Cucumber?
The 'Dry Run' option is used to check if all the steps in the feature file have matching step definitions. It helps identify undefined or pending steps without executing the actual test.
Example:
cucumber --dry-run
質問 27. How can you handle dynamic data in Cucumber?
Dynamic data can be handled using Scenario Outline and Examples, allowing the same scenario to be executed with different sets of data.
Example:
Scenario Outline: Search with dynamic data
Given the user is on the search page
When the user searches for
Then results should include
Examples:
| dynamic_keyword | result |
| cucumber | relevant results |
| testing | accurate results |
質問 28. How do you handle browser-specific testing in Cucumber?
Browser-specific testing can be handled by using tags and configuring the test runner to run scenarios with specific tags. Different scenarios can be tagged for different browsers, and appropriate configuration can be set for each browser.
Example:
@chrome
Scenario: Test on Chrome browser
Given the user is on the application
When the user performs an action
Then the result should be validated
質問 29. What is the purpose of the 'Scenario Context' in Cucumber?
Scenario Context is used to share data between steps within the same scenario, allowing you to pass information between steps.
Example:
Scenario: Sharing data between steps
Given a variable is initialized
When the variable is modified
Then the modified value should be accessible in subsequent steps
質問 30. Explain the difference between Cucumber and JUnit/TestNG.
Cucumber is a BDD tool that allows tests to be written in a natural language style, whereas JUnit and TestNG are testing frameworks used for unit testing in a more traditional manner.
Example:
Feature: Login
Scenario: Successful login
Given the user is on the login page
When the user enters valid credentials
Then the user should be logged in
ユーザー評価で最も役立つ内容: