Low Severity and High Priority Bugs in E-commerce Web Application

1. Typo on the Checkout Confirmation Page

Description: A misspelled word on the checkout confirmation page.

Severity: Low

Priority: High

2. Logo Displaying Incorrectly on Homepage

Description: The company logo appears stretched or pixelated.

Severity: Low

Priority: High

3. Incorrect Customer Support Email Address on the Contact Us Page

Description: The email address provided for customer support is incorrect.

Severity: Low

Priority: High

4. Broken Social Media Links in Footer

Description: Links to social media pages in the footer are broken.

Severity: Low

Priority: High

5. Non-functional Promo Code Input Box

Description: The input box for promo codes in the checkout process does not work.

Severity: Low

Priority: High

High Severity Low Priority Bugs in E-Commerce Web Application

1. Payment Gateway Failure in Specific Currency
High Severity: Users cannot complete purchases using a particular currency.
Low Priority: This currency is rarely used by the customer base.
Technical: When users select a rarely used currency, the payment gateway integration fails due to incorrect API calls or missing currency configuration.
Simple: Users can't pay in a specific, rarely-used currency.

2. Crash When Filtering Products by a Rare Attribute

High Severity: The website crashes, disrupting user experience.

Low Priority: The attribute filter is rarely used by customers.

Technical: Filtering by an uncommon attribute triggers a crash, possibly due to a null reference or unhandled exception.

Simple: The site crashes when filtering by a rarely used feature.

3. Incorrect Discount Calculation for Bulk Orders

High Severity: Users are charged incorrect amounts.

Low Priority: Bulk orders are rare.

Technical: The discount logic has a bug when calculating bulk order discounts, leading to incorrect pricing.

Simple: Bulk orders get the wrong discounts.

4. Failure to Load Product Images on Secondary Pages

High Severity: Product images do not load, affecting user experience.

Low Priority: Occurs on less frequently visited pages.

Technical: Image URLs or CDN issues prevent images from loading on less-visited pages.

Simple: Product images don't show up on certain pages.

5. Inability to Apply Multiple Coupons on Checkout

High Severity: Users cannot avail of multiple discounts.

Low Priority: Only a few users use multiple coupons.

Technical: The checkout process doesn't handle multiple coupon codes due to a bug in the discount application logic.

Simple: Users can't use more than one coupon at a time.

6. Error in Wishlist Functionality for Out-of-Stock Items

High Severity: Users cannot add out-of-stock items to their wishlist.

Low Priority: Out-of-stock items are a small portion of the catalogue.

Technical: The wishlist feature crashes or misbehaves when adding out-of-stock items due to lack of proper handling.

Simple: Can't add out-of-stock items to a wishlist.

7. Mismatch in Product Specifications on Detailed View

High Severity: Detailed view shows incorrect specifications.

Low Priority: Rarely visited detailed specifications page.

Technical: The product detail page shows incorrect specs due to outdated or incorrect data fetching logic.

Simple: Wrong details are shown on the product page.

8. Search Function Fails for Long Strings

High Severity: Users can't search with long keywords.

Low Priority: Most users use short search queries.

Technical: Long search queries cause database or server errors, possibly due to input length limits or inefficient query handling.

Simple: Searching with long phrases doesn't work.

9. Incorrect Display of User Loyalty Points

High Severity: Users see the wrong loyalty points balance.

Low Priority: The loyalty points program has low participation.

Technical: The loyalty points calculation or display logic has errors, showing incorrect balances.

Simple: Users see the wrong loyalty points balance.

10. Failure to Load Reviews for Products with No Reviews

High Severity: Page crashes if a product has no reviews.

Low Priority: Most products have at least one review.

Technical: The review section crashes when there are no reviews, likely due to poor handling of empty datasets.

Simple: Page crashes if there are no reviews.

Must-Have Security Test Cases for Your Web Application

1. Try to directly access the bookmarked web page without logging into the system.

2. Verify that the system should restrict you from downloading the file without signing in to the system.

3. Verify that previously accessed pages should not be accessible after logging out i.e. Sign out and then press the Back button to access the page accessed before.

4. Check the valid and invalid passwords, password rules say it cannot be less than 8 characters, user ID and password cannot be the same etc.

5. Verified that important i.e. sensitive information such as passwords, ID numbers, credit card numbers, etc should not be displayed in the input box when typing. They should be encrypted and in asterisk format.

6. Check Is bookmarking disabled on secure pages? Bookmarking Should be disabled on secure pages.

7. Check Is Right Click, View, Source disabled? The source code should not be visible to the user.

8. Check if your server locks out an individual who has tried to access your site multiple times with invalid login/password information?

9. Verify the timeout condition, after a timeout, the user should not be able to navigate through the site.

10. Check Are you prevented from doing direct searches by editing content in the URL?

11. Verify that the restricted page should not be accessible by a user after session time out.

12. ID/password authentication, the same account on different machines cannot log on at the same time. So at a time, only one user can log in to the system with a user ID.

13. ID/password authentication methods enter the wrong password several times and check if the account gets locked.

14. Add or modify important information (passwords, ID numbers, credit card numbers, etc.). Check if it gets reflected immediately or caching the old values.

15. Verify that the Error Message does not contain malicious info so that hackers will use this information to hack the website.

Exploring the Different Types of Software Testing

 Overview of web app testing scope

1. Functional Testing

2. Usability Testing

3. Performance Testing

4. Security Testing

5. Compatibility Testing

6. Interface Testing

User Interface Test Cases: What You Need to Know

1. Navigation Test: 

• Test the navigation bar or menu by clicking on each link or button to ensure that they take you to the correct page or section of the website or application.

2. Input Validation Test: 

• Test the input fields, such as forms or search boxes, by entering valid and invalid data to ensure that the system handles the inputs correctly.

3. Button Test: 

• Test all buttons on the UI to ensure they perform the intended actions and provide appropriate feedback, such as success or error messages.

4. Compatibility Test: 

• Test the UI on different devices and browsers to ensure it is compatible with various screen sizes, resolutions, and operating systems.

5. Responsiveness Test: 

• Test the UI for responsiveness by resizing the browser window or using device emulators to see how the UI adapts to different screen sizes.

6. Content Test: 

• Test the UI for consistency and accuracy of content, including text, images, and multimedia.

7. Accessibility Test: 

• Test the UI for accessibility compliance, ensuring that users with disabilities can access and use the UI without any issues.

8. Performance Test: 

• Test the UI for performance by checking loading times, response times, and any delays or lags in the system.

The Power of Headless Browser Testing: Enhancing Your QA Strategy

What is Headless Testing?

• Headless testing is a method for evaluating a website’s or online application’s functionality without having to use a web browser. The test script simulates operations like clicking buttons and filling out form fields by sending commands directly to the website’s source code rather than engaging with it through the UI. As a result, testing may be done more quickly and effectively because there is no need to load a full web browser; the test script can instead run in the background.

Advantages of Headless Testing:

1.  Speed of Execution: Headless tests run substantially quicker than tests executed on a real browser. The primary reason for this is that your tests aren’t having to start up a browser UI each time. This means they can avoid the time it takes a real browser to load JavaScript, CSS, and render HTML on a website. I’ve seen estimated execution time savings in the range of 7-15%.
2.  CICD: Because it is so much quicker, it makes it ideal for continuous integration and delivery (CI/CD) pipelines.
3.  Server Testing: It can also be helpful for testing web applications in contexts without a UI, such as servers.
4.  Multi-Tasking: The test script can run in the background and finish tests more rapidly because it does not need to open a full web browser.
5.  Shift-Left: Because it runs so much quicker than real browser testing, you can get the results of your testing much faster.

Disadvantages of Headless Testing:

1.  User Experience: Headless testing may not always correctly imitate the user experience, which is one potential problem. The test script may not always correctly reflect how a user would actually interact with the website or web application because it is engaging directly with the source code rather than through a UI.
2.  UX or Visual Design: Additionally, headless testing might not be able to completely test specific features of a website or web application, including the user interface or visual design.
3.  Debugging: Debugging with headless can be challenging. Typically you will need to run the traditional way to get to the bottom of failures.
4.  Real-time test execution visual: When running headless you don’t get the option to watch your test running on the UI.

Headless Testing Use Cases:

•  Simulating multiple browsers on a single machine.
•  Running tests on a headless system without a UI.
•  Element testing – since headless browsers render and interpret CSS & HTML like a real browser, you can use them to test style elements such as buttons, forms, links, etc…
•  Extracting values from a page/scraping.
•  Extracting a PDF.
•  Generate test data.
•  Performance issues such as SSL, front- and back-end code, and load considerations, as well as non-graphic elements such as response time, error handling, and access to remote resources, can all be evaluated using headless testing.

Common Headless Browsers:

•  For headless testing, a number of tools and frameworks are available, including Headless Chrome, PhantomJS, HtmlUnit, Firefox, Puppeteer, and Splinter. These tools allow you to create and execute test scripts in a number of different computer languages, such as Java, Python, and JavaScript.

Essential Points to Include in Your Checklist for Testing a Web Application

PDF - Testing of Web Application

OTP Code Verification: How to Test for Every Scenario

1. Verify for verification whether valid and correct OTP is generated or not.
2. Verify OTP code should be valid only for one time or not.
3. Verify the count for the OTP code generated should not be more than required.
4. Test the count for the OTP code generated should not be less than required.
5. Verify OTP code is sent to the user successfully or not within time or not.
6. Verify and confirm the time duration in which the user received the OTP-generated code sent by email.
7. Check the time duration for the OTP-generated code received by the user on mobile.
8. Verify the OTP code fetched by the application from the message by default or user add manually. It depends on the requirements.
9. Verify by adding the valid OTP application that must accept the code successfully.
10. Confirm whether the correct info message is shown or not in case if the User adds a valid OTP code.
11. Verify a proper error message should be shown in case if the user adds an invalid OTP code.
12. Verify OTP code should expire after the time allowed by the application or software.
13. Verify application should not accept the OTP code once expired.
14. Verify the user can request a new OTP code by clicking on the link or button to resend the code.
15. Verify on again request on clicking on the Resend link OTP code should be sent to the user successfully or not.
16. Verify whether the user should be temporarily blocked or not in case it requests for new OTP code again and again.
17. Verify whether the limit is set for the OTP code to resend multiple times or not. (For example, a maximum of five attempts is allowed per user)
18. Verify OTP code is case-sensitive or Not.
19. Verify OTP code is only numeric or alphanumeric.

Email Field Testing: Tips and Best Practices for Effective Results

 Design-related Test Cases:

1.  Verify email field is present on the page.
2.  Verify whether the label text is shown with the email field or not.
3.  Verify label text email align with the email field.
4.  Verify that the placeholder text in the email field is added or not.

Functional Test Cases:

1.  Verify email address field is accessible by clicking on the email field.
2.  Check users can type email in the email field.
3.  Verify user can paste the email address in the field by keyboard keys Ctrl + v.
4.  Verify that the user can paste the email address with the mouse by right-clicking in the email field and pasting the email address.
5.  Verify validation for the email field is implemented or not.
6.  Verify whether an error message should be shown in case if the user adds an invalid email address or not.

Positive Test Cases:

1.  Validate the email field by entering a valid email address. (abc@gmail.com)
2.  Verify the email must contain @ in the email address.
3.  Verify that an email field accepts an email containing a plus + sign in the Email address.
4.  Verify whether an email field validates an email address containing a domain or not. (abc@gmail.com)
5.  Make sure there should dot present in the email address or not.
6.  Verify an email address should be considered correct if an email contains a subdomain.
7.  Check that an email address has a maximum of 2 dots in the case of the subdomain.
8.  Verify an email address containing a special character consider valid.
9.  Verify an email address having numbers is valid.
10.  An email address with quotes ” ” should consider valid.
11.  An email address may contain a dash – or underscore _.