Monday, 27 February 2023

Automation Metrics is very imp for Automation QA and SDET, if you are trying for SDET role do check out our post on SDET Job Roles & Responsibilities

In software testing, the terms defect, error, and bug are often used interchangeably, but they have slightly different meanings.

DEFECT

A defect is a flaw or deviation from the expected behavior of the software system. It can occur at any stage of the development process, and it can be caused by various factors such as coding mistakes, design issues, or testing errors. Defects are also known as faults or issues.

Example:
A software application crashes or freezes when a user enters certain input values. This could be due to an unexpected combination of user inputs that was not accounted for during testing or development.

ERROR

An error is a human mistake or an incorrect action taken by the developer or tester that leads to a defect in the software. Errors can be caused by misunderstandings, miscommunication, lack of knowledge or skill, and other factors.

Example:
A tester accidentally skips a critical test case, resulting in a defect going unnoticed until after the software is released. This could be due to a lack of understanding of the requirements or a miscommunication with the development team.

BUG

A bug is a specific type of defect that causes the software to behave in an unintended way or produce incorrect results. Bugs are typically caused by coding errors or logical mistakes in the program.

Example:
A mobile app that is supposed to allow users to upload photos crashes when the user selects a photo from their camera roll. This could be due to a coding error where the app is unable to handle the file format of the selected photo.

To summarize, an error is a mistake made by a human, which can lead to a defect, which is a flaw in the software. A bug is a specific type of defect that causes the software to behave unexpectedly or produce incorrect results.

Calculate Automation Test Metrics

To calculate Test Estimation, check the link below:
Automation Test Estimation

What are the Types of APIs ?

Gmail Automation with Cypress & JavaScript

*******************************************************************

For any doubts or career guidance, reach out to me

https://topmate.io/sidharth_shukla

********************************************************************

Do remember that knowing Linux is one of the most important aspect to work as an SDET.

Basic Linux Commands for Automation QA

****************************************

TOP 15 BDD - CUCUMBER Interview Q&A

************************************************

✍️AUTHOR: LinkedIn Profile

************************************************

Learn (API-Microservice)Testing+ Selenium UI Automation-SDET with Self Paced Videos prepared by FAANG employees and LIVE Doubt Session

*************************************************

SeleniumWebdriver Automation Testing Interview Questions:

https://automationreinvented.blogspot.com/search/label/SeleniumWebdriver

API Testing Interview Question Set:

https://automationreinvented.blogspot.com/2022/03/top-80-api-testing-interview-questions.html

DevOps Interview Q&A:

https://automationreinvented.blogspot.com/2021/11/top-11-devops-interview-questions-and.html

Kubernetes Interview Question Set

https://automationreinvented.blogspot.com/search/label/Kubernetes

Docker Interview Question Set

https://automationreinvented.blogspot.com/Docker

Linux Interview question Set

https://automationreinvented.blogspot.com/search/label/Linux

Automation Testing/SDET Framework Design

https://automationreinvented.blogspot.com/search/label/FrameworkDesign

Java Related Interview Question Set

https://automationreinvented.blogspot.com/search/label/Java

GIT Interview Question Set:

https://automationreinvented.blogspot.com/2021/09/top-40-git-interview-questions-and.html

Coding Interview Question Set:

https://automationreinvented.blogspot.com/search/label/Coding%20Questions

Mobile Testing Interview Question Set:

https://automationreinvented.blogspot.com/search/label/Mobile%20Testing

Python Interview Question Set for QAE - SDET - SDE:

https://automationreinvented.blogspot.com/search/label/Python

Wednesday, 22 February 2023

How to handle --ignore-certificate-errors in selenium?

SDET Interview Question and Answers.

Jenkins Interview Questions and Answers.

Appium Interview Questions and Answers

Selenium Interview Questions and answers.

GIT Interview Questions and Answers

In Selenium WebDriver, you can use the --ignore-certificate-errors option to ignore SSL certificate errors in ChromeDriver. This option tells ChromeDriver to ignore any SSL certificate errors that occur while navigating to a website.

Here's an example :

import org.openqa.selenium.WebDriver;

import org.openqa.selenium.chrome.ChromeDriver;

import org.openqa.selenium.chrome.ChromeOptions;

public class IgnoreCertificateErrors {

public static void main(String[] args) {

// Create ChromeOptions object

ChromeOptions options = new ChromeOptions();

// Add the --ignore-certificate-errors option to the ChromeOptions object

options.addArguments("--ignore-certificate-errors");

// Set system property for ChromeDriver

System.setProperty("webdriver.chrome.driver", "path/to/chromedriver");

// Create ChromeDriver instance with options

WebDriver driver = new ChromeDriver(options);

// Navigate to website with SSL certificate error

driver.get("https://example.com");

// Continue with the website despite the SSL certificate error

// Close the driver

driver.quit();

}

In this example, we create a ChromeOptions object and add the --ignore-certificate-errors option to it using the addArguments method. We then create a ChromeDriver instance with the options and navigate to a website with an SSL certificate error. The --ignore-certificate-errors option allows the browser to continue despite the error.

To calculate Test Estimation, check the link below:
Automation Test Estimation

What are the Types of APIs ?

Gmail Automation with Cypress & JavaScript

*******************************************************************

For any doubts or career guidance, reach out to me

https://topmate.io/sidharth_shukla

********************************************************************

Do remember that knowing Linux is one of the most important aspect to work as an SDET.

Basic Linux Commands for Automation QA

****************************************

TOP 15 BDD - CUCUMBER Interview Q&A

************************************************

✍️AUTHOR: LinkedIn Profile

************************************************

Learn (API-Microservice)Testing+ Selenium UI Automation-SDET with Self Paced Videos prepared by FAANG employees and LIVE Doubt Session

*************************************************

SeleniumWebdriver Automation Testing Interview Questions:

https://automationreinvented.blogspot.com/search/label/SeleniumWebdriver

API Testing Interview Question Set:

https://automationreinvented.blogspot.com/2022/03/top-80-api-testing-interview-questions.html

DevOps Interview Q&A:

https://automationreinvented.blogspot.com/2021/11/top-11-devops-interview-questions-and.html

Kubernetes Interview Question Set

https://automationreinvented.blogspot.com/search/label/Kubernetes

Docker Interview Question Set

https://automationreinvented.blogspot.com/Docker

Linux Interview question Set

https://automationreinvented.blogspot.com/search/label/Linux

Automation Testing/SDET Framework Design

https://automationreinvented.blogspot.com/search/label/FrameworkDesign

Java Related Interview Question Set

https://automationreinvented.blogspot.com/search/label/Java

GIT Interview Question Set:

https://automationreinvented.blogspot.com/2021/09/top-40-git-interview-questions-and.html

Coding Interview Question Set:

https://automationreinvented.blogspot.com/search/label/Coding%20Questions

Mobile Testing Interview Question Set:

https://automationreinvented.blogspot.com/search/label/Mobile%20Testing

Python Interview Question Set for QAE - SDET - SDE:

https://automationreinvented.blogspot.com/search/label/Python

Thursday, 16 February 2023

Automate Gmail Login with pytest & Selenium

SDET Interview Question and Answers.

Jenkins Interview Questions and Answers.

Appium Interview Questions and Answers

Selenium Interview Questions and answers.

GIT Interview Questions and Answers

If you are preparing for Selenium-Python Interview then also check below Q&A:
Python Interview Question & Answers Set - 01

Python Interview Q&A Set - 02

Python Interview Q&A Set - 03

If you are new to PYTHON then first check the post on How to Install Python on windows and mac?, once installation is complete then only checkout the below Q&A

To automate Gmail login with pytest, you can use the pytest framework along with the selenium package to simulate user actions on a web browser. Here are the steps you can follow:

Install the pytest and selenium packages using pip:

pip install pytest selenium

Download the appropriate driver for your browser. You can download the Chrome driver from https://sites.google.com/a/chromium.org/chromedriver/downloads. Make sure to select the version that matches the version of your browser.
Create a new Python file for your test, and import the necessary modules:

import pytest
from selenium import webdriver

Create a fixture that sets up the Selenium WebDriver instance:

@pytest.fixture
def browser():
driver = webdriver.Chrome()
yield driver
driver.quit()

This fixture creates a new Chrome driver instance before the test runs, and quits the driver after the test is finished.

Define a test that logs into Gmail using a valid username and password:

def test_login(browser):
browser.get("https://mail.google.com")
email_input = browser.find_element_by_css_selector("input[type='email']")
email_input.send_keys("your-email-address")
next_button = browser.find_element_by_css_selector("button[jsname='LgbsSe']")
next_button.click()
password_input = browser.find_element_by_css_selector("input[type='password']")
password_input.send_keys("your-password")
signin_button = browser.find_element_by_css_selector("button[jsname='LgbsSe']")
signin_button.click()
assert "Gmail" in browser.title

This test navigates to the Gmail login page, enters the email address and password, and clicks the "Next" and "Sign in" buttons. It then checks if the Gmail inbox is displayed by checking if the page title contains the string "Gmail".

Run the test using pytest:

pytest test_gmail_login.py

This will launch the Chrome browser and run the test. If the test passes, you should see a message indicating that one test has passed. If the test fails, you should see an error message indicating the reason for the failure.

How to use Selenium with a remote webdriver in Python?

*******************************************************************

For any doubts or career guidance, reach out to me

https://topmate.io/sidharth_shukla

********************************************************************

Do remember that knowing Linux is one of the most important aspect to work as an SDET.

Basic Linux Commands for Automation QA

****************************************

TOP 15 BDD - CUCUMBER Interview Q&A

************************************************

✍️AUTHOR: LinkedIn Profile

************************************************

Learn (API-Microservice)Testing+ Selenium UI Automation-SDET with Self Paced Videos prepared by FAANG employees and LIVE Doubt Session

*************************************************

SeleniumWebdriver Automation Testing Interview Questions:

https://automationreinvented.blogspot.com/search/label/SeleniumWebdriver

API Testing Interview Question Set:

https://automationreinvented.blogspot.com/2022/03/top-80-api-testing-interview-questions.html

DevOps Interview Q&A:

https://automationreinvented.blogspot.com/2021/11/top-11-devops-interview-questions-and.html

Kubernetes Interview Question Set

https://automationreinvented.blogspot.com/search/label/Kubernetes

Docker Interview Question Set

https://automationreinvented.blogspot.com/Docker

Linux Interview question Set

https://automationreinvented.blogspot.com/search/label/Linux

Automation Testing/SDET Framework Design

https://automationreinvented.blogspot.com/search/label/FrameworkDesign

Java Related Interview Question Set

https://automationreinvented.blogspot.com/search/label/Java

GIT Interview Question Set:

https://automationreinvented.blogspot.com/2021/09/top-40-git-interview-questions-and.html

Coding Interview Question Set:

https://automationreinvented.blogspot.com/search/label/Coding%20Questions

Mobile Testing Interview Question Set:

https://automationreinvented.blogspot.com/search/label/Mobile%20Testing

Python Interview Question Set for QAE - SDET - SDE:

https://automationreinvented.blogspot.com/search/label/Python

Tuesday, 14 February 2023

What are the Automation Test Metrics?

SDET Interview Question and Answers.

Jenkins Interview Questions and Answers.

Appium Interview Questions and Answers

Selenium Interview Questions and answers.

GIT Interview Questions and Answer

Automation Metrics is very imp for Automation QA and SDET, if you are trying for SDET role do check out our post on SDET Job Roles & Responsibilities

As automation testing becomes increasingly popular, it's essential to have a set of reliable metrics to track and measure its effectiveness. In this post, let's take a closer look at some common types of automation test metrics:

Test Coverage:
This metric measures the percentage of code or features covered by automated tests. It helps to identify areas where testing is lacking, enabling teams to add tests to ensure better coverage.

Test Coverage = (Number of Features Covered by Tests ÷ Total Number of Features in the Application) x 100
For example, let's say your application has 10,000 lines of code, and your automated tests cover 7,500 lines of code. To calculate the test coverage, you would plug in these values into the formula:

Test Coverage = (7,500 ÷ 10,000) x 100 = 75%

So, in this example, the test coverage is 75%, indicating that 75% of the application's code is covered by the automated tests.
Tracking test coverage over time can help you identify areas where your tests may be lacking and prioritize efforts to improve test coverage in those areas. It's important to note that test coverage alone is not enough to ensure that your tests are effective, but it is an important metric to track to ensure that your tests are comprehensive.
Test Execution Time:
This metric measures how long it takes to execute automated tests. By tracking execution time, teams can identify tests that take too long to run and optimize them accordingly.
Test Failure Rate:
This metric tracks the number of failed tests and helps teams to identify the areas where defects are occurring most frequently. By analyzing failure patterns, teams can focus on addressing the underlying issues.

Test Failure Rate = (Number of Failed Tests ÷ Total Number of Tests Executed) x 100
For example, let's say you executed a total of 100 automated tests and 10 of those tests failed. To calculate the test failure rate, you would plug in these values into the formula:

Test Failure Rate = (10 ÷ 100) x 100 = 10%

So, in this example, the test failure rate is 10%, indicating that 10% of the tests executed during the period resulted in failures.
Tracking the test failure rate over time can help you identify trends and patterns in your testing process. High failure rates may indicate that there are issues with the application code, or that the tests themselves need to be improved. Conversely, low failure rates may suggest that the tests are not comprehensive enough or that there are issues with the testing infrastructure.
Test Effectiveness:
This metric measures how effective automated tests are in identifying defects. It's important to track this metric to ensure that the tests are providing the expected results.

Test Effectiveness = (Number of Defects Found by Tests ÷ Total Number of Defects Found) x 100

For example, let's say you discovered a total of 100 defects during your testing process, and your automated tests found 70 of those defects. To calculate the test effectiveness, you would plug in these values into the formula:

Test Effectiveness = (70 ÷ 100) x 100 = 70%

So, in this example, the test effectiveness is 70%, indicating that 70% of the defects were found by the automated tests.

5. Defect Leakage:

This metric tracks the number of defects that are missed by automated tests and are discovered later in the development process. It helps teams to identify areas where tests need to be improved or enhanced.

Defect Leakage = (Number of Defects Found after Release ÷ Total Number of Defects Found) x 100

For example, let's say you discovered a total of 100 defects during your testing process. After the product was released, you found 10 additional defects that were not caught during testing. To calculate the defect leakage, you would plug in these values into the formula:
Defect Leakage = (10 ÷ 100) x 100 = 10%
So, in this example, the defect leakage rate is 10%, indicating that 10% of the defects were not caught during the testing process and were found after the product was released.
It's important to track defect leakage to identify areas where your testing process may be lacking and to make improvements to prevent defects from leaking into production.

These are just a few examples of the types of automation test metrics that can help teams to monitor and measure their testing efforts. By using these metrics, teams can identify areas of improvement, optimize their testing processes, and ultimately deliver better quality products to their customers. #automationtesting #testmetrics #qualityassurance

To calculate Test Estimation, check the link below:
Automation Test Estimation

What are the Types of APIs ?

Gmail Automation with Cypress & JavaScript

*******************************************************************

For any doubts or career guidance, reach out to me

https://topmate.io/sidharth_shukla

********************************************************************

Do remember that knowing Linux is one of the most important aspect to work as an SDET.

Basic Linux Commands for Automation QA