Candidate responsibilities

Android Test Developer (Clank)

Modify instrumentation tests for Chrome Android (chrome_public_test_apk) and test utility classes these tests, which are open-source code in the Chromium repository, by:

- Replacing calls to Espresso and other helpers with using the Public Transit test framework instead.
- Writing test-specific classes that model application UI states (e.g. dialogs, screens, other visual elements) where necessary using the Public Transit framework.
- Making changes to the Public Transit framework if necessary to support the changes
- The scope of the changes is a number of the child bugs of the umbrella bug crbug.com/433553616: Migrate instrumentation tests to Public Transit. (It is NOT expected the contractor will complete all child bugs of the umbrella bug.)
- Keeping the test cases passing on all Continuous Integration environments they run in, which includes:
Emulator environments and real device environments
Multiple Android versions (Android 10 through latest)
Phones,



Tablets, Laptops and Automotive” infotainment systems
- Keeping equal or improving readability of the test cases.
- Keeping equal or improving flakiness (reliability) of the test cases.
- Keeping test runtime of the test cases equal to or below 125% of the original runtime, counted separately per test case. Larger regressions are acceptable when there are changes to the scope of the validation performed by the test.
- Code Reviews will be performed by Google employees prior to merging the changes.
- Fixing compilation errors, test breakages, significant test performance regressions, or flakiness (reliability) regressions if caused by the changes. If the changes have been reverted due to any of these problems, modify the change to fix the problem and submit it again for review and ultimately merge the fixed version.

📌 Senior Android Developer (Hyderabad)
🏢 Grid Dynamics
📍 Hyderabad