Q: What are the benefits of Automation Testing?

Benefits of Automation Testing Automation testing offers significant advantages over manual testing in speed, reliability, and scale. 1. Saves Time and Money Automated tests run in minutes what would take hours manually. Once created, they execute for free on every run. 2. Reusability of Code Write a test method once, reuse it across multiple test scenarios, environments, and data sets. java @Test(dataProvider = "loginData") public void loginTest(String user, String pass) { } // Reused with 100 data sets 3. Create Once, Execute Multiple Times Automation scripts can be run thousands of times with zero marginal cost — critical for regression suites. 4. Easy and Automatic Reporting TestNG, Extent Reports, and Allure generate detailed HTML/XML reports automatically aft

Q: Explain what is Group Test in TestNG.

Group Test in TestNG TestNG allows test methods to be categorized into groups using the groups attribute in @Test. When a group is executed, all methods belonging to that group run. Defining groups: java public class GroupTestExample { @Test(groups = { "sanity" }) public void loginByEmail() { System.out.println("this is login by email"); } @Test(groups = { "sanity" }) public void loginByFacebook() { System.out.println("this is login by facebook"); } @Test(groups = { "sanity", "regression" }) public void signupByEmail() { System.out.println("signup by email"); } @Test(groups = { "sanity", "regression" }) public void signupByFacebook() { System.out.println("signup by facebbok"); }

Q: What are the advantages of Selenium?

1. Free and open-source — no licensing cost 2. Supports multiple languages — Java, Python, C, Ruby 3. Supports multiple browsers — Chrome, Firefox, Edge 4. Large community and resources available online 5. Selenium IDE allows non-programmers to automate using record & playback 6. Selenium Grid enables distributed testing across remote machines

Q: What is the limit for the maximum number of scenarios in a Cucumber feature file?

Maximum Scenarios in a Feature File Technical Limit Cucumber has no enforced hard limit on the number of scenarios in a feature file. You can technically add hundreds of scenarios to a single file. Recommended Best Practice Keep feature files to a maximum of 10 scenarios. However, this number can vary from project to project and organization to organization. Why Limit Scenarios Per Feature File? 1. READABILITY - Files become hard to scan with 30+ scenarios - Difficult to find specific scenarios quickly 2. MAINTAINABILITY - One change in Background affects all scenarios - Large files have higher merge conflict risk 3. FOCUS - Each feature file should test ONE feature/module - Mixing multiple features in one file violates SRP 4. EXECUTION T

Q: What is meant by a feature file in Cucumber?

Feature File in Cucumber A feature file is the core component of Cucumber BDD testing. It contains test scenarios written in Gherkin language and acts as both executable test specification and living documentation. Properties of a Feature File - Extension: .feature - Location: src/test/resources/features/ - Written in plain English (Gherkin) - Contains one Feature and multiple Scenarios - Maximum recommended: 10 scenarios per feature file Structure of a Feature File gherkin Feature: User Registration As a new user I want to register on the website So that I can access premium features Background: Given the user is on the registration page Scenario: Register with valid details When the user enters name "John Doe" And the user enters em

Q: Your Selenium script works locally but fails in CI/CD. How do you fix it?

Script Works Locally but Fails in CI/CD — Diagnosis Guide This is one of the most common real-world Selenium problems. Work through these causes in order: Root Cause 1 — Missing Headless Mode CI servers have no display. You must run headless: java ChromeOptions options = new ChromeOptions(); options.addArguments("--headless=new"); options.addArguments("--no-sandbox"); // required in Docker/Linux options.addArguments("--disable-dev-shm-usage"); // prevents memory crashes options.addArguments("--disable-gpu"); options.addArguments("--window-size=1920,1080"); // headless has no screen size WebDriver driver = new ChromeDriver(options); Root Cause 2 — Timing / Waits CI machines are slower than your dev machine. Replace all Thread.sleep() with proper wai

Q: How do you handle shadow DOM elements in Selenium?

Handling Shadow DOM in Selenium Shadow DOM is an encapsulated DOM tree that hides internal implementation of web components. Standard findElement cannot cross the shadow boundary. Understand the Structure html <!-- Host element -- <custom-input id="myInput" <!-- Shadow DOM (not visible to standard XPath/CSS) -- shadow-root <input type="text" class="internal-input" </custom-input Method 1 — Selenium 4 getShadowRoot() (Native Support) java // Selenium 4.x has native shadow DOM support WebElement host = driver.findElement(By.cssSelector("custom-inputmyInput")); SearchContext shadowRoot = host.getShadowRoot(); // Now find element inside shadow DOM WebElement innerInput = shadowRoot.findElement(By.cssSelector("input.internal-input")); innerInput.sendKeys

Question 1

How to run failed test cases using TestNG in Selenium WebDriver?

Accepted Answer

Running Failed Test Cases Using TestNG After every TestNG test run, if any tests fail, TestNG automatically generates a testng-failed.xml file inside the test-output folder. This file contains only the failed tests. Location: test-output/testng-failed.xml Generated testng-failed.xml example: xml

Question 2

How do you run Selenium tests in parallel across multiple browsers?

Accepted Answer

Parallel Execution Across Multiple Browsers Method 1 — TestNG Parallel with Browser Parameter testng.xml: xml

Question 3

How do you test a rich text editor like TinyMCE or CKEditor in Selenium?

Accepted Answer

Testing Rich Text Editors (TinyMCE / CKEditor) in Selenium  Rich text editors render inside an <iframe with a contenteditable body. Standard sendKeys on the visible area does not work.   TinyMCE — Type Text via iframe  java // Switch to TinyMCE''s iframe driver.switchTo().frame(driver.findElement(By.cssSelector("tinymceifr")));  // Click the body and type WebElement body = driver.findElement(By.cssSelector("bodytinymce")); body.click(); body.sendKeys("Hello from Selenium! This is a test article.");  // Switch back to main page driver.switchTo().defaultContent();    TinyMCE — Set Content via JavaScript API  java // Faster and more reliable — use TinyMCE''s own API JavascriptExecutor js = (JavascriptExecutor) driver; js.executeScript(     "tinymce.get(0).setContent('

Question 4

What are the benefits of Automation Testing?

Accepted Answer

Benefits of Automation Testing  Automation testing offers significant advantages over manual testing in speed, reliability, and scale.  1. Saves Time and Money Automated tests run in minutes what would take hours manually. Once created, they execute for free on every run.  2. Reusability of Code Write a test method once, reuse it across multiple test scenarios, environments, and data sets. java @Test(dataProvider = "loginData") public void loginTest(String user, String pass) { }  // Reused with 100 data sets   3. Create Once, Execute Multiple Times Automation scripts can be run thousands of times with zero marginal cost — critical for regression suites.  4. Easy and Automatic Reporting TestNG, Extent Reports, and Allure generate detailed HTML/XML reports automatically aft

Question 5

Explain what is Group Test in TestNG.

Accepted Answer

Group Test in TestNG  TestNG allows test methods to be categorized into groups using the groups attribute in @Test. When a group is executed, all methods belonging to that group run.  Defining groups: java public class GroupTestExample {      @Test(groups = { "sanity" })     public void loginByEmail() {         System.out.println("this is login by email");     }      @Test(groups = { "sanity" })     public void loginByFacebook() {         System.out.println("this is login by facebook");     }      @Test(groups = { "sanity", "regression" })     public void signupByEmail() {         System.out.println("signup by email");     }      @Test(groups = { "sanity", "regression" })     public void signupByFacebook() {         System.out.println("signup by facebbok");     }

Question 6

What are the advantages of Selenium?

Accepted Answer

1. Free and open-source — no licensing cost 2. Supports multiple languages — Java, Python, C, Ruby 3. Supports multiple browsers — Chrome, Firefox, Edge 4. Large community and resources available online 5. Selenium IDE allows non-programmers to automate     using record & playback 6. Selenium Grid enables distributed testing across     remote machines

Question 7

What is the limit for the maximum number of scenarios in a Cucumber feature file?

Accepted Answer

Maximum Scenarios in a Feature File   Technical Limit Cucumber has no enforced hard limit on the number of scenarios in a feature file. You can technically add hundreds of scenarios to a single file.   Recommended Best Practice Keep feature files to a maximum of 10 scenarios. However, this number can vary from project to project and organization to organization.   Why Limit Scenarios Per Feature File?   1. READABILITY    - Files become hard to scan with 30+ scenarios    - Difficult to find specific scenarios quickly  2. MAINTAINABILITY    - One change in Background affects all scenarios    - Large files have higher merge conflict risk  3. FOCUS    - Each feature file should test ONE feature/module    - Mixing multiple features in one file violates SRP  4. EXECUTION T

Question 8

What is meant by a feature file in Cucumber?

Accepted Answer

Feature File in Cucumber  A feature file is the core component of Cucumber BDD testing. It contains test scenarios written in Gherkin language and acts as both executable test specification and living documentation.   Properties of a Feature File  - Extension: .feature - Location: src/test/resources/features/ - Written in plain English (Gherkin) - Contains one Feature and multiple Scenarios - Maximum recommended: 10 scenarios per feature file   Structure of a Feature File  gherkin Feature: User Registration   As a new user   I want to register on the website   So that I can access premium features    Background:     Given the user is on the registration page    Scenario: Register with valid details     When the user enters name "John Doe"     And the user enters em

Question 9

Your Selenium script works locally but fails in CI/CD. How do you fix it?

Accepted Answer

Script Works Locally but Fails in CI/CD — Diagnosis Guide  This is one of the most common real-world Selenium problems. Work through these causes in order:   Root Cause 1 — Missing Headless Mode  CI servers have no display. You must run headless:  java ChromeOptions options = new ChromeOptions(); options.addArguments("--headless=new"); options.addArguments("--no-sandbox");            // required in Docker/Linux options.addArguments("--disable-dev-shm-usage"); // prevents memory crashes options.addArguments("--disable-gpu"); options.addArguments("--window-size=1920,1080"); // headless has no screen size  WebDriver driver = new ChromeDriver(options);    Root Cause 2 — Timing / Waits  CI machines are slower than your dev machine. Replace all Thread.sleep() with proper wai

Question 10

How do you handle shadow DOM elements in Selenium?

Accepted Answer

Handling Shadow DOM in Selenium Shadow DOM is an encapsulated DOM tree that hides internal implementation of web components. Standard findElement cannot cross the shadow boundary. Understand the Structure html

Master QA Automation
Interviews

Browse by Topic

All Questions

Master QA Automation Interviews

Browse by Topic

All Questions

Master QA Automation
Interviews