Latest post from this blog

Test Scenarios vs. Test Cases: Understanding the Basics

By
What Are Test Scenarios Test scenarios represent high-level ideas or conditions that need to be validated to ensure the application works as expected. They provide a broader perspective and are typically used during the test planning phase. Purpose: To capture the "what to test" without going into granular details. Example of a Test Scenario: Verify that a user can successfully log in to the application using valid credentials. Verify the behavior of the login page when invalid credentials are entered. Verify the application behavior when the login button is clicked without entering any credentials. What Are Test Cases Test cases are detailed documents that define the specific steps to execute a test. They cover inputs, execution steps, expected results, and actual outcomes. Purpose: To guide the tester step-by-step on "how to test." Example of a Test Case (for the first scenario): Test Case ID TC_01_Login_Valid_Credentials Test Scenario Verify user login with val...
Post a Comment

Controlling Execution Order by Naming Feature Files Alphabetically in Cucumber Framework

By

Introduction

In the Cucumber framework, you can control the order of execution of your feature files by naming them in the sequence you want them to be executed. Cucumber executes feature files in alphabetical order by default. So, you can prefix your feature files with numbers or letters to control their execution order.

Consider the following three features in a basic application: Login, HomePage, and Registration.
Here’s how your feature files may look initially:

  • Login.feature
  • HomePage.feature
  • Registration.feature

By default, Cucumber might execute these in an unpredictable order. To control the execution sequence, you need to rename them alphabetically or numerically.

Rename Feature Files Alphabetically

For example, you can rename your feature files like this:

  • 1_Login.feature
  • 2_HomePage.feature
  • 3_Registration.feature

And, add the same tag (@Sanity) in each feature file:


In the TestNG runner class, you specify the tag @Sanity to run the tests.

Execution Flow

When you run the tests, Cucumber will:
  • Identify all the feature files that contain the @Sanity tag.
  • Execute them in alphabetical order based on their file names, even though all of them have the same tag.
Why It Works
When you specify a tag in the TestNG runner (@Sanity in this case), Cucumber looks for all the feature files that match this tag. It then executes those files in alphabetical order based on their file names, unless a custom order is specified (for example, in testng.xml or through a custom runner). By numbering or alphabetically naming the feature files, you ensure that Cucumber follows a specific execution sequence.

Conclusion
Controlling the execution order of feature files in Cucumber is often necessary to ensure a logical flow, especially in projects where one feature depends on the outcome of another. By naming the feature files alphabetically or numerically, you can achieve a defined execution sequence effortlessly. This approach is ideal for teams using JUnit or TestNG with Cucumber, as it requires no extra setup and works out of the box.

Comments

Post a Comment

Popular posts from this blog

Common Exception in Selenium

By
Introduction Selenium automation testing can throw several types of exceptions due to various issues during the execution of test scripts.  Here are some of the  most common exceptions  encountered in Selenium. 1. WebDriverException  is a base class for all exceptions thrown by the WebDriver API.  2. StaleElementReferenceException  is thrown when trying to interact with an element no longer attached to the DOM (Document Object Model).  This can happen if the element has been deleted or the page has been refreshed since the element was located. "stale" is often used to refer to something that is no longer fresh or current. 3. TimeoutException  is thrown when a command times out. This can occur if the page takes too long to load or if an element is not found within the specified time period. 4. UnreachableBrowserException  is thrown when a connection to a web browser cannot be established. 5. NoSuchElementException  is thrown when it canno...
Read more»

Test Scenarios vs. Test Cases: Understanding the Basics

By
What Are Test Scenarios Test scenarios represent high-level ideas or conditions that need to be validated to ensure the application works as expected. They provide a broader perspective and are typically used during the test planning phase. Purpose: To capture the "what to test" without going into granular details. Example of a Test Scenario: Verify that a user can successfully log in to the application using valid credentials. Verify the behavior of the login page when invalid credentials are entered. Verify the application behavior when the login button is clicked without entering any credentials. What Are Test Cases Test cases are detailed documents that define the specific steps to execute a test. They cover inputs, execution steps, expected results, and actual outcomes. Purpose: To guide the tester step-by-step on "how to test." Example of a Test Case (for the first scenario): Test Case ID TC_01_Login_Valid_Credentials Test Scenario Verify user login with val...
Read more»

Handling Shadow DOM in Selenium WebDriver

By
Image
Introduction Modern web applications often use Shadow DOM to keep parts of the webpage separate from the rest of the document. This helps in creating reusable components, but it also makes it difficult for Selenium WebDriver to access elements inside the Shadow DOM. In this blog, we'll explore what Shadow DOM is, why it's used, and how to handle it in Selenium WebDriver. What is Shadow DOM The Shadow DOM is a way to create a separate, hidden section of the DOM inside a web page. It's like a mini DOM tree attached to an element, which keeps its structure and styles isolated from the rest of the page. This helps developers build reusable web components without worrying about outside styles or scripts affecting them. Challenges in Handling Shadow DOM with Selenium WebDriver Selenium WebDriver typically interacts with the visible DOM. However, elements inside a Shadow DOM are not directly accessible through standard methods like driver.findElement() . This leads to exceptions ...
Read more»

Handling HTTPS Websites and SSL Certificate Errors in Selenium

By
Why SSL Certificate Errors Occur   SSL certificates ensure secure communication between the server and browser. If there's an issue, like an untrusted or expired certificate, the browser shows a warning. In automation, these warnings can interrupt tests, causing them to fail unless managed properly.In this post, we'll explain how to handle SSL certificate errors in Selenium for Chrome, Firefox, and Edge to ensure your tests run smoothly. setAcceptInsecureCerts(true) option allows the browser to ignore SSL certificate errors, enabling Selenium tests to run smoothly on sites with untrusted or invalid certificates. Handling SSL Certificate Errors in Chrome You can configure Chrome to accept insecure certificates by passing the option in ChromeOptions. ChromeOptions.setAcceptInsecureCerts(true)  allows Chrome to skip SSL warnings and continue testing on sites with untrusted certificates.its similar to the Firefox and Edge Browser also. import org.openqa.selenium.WebDriver; import...
Read more»

Normalize-space Function In Xpath

By
Introduction   When working with XPath, handling whitespace in text nodes can sometimes be a challenge. The normalize-space() function is a powerful tool to simplify text processing by removing unnecessary spaces and ensuring consistent string formatting. In this blog, we’ll explore what normalize-space() does, its syntax, and practical use cases in automation. What is the normalize-space() Function: The normalize-space() function in XPath trims leading and trailing whitespaces and reduces multiple spaces between words to a single space. It is useful for matching text nodes with inconsistent whitespace formatting. Syntax: normalize-space(string) string: The input text to be normalized. If omitted, it defaults to the current node’s text. Key Features: Removes leading and trailing spaces. Converts multiple spaces between words into a single space. Works seamlessly with text nodes and string attributes. Example :  <div id="example">   Hello World. </d...
Read more»