- Elements (Objects)
- Web Applications
Record Single Element
Record Multiple Elements
Create Elements
Supported Locator Types
Formulating Elements
Shadow DOM Elements
Verifying elements in Chrome DevTools
Handling iframe Elements?
Create Image Based Elements
Dynamic Locators using Parameter
Dynamic Locators using Runtime
Using Environment Test Data for Dynamic Locators
Locating Dynamic Elements in Date Widget
Freeze & Inspect Dynamic Elements (WebPage)
Locating Dynamic Elements in Tables
Import/Export Elements
Locator Precedence (Web Apps)
Verify Elements from Test Recorder
Overview of Elements for an iOS Project
Element in an iOS project in Testsigma refers to an object that forms a part of the application's UI and can be located or identified. This article discusses an overview of elements for an iOS project.
Ways to Create Elements
There are 2 different ways to create elements in Testsigma:
- Manual Creation: Here, you manually give the details of the element to create them. For more information on creating elements manually, refer to the documentation on creating elements manually.
- Using Test Recorder: Here, you access your application’s UI using test recorder and inspect the elements that you want to capture. For more information on capturing elements using test recorder, refer to the documentation on capturing elements using test recorder.
Supported Locator Types
When creating elements for an application, you need to provide a way to identify them uniquely. Testsigma supports five ways to identify or locate these elements for your automated tests uniquely. The five supported locator types are:
- Accessibility ID: This is the most preferred locator to automate your tests, as this attribute would remain the same for other platforms like iOS, too, and makes it easier to port the same tests to different platforms. This attribute is also least likely to be changed during a structural change in the source.
- ID: After accessibility ID, this is the second preferred locator. Every element is supposed to have a unique ID.
NOTE:
If you are facing difficulty finding IDs for your elements, you should talk to your developer about it.
- XPATH: XPath stands for XML Path Language and will parse the source code to get the value of the referred element.
- Class Name: This will be the value assigned to the attribute Class Name for the element you want to capture.
- Name: This will be the value assigned to the attribute Name for the element you want to capture.