Mobile app testing automation
Mobile app testing automation that does not break every release
Scripts that depend on one resource ID snap when a screen changes. Parikshak looks for each control in several ways, so a small UI change does not wreck your whole suite.
Real devices and emulators
Run over USB, over Wi-Fi, or on an emulator. Run the same suite on more than one device at once.
Native and Flutter
Native apps are found by resource ID, text and accessibility labels. Flutter apps are matched through their semantic descriptions.
Several ways to find a control
Text, description, class, position and visual matching are tried so one renamed ID does not stop the run.
Handles the awkward bits
Toasts, pop-ups, OTP screens, locked or sleeping devices and crashes seen in logcat are all part of the run, not an afterthought.
Live mirror while it runs
Watch the phone screen inside the desktop app as tests execute.
Reports with proof
Screenshots per step, short video clips and logs, bundled into a report your client or auditor can open in a browser.
Frequently asked questions
No. Parikshak tests the installed app from the outside, the way a person would use it.