dtac

Overview

dtac is a telecommunications ecosystem rather than a single application: Android and iOS clients, a web application, and the backend services all of them depend on. The QA work covered the full cycle, from reading requirements through to automation and performance testing.

The Challenge

Four surfaces share one set of backend services, so the same feature has to be verified in four places with different constraints, and a backend change can affect all of them at once. That shape pushes work down the stack: validating behaviour at the API level first makes client testing about the client, not about re-testing business rules on every platform.

My Contribution

• Requirement analysis and test preparation
• Test case writing and test execution
• Bug reporting and defect follow-up
• API automation
• UI automation for Android and Web
• Performance testing

Automation

Automation ran on two fronts: API automation covering the shared backend services, and UI automation for the Android and Web clients so that repeatable regression passes did not have to be executed by hand on every release.

Testing Strategy

Requirement analysis first, so that risk was identified before test cases existed. Functional coverage was designed per platform, API testing verified shared behaviour once instead of four times, and performance testing validated how the system held up under load.

Testing Areas

• Requirement Analysis
• Test Planning
• Test Case Design
• Functional Testing
• API Testing
• UI Automation
• Performance Testing
• Bug Reporting