One of the difficult decisions in testing is picking the correct feature for reporting a bug. Fortunately, we have compiled the list of the most frequent features you can see on the test cycle overview page.
Bag, Shopping Bag, Cart, or Shopping Cart | represents the feature that allows the user to purchase the product, edit the number of articles in the Cart and discard unwanted items from the Cart. |
Category Landing Page | represents the page where the user finds relevant products from the same category. Depending on the design, a category landing page could display the promo material at the top of the page. |
Checkout | represents the set of steps the user conducts to complete the order. The user can proceed to the Checkout as an existing or guest user. |
Footer | represents the bottom of the page. The Footer contains the legal document links, contact info, and social media links/icons. Depending on the design, some pages omit the Footer. |
Header | is located at the top of the webpage. Considering most of the websites, the Header is a strategic section that provides the basic idea of the website content. It gives structure to the website and catches the attention of users. |
Homepage | represents the front page of the website. Most of the visitors start their journey through the website from the Homepage. |
Landing Page | represents the page the user lands on after clicking on the link. It is designed for conversion and driving traffic to the website. One of the examples of the Landing Page is the page one lands after clicking on the ad link after performing a Google search. |
Login/Logout | represents the set of actions the user needs to conduct to access the profile and leave it afterward. |
My Account | represents the feature where the user saves and stores personal info together with settings. |
Navigation | represents all the movement on the website or app. It includes but is not limited to the Main Navigation, “Hamburger” Navigation, Sticky Menu, Sidebar Navigation, and Breadcrumbs Navigation. |
Newsletter Subscription | represents the feature or action the user undertakes to subscribe for special offers from a website or application. |
Order Process/Order flow | is the same feature as the Checkout. |
Product Category Page | represents the page with a set of similar products merged into categories. |
Product Collection Page | represents the page with a list of products that belong to the same collection. |
Product Detail Page | represents the page of a single product where the user can find product info, media gallery, possible options for purchase (size, volume, quantity), similar or suggested products, etc. |
Product Landing Page | represents the page where the user can perform the following actions: purchasing a discounted product or subscribing to the offer. In marketing, this is called Post Click Page. The difference between PDP and PLP are the following: PDP has Navigation Menu and Footer. PLP has less volume, but it contains the title that matches the ad text, a button, or a link that calls for action (subscription or purchase). One of the indicators that the user is on PLP is a list of so-called success stories. |
Product Listing Page | represents the list of products belonging to the same category or keyword search. |
Product Overview Page | represents the list of products that belong to the same category or subcategory. |
Register | represents the set of actions in the creation of an account. |
Search | represents the feature one can use for finding products or services using the keywords. |
Search Results Page | represents the generated list that appears after the user searches for keywords. |
Sign up for an account | is the same as Register for an account. |
Wishlist | represents the feature that facilitates saving products for the later purchase. |
In case you don't see a feature on the list, bear in mind that our customers decide if they want to use our standard features or not. Furthermore, they create their own features if our list is not extensive enough. When that happens, you can always reach out to your TL for help in understanding where you should report the bug.