- Welcome to Pcloudy!
- Existing Users
- Mobile Testing
- Getting Started
- Live Testing - Mobile
- Setting up Google Pay on Android Devices
- Uploading Apps & Installation
- App Activation for Readiness
- Reports & Analytics
- Test Management & Logging
- Debugging Apps
- Local Testing
- Additional Features
- Testing Apple Pay on iOS Devices
- Device Planner
- Accessibility Testing
- Enabling iOS Settings
- Android Image Injection
- iOS Image Injection
- OCR Testing
- Appium
- XCTest
- Espresso
- Automation Studio
- DevOps
- Web Testing
- Mobile Testing
- New Users to Pcloudy Unified Platform
- Pcloudy Unified Documentation
- Quality Lifecycle Management - QLM
- Analyzing Test Runs on QLM
- Introduction to My Space
- Creating and Managing Tickets in QLM
- Creation and Execution of Automated Test Runs
- Understanding Test Runs Dashboard in QLM
- Creating Manual Test Case in QLM
- Creating and Managing Test Suites in QLM
- Creating a Release & Adding Milestones in QLM
- Creating User Story in QLM
- No-Code Test Automation
- Opkey License Request & Upload
- Opkey Execution Agent Installation
- Using Mobile Recorder to Create a Test Case for Mobile Application
- Creating Automated Test Case in QLM
- Creating and Calling a Reusable component in Test Case
- Creating Reusable Component Using Keywords
- Creating a Local Data Repository in a Test Case
- Creating a Global Data Repository and Adding Encryption
- Working with Global Variables
- Creating SOAP API Test in Automate
- Creating REST API Test in pCloudy
- Schedule a Test Suite
- Quality Lifecycle Management - QLM
- Existing Users
- AI Tools
- App Performance Testing
- Cloud Administration
- API Documentation
- Integrations
- Release Note
- Release Note 5.7
- Release Note 5.8
- Release Note 5.9
- Release Note 6.0
- Release Note 6.1
- Release Note 6.2
- Release Note 6.3
- Release Note 6.4
- Release Note 6.5
- Release Note 6.6
- Release Note 6.7
- Release Note 6.8
- Release Note 6.9
- Release Note 6.10
- Release Note 6.11
- Release Note 6.12
- Release Note 6.14
- Release Note 6.13
- Release Note 7.0
- Release Note 7.1
- FAQs
Creating a Local Data Repository in a Test Case
Local Data Repository (LDR) is akin to a spreadsheet that contains various data sets, allowing you to run iterations of specific test steps with different data values within a test case.
For instance, consider a scenario where you're testing a sign-up feature of a website. The LDR can hold different datasets such as varying email addresses, passwords, and user details, enabling the test case to simulate sign-up attempts with diverse input combinations.
This repository provides flexibility through features like adding new datasets, modifying rows or columns, and importing/exporting data from Excel. When you integrate a local data repository into a test case, the associated test step(s) iterate based on the corresponding DataRow in the LDR.
Steps
Hover over the Automate section and click Test. Open the test case where you want to create and use your local data repository.
In a test case, by default, Global Data Repository mode is selected. Click on the dropdown present on the automated test case to change the mode of the data to Local Data Repository.
In the icon next to the dropdown, you can create Local Data Repository. A new page opens up on the right pane where you get the option of adding a new LDR.
Open the datasheet and click Enable Editing option to unlock the datasheet.
The number of columns in the Local Data Repository is equal to the number of test steps in the Test Case.
You can add either a single or multiple Datasets divided into rows and columns in your LDR. The number of datasets in the Local Data Repository defines the number of iterations a step will go through.
After entering the relevant data in the LDR, click the Save button at the top to save the inputs.
Click on the Run button to execute the test case.
The Run Wizard will open up on the right pane. Enter details like Run Name and Milestone and select the browser.
Under ‘Advance Setting’, select the build, agent, and plugin. Click Start Run.
Once the execution is complete, you can view the result by clicking on View Result.
During the execution, the data gets picked up from the datasheet. On clicking the ‘View Result’ button, you can view the details of the executed test case.