Conversation
Adding Identifiers, Labels and Values where necessary
Implement base POM and base test
Finalising and polishing the UI Test
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request: iOS Automation – Tech Test Submission
This PR includes a UI automation test for the Wiggles iOS app, focusing on navigation from the Puppy Listing Page (PLP) to the Puppy Details Page (PDP) and back.
Highlights:
Implemented using the Page Object Model (POM) for clarity, modularity, and future scalability
Verifies the presence of key UI elements on the PDP to demonstrate UI automation setup
Original accessibility identifiers were preserved and used directly as defined in the app
Identifiers, Labels, and Values were added to show how we could support automated testing and improve clarity
Note:
In a real-world scenario, validating the presence of individual UI elements is typically not the most effective approach for end-to-end automation. While helpful in demonstrating a working automation framework, these kinds of checks offer limited long-term value and can become brittle as the UI evolves.
Notes:
UI tests are generally more impactful when focused on complete user journeys and functional outcomes—such as validating that an item was added to a cart, a user was successfully authenticated, or a confirmation message was displayed. Given the limited functionality of this app, this test uses element visibility checks as a way to show structure, reliability, and test design in the absence of full user flows.