Home Urban Scooters Project

Urban Scooters Project

Web, Mobile & API Testing

This comprehensive QA project demonstrates my testing expertise across multiple platforms within a single real-world application. I performed end-to-end testing covering web application testing, mobile testing, and API testing — all documented with test cases, defect reports, and evidence.

Web Testing

Functional, UI/UX, and regression testing

Mobile Testing

iOS/Android app testing with video evidence

API Testing

Postman validation and status code verification

Test Case Documentation

Complete test case documentation covering all testing scenarios for the Urban Scooters application. Scroll within the document to view test cases for web, mobile, and API testing.

Urban_Scooters_Test_Cases.xlsx
Open Full Document

Scroll within the document to view all test cases

Testing Breakdown

Detailed overview of each testing domain covered in this project

Web Application Testing Chrome, Firefox, Edge

Performed comprehensive testing of the Urban Scooters web application including functional testing, UI/UX validation, form submissions, and cross-browser compatibility checks.

Functional Testing Regression Testing UI/UX Validation Cross-Browser

Test cases documented in the spreadsheet above

Mobile Application Testing iOS & Android

Tested the Urban Scooters mobile application across iOS and Android platforms. Validated core features, reported defects with video evidence, and documented reproduction steps for each bug found.

Native App Testing Defect Reporting Video Evidence Bug Screenshots
View Mobile Defect Evidence & Bug Reports

API Testing Postman

Performed REST API testing using Postman to validate endpoints, request/response structures, status codes, and error handling. Tested positive and negative scenarios to ensure API reliability.

Request Validation Negative Testing Status Code Verification JSON Validation

See API concepts and HTTP methods explained below

Bug Evidence & Defect Reports

Click any screenshot to view in full size

Screenshots documenting bugs found during web, mobile, and API testing. Each defect was properly logged with reproduction steps, expected vs actual results, and severity classification.

Web Bug #1 – Text / Content Defect Web
Web bug report - Misspelled text in scooter description table
Expand

Content / Text Defect

Misspelled user-facing text in scooter description table

Mobile Bug #1 Mobile
Mobile bug report - No push notification received at scheduled time
Expand

Push Notification Timing Issue

No push notification received at 9:59 as scheduled

API Bug #1 API
API bug report - Creating courier without firstName returns 400 instead of 201
Expand

Incorrect Status Code / Request Validation Issue

Creating courier without firstName returns 400 instead of 201

View detailed mobile bug report with video evidence

API Concepts & HTTP Methods I Used

Understanding the fundamentals of REST API testing and the HTTP methods used to interact with web services

POST

Create

New Resource

Used to create a new resource on the server. For example, creating a new user account, adding a new order, or submitting form data.

POST /api/users
PUT

Update

Existing Resource

Used to update an existing resource on the server. Replaces the entire resource with the new data provided in the request body.

PUT /api/users/123
DEL

Delete

Remove Resource

Used to remove a resource from the server. Permanently deletes the specified resource from the database.

DELETE /api/users/123

What I Validate in API Testing

Request Body (JSON)

Verify correct structure and data types

Required Fields

Ensure mandatory fields are validated

Response Status Codes

Verify correct HTTP status returned

Response Body

Validate response data and format

Error Handling

Test negative scenarios and edge cases

Data Integrity

Confirm data persists correctly

Common HTTP Status Codes

Quick reference for status codes I verify during API testing

Code Status Meaning
Success (2xx)
200 OK Request successful
201 Created Resource created successfully
204 No Content Success with no response body
Client Errors (4xx)
400 Bad Request Invalid syntax or parameters
401 Unauthorized Authentication required
403 Forbidden Access denied
404 Not Found Resource doesn't exist
409 Conflict Resource state conflict
Server Errors (5xx)
500 Internal Server Error Server-side failure