Testing the Taco Bell website | Exploratory Testing | QA

Introduction

Hey everyone, this is Jason with Glitch in the System, and today we have another episode of Exploratory Testing. If you're new to the channel, exploratory testing is when we find a website, test it for 30 minutes to an hour, and report any bugs we find. Today, we are testing the Taco Bell website. Stay tuned as we explore and see how many bugs we can find.

Getting Started

The rules are straightforward: we will explore the Taco Bell website for around 30 minutes to an hour. We'll record our findings using QA Touch and Snagit for screen captures. You can check these tools out via the provided links in the description if you want to give them a try.

An Overview

Previously, we tested Wendy's and Burger King, specifically their delivery menu ordering systems. Both had issues but let's see how Taco Bell fares today. To get started, we need to check the delivery button and navigate the menu using Disneyland's address.

Initial Impressions

On the Taco Bell website, some design elements immediately stood out. There's a gap between some menu items, and the alignment is inconsistent. For example, one menu item doesn't have an "add to order" button unless you customize it. This inconsistency makes for a poor user experience.

Trying to Order

I decided to try ordering everything on the menu. However, the site has a logic that prevents you from exceeding 50 items in the cart. Interestingly, the cart already had 53 items. When I tried to adjust quantities, I found several error messages and inconsistencies.

Further Testing

Adding more items revealed more issues, such as misaligned modals and broken scroll functionality. I also noticed that some images were missing, and the site had parts where the error messages were incorrect or missing altogether.

Design and Functionality Issues

While testing, I found that some design choices on the website were awkward and confusing. Some elements overlapped, making the interface less user-friendly. Additionally, I discovered that customizing items resulted in different behaviors depending on how you accessed the customization options.

Testing Responsiveness

Switching to a mobile view revealed further problems: the default view cuts off important sections, and scrolling is problematic. This degradation indicates a need for better responsive design.

Conclusion

After 30 minutes of testing, I found numerous issues on the Taco Bell website. These ranged from broken logic and missing elements to poor design choices that hinder user experience. There's no such thing as bug-free software, but some manage to catch more issues ahead of time.

Keywords

• Exploratory Testing
• Taco Bell Website
• QA Touch
• Snagit
• Ordering System
• User Experience
• Design Issues
• Website Bugs
• Responsive Design
• Bug Reporting

FAQs

1. What is exploratory testing? Exploratory testing is a type of software testing where the tester actively explores the application without predefined test cases to identify bugs.

2. Which tools were used in this testing? We used QA Touch for reporting issues and Snagit for screen captures.

3. What were some of the primary issues found on the Taco Bell website? The issues ranged from design inconsistencies and misaligned elements to broken cart logic and poor responsiveness on mobile devices.

4. How did the Taco Bell website perform compared to Wendy's and Burger King? Taco Bell's website had numerous issues, much like those we found on Wendy's and Burger King. Performance varied but generally highlighted a need for better quality control.

5. Why is there no such thing as a bug-free application? It is virtually impossible to catch all bugs due to the complexity and variability of software environments and user interactions.

If you have any specific websites or fast food chains you'd like me to test next, drop a comment below. Until next time, make sure to hit like, subscribe, and the bell icon to get notifications for future videos. Happy testing!