Reusable framework structure for testing a functionality across multiple webpages

Help Studio
1

Hi All, I am new to UiPath. I need help in creating the framework structure. I have 3 websites available on different test environments(test,uat,prod). So total 9 urls with same functionality only data would be different. I want to create a reusable structure so that single testcase for each functionality(Login, Search etc.) with different data can be executed for each 9 website urls. Is it possible, or i need to create different test cases for different websites? If yes, could i get some idea/pointers on how to structure the framework for this? Also, While executing i should be able to select which test environment i need to run the testcase or which browser. I dont want to run test cases on all 9 webpages everytime.
Thanks in advance.
Riya

2

@RiyaK

When creating your test cases make sure you add the url as an asset or argument so that you can pass it into test case rather than hardcoding it in process…that way all urls can be changed

And environment depends on which env the robot is connected to …it would wrk on it

Hope this clarifies

Cheers

3

Hi @RiyaK,

Creating a reusable automation framework for your scenario in UiPath is certainly possible. To achieve this, you can follow a data-driven approach and design your framework with flexibility in mind. Here are some pointers on how to structure your framework:

  1. Data-Driven Approach: Use data tables or Excel files to store the URLs for the three different test environments (test, uat, prod) and their corresponding data. This will allow you to easily switch between environments and data sets.

  2. Test Cases: Create generic test cases for each functionality (Login, Search, etc.), keeping the functionality separate from the data. Parameterize your test cases to accept inputs, such as URLs and data.

  3. Configurations: Create a configuration file that specifies the environment (test, uat, prod) and browser choice. You can read this configuration at runtime to determine where and how the test case should be executed.

  4. Test Execution: Implement logic that allows you to select the test environment and browser before running a test case. This can be done using input arguments or by reading the configuration file.

  5. Reusability: Ensure that your test cases are designed to be generic and reusable. They should be capable of working with different data sets and environments without modification.

  6. Error Handling: Implement error-handling mechanisms to gracefully handle exceptions and provide informative error messages or logs.

  7. Reporting: Include a reporting mechanism to track the execution results for each combination of environment and browser.

  8. Test Data Management: Use UiPath’s capabilities to manage and manipulate test data efficiently. Consider using Orchestrator queues or other data storage solutions to manage your test data.

  9. Version Control: Implement version control for your automation project to manage changes and updates effectively.

By following this approach and structuring your UiPath framework as described, you can create a flexible and reusable solution that allows you to run your test cases on different websites with different data and under different test environments and browsers as needed.