iOS Developer for Puzzle App Automation
Budget: $30 – $250 USD
Summary
We are seeking a skilled iOS (iPhone) automation developer to assist with building a UI automation and workflow testing solution for a puzzle-style mobile application. The project focuses on automating predefined user interface flows for quality assurance, usability testing, and repetitive interaction validation.
The automation will simulate normal user interactions by identifying on-screen elements and responding appropriately to different UI states such as pop-ups, dialogs, and navigation screens.
⸻
What We Need
The developer will create an automation system that can:
• Operate on iPhone (iOS) devices
• Identify and interact with specific UI elements (buttons, boxes, pop-ups)
• Navigate predefined workflows consistently and accurately
• Handle interruptions such as modal dialogs or temporary screens
• Run for extended periods for stability and endurance testing
• Be configurable and maintainable for future UI updates
⸻
Expectations & Deliverables
• A functional iOS automation solution suitable for testing purposes
• Clear documentation for setup and configuration
• Basic error handling and logging
• Professional communication and realistic timelines
⸻
Working Relationship
We value a transparent, professional, and collaborative relationship. This project has clearly defined goals, structured milestones, and a focus on long-term maintainability. We are responsive, organized, and respectful of a developer’s expertise and time.
⸻
Why Work With Us
• Well-scoped technical challenge
• Clear expectations and decision-making
• Emphasis on quality, stability, and professionalism
• Open communication and prompt feedback
Screening Questions
1. What experience do you have with iOS (iPhone) UI automation or mobile test automation projects?
2. Which iOS automation tools or frameworks have you used (e.g., Appium, XCUITest), and in what context?
3. How do you design automation to remain stable when UI elements or screens change?
4. Have you worked on long-running or endurance automation tests before? If so, how did you ensure reliability?
We are seeking a skilled iOS (iPhone) automation developer to assist with building a UI automation and workflow testing solution for a puzzle-style mobile application. The project focuses on automating predefined user interface flows for quality assurance, usability testing, and repetitive interaction validation.
The automation will simulate normal user interactions by identifying on-screen elements and responding appropriately to different UI states such as pop-ups, dialogs, and navigation screens.
⸻
What We Need
The developer will create an automation system that can:
• Operate on iPhone (iOS) devices
• Identify and interact with specific UI elements (buttons, boxes, pop-ups)
• Navigate predefined workflows consistently and accurately
• Handle interruptions such as modal dialogs or temporary screens
• Run for extended periods for stability and endurance testing
• Be configurable and maintainable for future UI updates
⸻
Expectations & Deliverables
• A functional iOS automation solution suitable for testing purposes
• Clear documentation for setup and configuration
• Basic error handling and logging
• Professional communication and realistic timelines
⸻
Working Relationship
We value a transparent, professional, and collaborative relationship. This project has clearly defined goals, structured milestones, and a focus on long-term maintainability. We are responsive, organized, and respectful of a developer’s expertise and time.
⸻
Why Work With Us
• Well-scoped technical challenge
• Clear expectations and decision-making
• Emphasis on quality, stability, and professionalism
• Open communication and prompt feedback
Screening Questions
1. What experience do you have with iOS (iPhone) UI automation or mobile test automation projects?
2. Which iOS automation tools or frameworks have you used (e.g., Appium, XCUITest), and in what context?
3. How do you design automation to remain stable when UI elements or screens change?
4. Have you worked on long-running or endurance automation tests before? If so, how did you ensure reliability?