← Back to projects
Case study · Mobile · Android

Hepsiburada Android test automation

An Appium/Java mobile testing project covering Android product search, filtering, and product detail assertions.

01 / Context and contribution

Scope of the work

An independent test automation project for the Hepsiburada Android application; no official company affiliation is claimed.

CV-described Appium/Java framework and repository-visible search and filter assertions.

02 / Approach

Search and product assertions

The ProductSearch test searches for a laptop, applies brand, price, and seller filters, and checks the brand, price range, and seller on the opened product. Interactions are collected in a SearchPage Page Object.

03 / Approach

Execution context and scope limit

BaseTest is configured for a specific Android emulator and local Appium server. This does not prove the test works on other devices or the current application version.

The CV also mentions a cart flow. No matching test file was found in the inspected repository tree, so it is not presented as a completed repository scenario here.

Technical structure

Execution context

The repository has no execution README. BaseTest uses an Android emulator named Pixel 4 API 29, UiAutomator2, and a local Appium server address. These settings do not show that the test currently passes on a recent device or app version.

Sources

The path to evidence

These links lead to public repository files. The presence of code does not mean the tests currently pass.

Open GitHub repository ↗
Verification status

What do we not know yet?

The repository has no README or shareable run report. The device, Appium, and application versions must be rechecked before any current pass status can be stated.

Contact

Let's talk about
test strategy.

Write to me about projects or how I approach testing.

Contact details ↗