My Testing Experience with Cars.ng: Ensuring a Seamless User Journey

Testing Cars.ng: A QA Engineer's Experience Introduction As a QA engineer, I recently had the opportunity to test Cars.ng, a platform designed to make buying and selling cars in Nigeria easier. The experience provided valuable insights into the importance of thorough testing in ensuring a seamless user journey. My testing included functionality, usability, and performance evaluations. (For reference, you can visit the live site Cars.ng to experience its features firsthand.) Understanding Cars.ng Cars.ng is a marketplace that connects car buyers and sellers, offering a range of features such as vehicle listings and price comparisons. Given its role in the auto industry, the platform must remain fast, secure, and user-friendly. Methodology To thoroughly assess the website, I adopted the following methodology: 1. Test Planning & Scope Definition I began by defining the scope of testing—covering both buyer and seller user flows. I prepared test cases that simulated real-life interactions, such as: Searching for vehicles Viewing detailed car pages Attempting account logins 2. Functional Testing I tested various features, including: User Registration & Login – Ensuring users can create accounts, log in, and reset passwords without issues. Car Listings – Checking that users can upload, edit, and search for vehicles smoothly. 3. Usability Testing I observed how easily users could navigate the website and complete common tasks, including: Assess the ease of navigation for buyers and sellers Test the responsiveness of the website across different devices Identify any UI/UX flaws that hinder the user experience. 4. Error Handling Verification Special attention was given to scenarios where users encounter issues. In one test, an unregistered user trying to log in using a Google account unexpectedly triggered an HTTP 500 error instead of a clear message. Screenshot 5. Bug Documentation Every defect discovered was documented in detail in my bug report sheet. Bug Report Sheet Screenshots were captured to illustrate key problems. For example, see the Testing Screenshot showing the 404 error when clicking the "Car Prices in Nigeria" footer link. Screenshot. Findings Throughout the testing phase, several issues were observed:

Feb 5, 2025 - 15:53

My Testing Experience with Cars.ng: Ensuring a Seamless User Journey

Testing Cars.ng: A QA Engineer's Experience

Introduction

As a QA engineer, I recently had the opportunity to test Cars.ng, a platform designed to make buying and selling cars in Nigeria easier. The experience provided valuable insights into the importance of thorough testing in ensuring a seamless user journey. My testing included functionality, usability, and performance evaluations. (For reference, you can visit the live site Cars.ng to experience its features firsthand.)

Understanding Cars.ng

Cars.ng is a marketplace that connects car buyers and sellers, offering a range of features such as vehicle listings and price comparisons. Given its role in the auto industry, the platform must remain fast, secure, and user-friendly.

Methodology

To thoroughly assess the website, I adopted the following methodology:

1. Test Planning & Scope Definition

I began by defining the scope of testing—covering both buyer and seller user flows. I prepared test cases that simulated real-life interactions, such as:

Searching for vehicles
Viewing detailed car pages
Attempting account logins

2. Functional Testing

I tested various features, including:

User Registration & Login – Ensuring users can create accounts, log in, and reset passwords without issues.
Car Listings – Checking that users can upload, edit, and search for vehicles smoothly.

3. Usability Testing

I observed how easily users could navigate the website and complete common tasks, including:

Assess the ease of navigation for buyers and sellers
Test the responsiveness of the website across different devices
Identify any UI/UX flaws that hinder the user experience.

4. Error Handling Verification

Special attention was given to scenarios where users encounter issues.

In one test, an unregistered user trying to log in using a Google account unexpectedly triggered an HTTP 500 error instead of a clear message. Screenshot

5. Bug Documentation

Every defect discovered was documented in detail in my bug report sheet. Bug Report Sheet

Screenshots were captured to illustrate key problems.
For example, see the Testing Screenshot showing the 404 error when clicking the "Car Prices in Nigeria" footer link. Screenshot.

Findings

Throughout the testing phase, several issues were observed: