โ€Œ
category-iconWEB TESTING

Breaking Cars.ng: Exploratory test on the website covering core user flows

13 Oct 20250480

๐Ÿš— Introduction

Cars.ng aims to simplify the process of buying and selling cars online. However, during testing, I discovered several issues that could frustrate users and impact transactions. From login failures to unclickable buttons, these problems need urgent fixes to enhance usability and increase conversions.

In this post, Iโ€™ll walk you through the methodology, key findings, and recommendations to improve Cars.ng by doing an exploratory testing.

๐Ÿ”Ž What is Exploratory Testing?
Exploratory testing is a dynamic approach where testers explore the application without predefined test cases. Instead of following a strict script, testers actively investigate the software, uncovering issues in real-world scenarios. This method is particularly effective for identifying usability problems, inconsistencies, and edge cases that automated tests might miss.

๐Ÿ”ฌ Methodology: How I Conducted the Test
Since exploratory testing thrives on real-world interactions, I took the following approach:
1. Smoke test: I started with smoke testing where i needed to make sure that the website serve its oroginal purpose its built for. In this case buying and selling cars and exploring details specification of cars and connect with car dealers.In this case website failed to pass the test as there were some critical bugs that hinder the progress of the buying and selling cars as well connecting with dealership.Here is a column chart based on severity :

Figure 1: Number of bugs based on severity

2.Minimal acceptance testing: Minimal acceptance testing is where i tested with all the positive values with all the featues.Here i made sure that all buttons are working and delivers what its originally built for.Here i found Some failed tests and documented them in my report.

3.Acceptance testing: Here both positive and negative values were tested to make sure Quality was assured and in these case i went through back and forth with all the functionalities-
1) Perform check if fields has validation and limitation
2)Perform check if fields accepts negative values
3)Perform check clicking around the button does not trigger any action
4)Perform check any missing feature in terms of Gui and functionality

4) Gui testing: Here as a sqa i tested all the nitty gritty details of all the features and looked for any missing features. I found some missing features and documented them i bug report as well suggested improvements based on my findings.

5)Cross browser testing: Where i tested the website with different browser and Operating system to make sure it delivers its functions as per requirements. I found some failed tests here too and reported them in bug report

6)Using dev tools: Using dev tools i tested how website behaved in different networking and throttle. The fields has and limitation or validation, that i found using dev tools. I used Elements and network tabs to do these comprehensive testing

๐Ÿ›‘ Findings: The 5 Most Critical Issues

1๏ธโƒฃ Authentication Errors & Missing Facebook Login

  • Users encounter login errors, making access unreliable.
  • Facebook login (mentioned in Bug-1) is missing, limiting quick authentication.
    ๐Ÿ“Œ Impact: Users may abandon the site if logging in is difficult.
Press enter or click to view image in full size

2๏ธโƒฃ No โ€˜Buyโ€™ Button in the Sell Section

  • The websiteโ€™s main purpose is to enable car transactions, yet the โ€œBuyโ€ button is missing in the Sell section.
    ๐Ÿ“Œ Impact: Confuses users and prevents smooth transactions.

3๏ธโƒฃ Mobile Users Canโ€™t Submit Contact Information

  • The contact form is unresponsive on mobile, preventing users from listing their cars.
    ๐Ÿ“Œ Impact: A major accessibility issue โ€” mobile users make up a large portion of online shoppers.+
Press enter or click to view image in full size

4๏ธโƒฃ Lack of Input Validation (Form Errors & Data Inconsistency)

  • Many fields allow incorrect or incomplete data, such as empty fields and excessive text.
    ๐Ÿ“Œ Impact: Poor data quality, security risks, and a frustrating experience for users.
Press enter or click to view image in full size

5๏ธโƒฃ Non-Clickable UI Elements (Broken Navigation & Buttons)

  • Sliding bars, profile buttons, and submit buttons donโ€™t respond to clicks.
    ๐Ÿ“Œ Impact: Users cannot complete essential actions, leading to frustration and drop-offs.

๐ŸŽจ UI/UX Recommendations: How to Fix These Issues

๐Ÿ”น Enhance Authentication & Enable Facebook Login:

  • Fix existing login issues.
  • Implement one-click Facebook login for seamless access.

๐Ÿ”น Fix the Missing โ€˜Buyโ€™ Button Issue:

  • Ensure the โ€œBuyโ€ button appears in all relevant sections to complete transactions.
  • Use a bold colour (green/blue) to improve visibility.

๐Ÿ”น Improve Mobile Usability:

  • Make sure forms are responsive and fully functional on mobile.
  • Add real-time validation messages (e.g., โ€œPlease enter a valid phone numberโ€).

๐Ÿ”น Apply Proper Input Validation:

  • Restrict inputs to correct formats (e.g., phone numbers, email).
  • Provide instant feedback when a user enters incorrect data.

๐Ÿ”น Fix Broken UI Elements:

  • Ensure buttons and navigation elements are clickable and responsive.
  • Improve touch sensitivity for mobile users.

๐Ÿš€ Final Thoughts

Exploratory testing is a powerful way to uncover real-world usability issues. The bugs found on cars.ng highlight the need for better authentication, mobile support, and functional UI elements. Fixing these issues will improve user satisfaction and increase conversions.

Iโ€™ll continue testing and updating this blog with new findings. Have you encountered similar issues on marketplace websites? Share your thoughts in the comments! ๐Ÿ‘‡