Android apps built here, for mobile automation practice
Three Android applications written by JS Testing Academy. Not somebody else’s demo app with our name on it — our code, our logo, and a stable id and accessibility description on every control, which is what makes them worth automating against.
These applications are for practice purpose, for automation testers.
Pick an application
ShopKart Mobile
E-commerce, end to end: sign in, search, cart, checkout, order id.
in.co.jstestingacademy.shopkart
JSTA UI Catalog
Every control, on its own screen: buttons, alerts, gestures, pickers, lists.
in.co.jstestingacademy.uicatalog
MediCare Mobile
Native screens plus a real WebView – the hybrid one.
in.co.jstestingacademy.medicare
What the three cover between them
Deliberately different from each other: a business flow, a widget catalogue, and a hybrid application.
| Application | What it is for |
|---|---|
| ShopKart Mobile | A business flow from sign-in to a generated order id. Forms, a cart, swipe-to-delete, a checkout. |
| JSTA UI Catalog | One screen per control. Buttons, text fields, choices, dropdowns, dialogs, pickers, sliders, a long list, gestures, tabs. |
| MediCare Mobile | Native screens plus a real WebView, so you have to switch contexts to drive it. The hybrid one. |
- One login everywhere:
student/practice123— the same credentials as the practice API. - Nothing is stored. Restarting the app is the reset, so a suite never inherits the last run’s data.
- No network and no server, except the WebView screen in MediCare, which loads our free QA demo site on purpose.
- Minimum Android 7.0, so an old spare phone will do.