Скачать или смотреть Utilizing the Same Steps for Web and Mobile Tests with Cucumber and WebdriverIO

Learn how to efficiently use Cucumber steps for both mobile and web tests using WebdriverIO in a single feature file. Discover a strategic way to streamline your automation testing.
---
This video is based on the question https://stackoverflow.com/q/73230546/ asked by the user 'Wicky' ( https://stackoverflow.com/u/8267843/ ) and on the answer https://stackoverflow.com/a/73248946/ provided by the user 'M.P. Korstanje' ( https://stackoverflow.com/u/3945473/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to use same cucumber steps for both mobile and web tests when testing the same functionality?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Streamlining Automation Testing: Using Same Steps for Mobile and Web with Cucumber

Automation testing is paramount in the development of web applications and mobile apps alike. Using the same functionalities, while adjusting for the differences in navigation and implementation, is a challenge that many developers face. This guide dives into how you can efficiently utilize the same Cucumber steps for both mobile and web tests within a hybrid framework.

The Problem

Let’s say you’ve developed a web application as well as a mobile app using React Native. You might find that you need to write similar test scenarios in separate feature files for both platforms. For instance, you might have a feature file for testing member details on the mobile application and a separate one for the web app.

The dilemma arises when you want to consolidate these tests into a single feature while maintaining clear, understandable, and maintainable code. If you attempted to use a single feature with multiple tags like -web and -mobile, it may lead to convoluted control structures within your step definitions, making your code complex and hard to manage. Here’s the scenario you might face in your setup:

[[See Video to Reveal this Text or Code Snippet]]

The Solution: Using a Unified Home Page Interface

To simplify your test implementation while leveraging Cucumber effectively, consider using a unified class for your HomePage functionality that adapts to both mobile and web implementations. Here’s how to approach it step-by-step:

Step 1: Create a Unified HomePage Class

Instead of defining separate classes for mobileHomePage and webHomePage, create a single homePage object. During instantiation, check which kind of driver you are using (mobile or web) to determine which specific page implementation to utilize:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Use Unified Steps in Cucumber Feature Files

Now you can write your Cucumber steps to handle both scenarios without needing to create separate logic for each environment, simplifying your feature file:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Implement Unified Step Definitions

Your step definitions will also be simplified because you check the type of the homePage just once. Here’s how you would set it up:

[[See Video to Reveal this Text or Code Snippet]]

Step 4: Implement Consistent Interfaces

To make this solution work, ensure that both the MobileHomePage and WebHomePage classes implement the same interface or extend a common base class. This guarantees that methods like openHomePage() and isPageDisplayed() exist for both types of pages.

Conclusion

By using a unified interface for your page classes, you can drastically reduce the complexity of your step definitions and the number of conditional checks in your test scenarios. This not only makes your code cleaner but also enhances maintainability. In a continuously evolving codebase, this methodology can save you time and reduce the potential for errors as you develop and execute automated test cases across different platforms.

Implementing such a strategy will allow you to maximize efficiency and streamline your testing process, ensuring that both web and mobile platforms are effectively covered without compromising on clarity or maintainability. Happy testing!