QA Engineer 2 -Mobile Apps

This role combines hands-on manual and exploratory testing with native mobile application automation for PanelSmart. You will assess Android and iOS app changes on representative devices, exercise survey and account workflows, and maintain Appium tests that provide dependable feedback. You will also validate mobile-to-service integration scenarios with the web and backend teams.

Core: Appium, Java, Selenium WebDriver, TestNG, Maven, and Allure. Supporting integration testing: REST-Assured for selected API interactions.

• Perform functional and exploratory testing of the PanelSmart mobile app on Android and iOS devices or simulators, as the team’s supported matrix requires.

• Investigate platform-specific behavior, device and OS differences, permissions, notifications, interruptions, orientation, connectivity, and app lifecycle where relevant.

• Test login, password recovery, menus, settings, survey navigation and pause/resume, and questionnaire types and validation rules.

• Report reproducible defects with device, OS, app build, setup, steps, expected and actual results, and screenshots or logs; retest fixes.

• Build and maintain Appium end-to-end tests in Java using the team’s TestNG and Maven framework.

• Keep shared driver setup, platform-specific locators, page objects, test data, and utilities readable and reusable.

• Automate agreed Android and iOS smoke, sanity, and regression scenarios, including login, menus, survey questions, notifications, and logout.

• Use Allure results and captured evidence to diagnose failures and distinguish application defects from device, environment, and test issues.

• Validate mobile workflows that depend on backend services, using REST-Assured helpers or API checks where they support the test scenario.

• Maintain test data and environment configuration for supported platforms, and coordinate app builds and test readiness with development teams.

• Run and maintain the Android and iOS automation workflows, review results, and improve stability, evidence, and feedback.

• Review stories and acceptance criteria for mobile-specific risks, accessibility of controls, and testability across supported platforms.

• Use manual and exploratory findings to prioritize new regression automation and focus coverage on high-impact user journeys.

• Contribute automation code through Git-based review workflows and communicate quality risks clearly to product and engineering.