Explore

Buggy Cars Rating Testing Task

Introduction

Buggy Cars Rating is a community-based platform where users can register, log in, and rate cars. It includes features like:

User authentication (registration, login, password reset).

Browsing and rating cars by categories (e.g., Make and Model).

Viewing and editing personal user profiles.

Leaderboards showing top-rated cars and active users.

The platform has intentionally introduced bugs and usability issues for testing purposes. Your task is to explore the application, identify bugs, and suggest improvements.

⁠

Task Objectives

Understand the Application:

Explore the functionalities of the website

Buggy Cars Rating⁠

Get familiar with the key workflows, such as user registration, car rating, and leaderboard navigation.

Design a Test Plan:

Identify key functionalities and propose testing scenarios.

Include both functional tests (e.g., "Does the rating feature work correctly?") and non-functional tests (e.g., "Is the website responsive on different devices?").

Perform Manual Testing:

Execute the test scenarios you designed.

Pay attention to edge cases (e.g., What happens if invalid data is entered?).

Document Bugs:

Create a detailed bug report for each issue you find. The report should include:

Bug Description.

Steps to Reproduce.

Expected vs. Actual Results.

Severity Level (e.g., Critical, High, Medium, Low).

Propose Improvements:

Suggest enhancements to the platform's usability or functionality.

⁠

Deliverables

Test Plan:

A structured document listing the test scenarios you performed.

Bug Reports:

A list of all identified issues, including the details mentioned above.

Improvement Suggestions:

A brief description of potential enhancements to the user experience or functionality.

Summary Report:

A concise summary of your findings and your testing experience.

⁠

Evaluation Criteria

Test Design: How well did you analyze the application and propose relevant test scenarios?

Bug Identification: The depth and accuracy of the identified bugs.

Documentation Quality: How clear, detailed, and structured are your reports?

Creativity: Any additional insights or unique approaches to testing the application.

Communication: Clear and concise reporting in English / Czech.

⁠

Helpful Notes

The website may contain intentional bugs. Identifying them is part of the task.

You are free to use any tools for testing (e.g., browser developer tools, screen size testing tools).

Time management is essential—focus on identifying the most critical issues.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.