Important Things to Test Ecommerce Applications

•  E-commerce applications have many users worldwide, dealing with finance, marketing, retail & wholesale, manufacturing, and auctions.

1. Testing E-commerce Application’s Functionality

An e-commerce web or mobile application has four important elements in its structure, and they are:

• Main Pages – Homepage, Product page, Special Offers, About Us page, Sitemap pages, Privacy Policy page, Press Releases page, etc.
• Category / Product Type Pages – The product page includes options such as product size, colour, and type. There is a sorting feature to filter out products based on price, model, size, etc. There is also the “Add to Cart” or “Add to Wishlist” feature present in the category pages.
• Product Description Page – Consists of the product title, description, product images, related products, Add to Cart feature, Product comparison, additional product info, etc.
• Shopping Cart – Products list view, removing the product from the list, cash on delivery option, Select delivery option, card payment, pay now option, etc.

2. Testing E-commerce Application Workflow

• Login and Signup options
• Search functionality
• Product review posting feature
• Sorting feature
• Applying filters for choosing the desired product(s)
• Add/remove functionality in the shopping cart
• Check out process
• Order number and invoice generation
• Payment gateway and payment processing

3. Payment Gateway Functionality

  Another important functionality to test is the payment gateway and you have to conduct multiple tests to ensure it functions properly and provides security while doing online transactions. Here are the checkout and payment processes that you need to test:

• You need to check the product price is correct, the shipping charge, VAT, and discount codes are applied and the price the customer has to pay is the right amount. You can test this payment process by making changes to the final list of products, applying different discount coupon codes, and choosing a different region to see the change in shipping charges.
• You need to check whether the payment is processed correctly, by using all kinds of payment methods such as net banking, Credit/Debit card, PayPal, etc. You can check all these using dummy accounts and demo debit/credit card numbers. Also, you need to check whether the orders are cancelled, and the payment ID sent back.
• Check whether the invoices and emails generated after the payment process are sent.
• You need to also ensure the refund process, email, and refund receipt all are working properly.

4. Other Common Things to be Tested

• There are other common things in your e-commerce application you need to test and they include website content, webpage format, website accessibility, cookies, social buttons, adding/deleting content, removing/adding links, web standards, analytics, and making changes to shipping settings.

5. Performing Security and Vulnerability Assessments

6. Checking Compatibility with Web Browsers

7. Testing for Mobile Responsiveness

8. Checking Performance and SEO-related Things

9. Social Media Integration

How to Handle Checkboxes in Selenium

 package com.system.patternz;

import java.util.ArrayList;
import java.util.List;
import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;
import org.testng.annotations.BeforeMethod;
import org.testng.annotations.Test;
import io.github.bonigarcia.wdm.WebDriverManager;

public class Practice {
WebDriver driver;

@BeforeMethod
public void setUp() {
WebDriverManager.chromedriver().setup();
driver = new ChromeDriver();
driver.get("https://testautomationpractice.blogspot.com/");
driver.manage().window().maximize();
}

@Test(enabled = true, priority = 0, description = "how to select specific checkboxes")
public void test1() throws InterruptedException {
driver.findElement(By.id("sunday")).click();
Thread.sleep(3000);
}

@Test(enabled = true, priority = 1, description = "how to select all checkboxes")
public void test2() throws InterruptedException {
List<WebElement> list = driver.findElements(By.xpath("//*[@class='form-group'][4]//div"));
for (WebElement x : list) {
x.click();
}
}

@Test(enabled = true, priority = 2, description = "how to select multiple checkboxes by choice")
public void test3() throws InterruptedException {
ArrayList<String> list3 = new ArrayList<String>();
list3.add("Sunday");
list3.add("Wednesday");
list3.add("Saturday");
System.out.println(list3);
List<WebElement> list1 = driver.findElements(By.xpath("//*[@class='form-group'][4]//div"));
for (WebElement x : list1) {
String str = x.getText();
for (String x1 : list3) {
if (str.equals(x1)) {
x.click();
Thread.sleep(3000);
}
}
}
}

@Test(enabled = true, priority = 3, description = "how to select multiple checkboxes by choice")
public void test4() throws InterruptedException {
List<WebElement> list1 = driver.findElements(By.xpath("//*[@class='form-group'][4]//div//input"));
for (WebElement x : list1) {
String str = x.getAttribute("id");
if (str.equals("monday") || str.equals("wednesday") || str.equals("saturday")) {
System.out.println("next click");
x.click();
Thread.sleep(3000);
} else {
System.out.println("not found");
}
}
}

@Test(enabled = true, priority = 4, description = "how to select last 2 checkboxes")
public void test5() throws InterruptedException {
List<WebElement> list = driver.findElements(By.xpath("//*[@class='form-group'][4]//div"));
int totalcheckboxes = list.size();
for (int i = totalcheckboxes - 2; i < totalcheckboxes; i++) {
list.get(i).click();
}
}

@Test(enabled = true, priority = 5, description = "how to select first 2 checkboxes")
public void test6() throws InterruptedException {
List<WebElement> list = driver.findElements(By.xpath("//*[@class='form-group'][4]//div"));
int totalcheckboxes = list.size();
for (int i = 0; i < totalcheckboxes; i++) {
if (i < 2) {
list.get(i).click();
Thread.sleep(3000);
}
}
}
}

Selenium test run without using System.setProperty in the code

 package com.system.pattern;

import org.openqa.selenium.WebDriver;

import org.openqa.selenium.chrome.ChromeDriver;

import org.testng.annotations.BeforeMethod;

import org.testng.annotations.Test;

import io.github.bonigarcia.wdm.WebDriverManager;

public class Practice {

WebDriver driver;

@BeforeMethod

public void setUp() {

WebDriverManager.chromedriver().setup();

driver = new ChromeDriver();

}

@Test(description = "Selenium test run without using System.setProperty in the code")

public void test() {

driver.get("https://suriyaparithy.blogspot.com/");

}

}

Chrome version - 125.0.6422.141

Webdrivermanager version - 5.5.3

How to Easily Read Chrome Driver Files from the src/main/resources Folder

 package com.system.pattern;

import org.openqa.selenium.WebDriver;

import org.openqa.selenium.chrome.ChromeDriver;

import org.testng.annotations.Test;

public class NewTest {

WebDriver driver;

@Test(description = "chrome webdriver found under src/main/resources")

public void chrome() {

String chromeDriverPath = System.getProperty

("user.dir") + "/src/main/resources/chrome/chromedriver";

System.setProperty("webdriver.chrome.driver", chromeDriverPath);

driver = new ChromeDriver();

driver.get("https://suriyaparithy.blogspot.com/");

}

}

Get Ahead with These Real-Time Software Testing Interview Questions (Part 1)

1. What are the three types of authentication?

• Authentication is crucial to security, ensuring that only authorized users gain access to systems, applications, and data. There are three main types of authentication methods:

Something You Know:

• This type of authentication relies on information that the user knows.
• Examples: Passwords, PINs, security questions, or passphrases.
• Advantages: Easy to implement and use.
• Disadvantages: Can be vulnerable to social engineering, phishing attacks, or being guessed.

Something You Have:

• This type of authentication depends on something the user possesses.
• Examples: Physical tokens, smart cards, mobile devices, security keys, or one-time password (OTP) generators.
• Advantages: Adds a layer of security that is more difficult to breach compared to just using passwords.
• Disadvantages: Can be lost, stolen, or damaged, and may require additional hardware.

Something You Are:

• This type of authentication uses the inherent characteristics of the user.
• Examples: Biometric authentication methods such as fingerprints, facial recognition, iris scans, voice recognition, or behavioural biometrics.
• Advantages: Provides a high level of security since biometric traits are unique to individuals.
• Disadvantages: It can be more expensive to implement and may have privacy concerns; some biometric systems can be tricked or spoofed.

2. What is a critical bug?

• A critical bug is a bug that impacts a major functionality of the application. This means affecting a large area of the functionality or breaking any functionality; there is no other method to overcome this problem. The application cannot be delivered to the end user unless the critical bug is fixed.
• For example, on a shopping website like Amazon, the following bugs will be classified as critical:

            Cannot log in to your account.

            Cannot checkout.

            The system crashes after payment.

            The product's price is not displayed.

Major:

• A major defect is a defect that leads to the failure of a crucial part of the application.
• For example, on a shopping website like Amazon, the following bugs will be categorized as major:

            Search results do not match the search query.

            Cannot use debit cards during checkout. (But can use credit cards and other payment options).

            Product reviews are not displayed.

Minor:

• A minor defect is a defect that causes problems in some unimportant or niche functionality of the system.
• For example, on a shopping website like Amazon, the following bugs will be deemed minor:

            Cannot search past orders that are more than a year old.

            Cannot compare more than three products at a time.

            Thumbnails of product photos uploaded by users are unclear.

3. What are the impacts caused by a failure in white box testing?

• White-box testing is a software testing method that focuses on the internal structure of the code.
• This type of testing is often used to identify defects in the code, such as logic errors, syntax errors, and data-handling errors.
• If defects are not identified and fixed early in the development process, they can be more expensive to fix later on. This is because it may take longer to find the root cause of the defect, and the fix may require changes to more code.

4. What bugs mainly come in Web testing?

• Issues in the navigation of the application - The flow of the site is not consistent.
• Usability - The application is not user friendly and the interface is not easy to understand, or navigate and is not extractive.
• Cosmetic Issues and GUI Issues - Cross browser application does not have a consistent look and feel, and Field level validations are not working.
• Functional Issues.
• Performance issues - How much time it takes to display the page to the user.
• Load - How much load an application can handle at any point in time.
• Stress - At how much load the application will crash.
• Flow of data - Information which is entered by the user is stored in the correct format.

5. What is Usability testing in web testing?

• Designers should always remember that the experience of the user on their website must be as pleasant as possible. How the user interacts with the website is very important.
• While doing usability testing of a web application:

           Font of the fields.

           Colour of the validation messages and fields.

           Mandatory fields should be in an asterisk symbol.

           Alignment of the fields.

           Showing the Next/previous link in a data grid if the application count reaches 10.

           Navigational link.

           All pages should have a heading consistently.

           User-friendly validation messages in each and every operation.

           Size, shape and arrangements of Iframe, panel, tables, text boxes, radio buttons etc.

6. What are the typical problems in web testing?

• Security: Authentication Issues, data not encrypted, User privileges leaks, SQL injection can done, cross side scripting, cookie testing etc.
• Session Issues: Session of page not maintained.
• GUI issues: Page resize issues, alignment of page, page refresh issues, look & feel, broken links, bad hyperlinks, spelling etc.
• Pages on the website are not properly validated and do not conform to industry standards (CSS, HTML/XHTML).
• The application's business logic is not proper.
• User inputs are not properly validated.
• User inputs do not meet technical specifications.
• Error messages are not generated or are incorrect.
• Web page design (fonts, colour scheme, layout) does not meet requirements.
• Broken links.
• Feeds do not work properly.
• Pages are not accessible to the visually impaired.
• Copyright information is incorrect.
• Images have not been optimized or do not otherwise meet requirements.
• Cookies don't work properly.
• Web clients can't handle some of the messages returned by the server.
• Pages don't render properly with some operating systems and/or browsers.
• Data obtained through web pages are not captured and/or stored properly in the database.
• It takes too long for some pages to render.
• Performance lags when there are numerous simultaneous users.
• Users have inappropriate access to roles or content.
• User problems with login (password strength, failure to track login attempts, etc).
• Concurrency issues (session problems) when multiple users are on the same page and/or when a single user is on multiple windows of the same page.
• The server log does not properly track transactions.
• The website does not properly use SSL.

7. There are 3 mandatory fields and 3 optional fields: How many possible test cases can be written?

• Submit the page with empty optional fields and verify whether the validation messages are shown for optional fields.
• Each time leave any one of the optional fields, submit the page and verify whether the validation messages are shown.
• Submit the page with empty mandatory fields and verify whether the validation messages are shown for mandatory fields.
• Each time leave any one of the mandatory fields, submit the page and verify whether the validation messages are shown.

8. Examples of Severity and Priority of all combination

       Priority is how soon the issue needs to be resolved. Severity defines the impact of the issue.

• High severity low priority: Logo of the company.
• High severity high priority: Submit button of login page not working or page not displaying.
• Low severity high priority: Cosmetic error or spelling mistake on the login page. It's a small bug but has high priority as it's on the main login page.
• Low severity low priority: spelling mistakes in text of home screen.

9. What is RTM? How is it useful in testing?

• The Requirement Traceability Matrix (RTM) captures all requirements proposed by client or development team. Used to check all testcases are covered, so that no functionality should miss.

10. The exact difference between alpha and beta testing

• Alpha Testing: Pre-release testing by end-user representatives at the developer site.
• Beta Testing: Done by a selective group of users (Normal Users). For example: Apps like Yahoo Messenger, and Firefox release their beta version to users and get their feedback.

API Testing Using Postman: Part 5

 Two types of scripts in postman:

1. Pre-request script (It will run the script before execution)
2. Test script (it will run the script after execution)

Order of execution:

 Pre-request --> Request --> Response--> Test script

Execute the pre-request script and test script in 3 levels.

1. Collection level
2. Folder level
3. Request level

• If we give scripts in pre-request and test scripts at all levels. The order will be executed in the following manner.
• Collection -> Folder-> Request (until this pre-request) -> Request -> Response -> Collection -> Folder -> Test script.

Variables:

• Variables are created to reduce the effort in updating data every time. In Postman, we are also creating variables to update data every time.
• For example, some parts of the URL are common across all the requests ("https://localhost3000"). This can be stored in one variable and can be used anytime whenever we want.
• If localhost number 3000 changes also, we can update the variable, it's a one-time update and can be updated everywhere.

Types of variables:

1. Global - Accessible in Workspace
2. Collection - Accessible within the collection.
3. Environment - Accessible in all collections, but we need to switch to a particular environment.
4. Local - Accessible only within the request (Specific to Request).

API Testing Using Postman: Part 4

 Here we are validating 5 types of response in the output.

1. Status code
2. Headers
3. Cookies
4. Response time
5. Response body

• To test the above validations we have something called "Assertions" in Postman. Assertion is nothing but a validation point. To add this validation we have one library in Postman called "pm".In this, we have so many functions available. By adding some parameters to these functions we can validate the above responses.

Testing Headers:

• We can check static values present in the header.
• We are checking whether the text is present in the header as well as the text assigned to the header.

Testing Cookies:

• Every time, the cookies we get are not constant. So we are using two types of assertions. One is to check whether that cookie is present and another is text present for that cookie.

Testing Response time:

• We are checking whether the API is running in the expected time. we don't know the exact time every time, So we are giving min or max time to validate the time.

Testing Response body:

• Sometimes the response in the body is not static values, it will be dynamic sometimes. So, we are validating only the static values or content in the response body.

validating the Response body in 3 categories.

1. Validating the type of values.
2. Validating the values assigned.
3. Validating JSON Schema.

API Testing Using Postman: Part 3

HTTP vs HTTPS:

• We have 2 types of URLs. One is HTTP and the other is HTTPS.

1. HTTP(Hypertext transfer protocol) will give the data to the client without any security(without password encryption).
2. HTTPS(Hyper Text transfer protocol secure) will give the data to the client with some security (password encryption).

• URL is divided into 3 parts:

1. URL: Uniform Resource Locator
2. URI: Uniform Resource Identifier
3. URN: Uniform Resource Name

Feature & Resource:

• The feature is the term which is used in manual Testing to test some functionality. Resource is the term used in API Automation Testing referring to some functionality.

Payload: payload is the body HTTP Request and Response message.

Request payload: In the Request payload, we send the request in the request body using HTTP/HTTPS Request.

Response payload: In the response payload we will get the response in the format of HTTP Response which contains the status code, Response payload and string message.