#AskRaghav

00:00 Intro
01:15 Scenario 1:
You're automating a login feature for a web application
How will you handle dynamic elements like Captcha or OTP fields in your automation script?
Answer:
To handle dynamic elements like Captcha or OTP fields, I would consider the following solutions:
We can request the development team to disable Captcha and OTP in the test environment to make automation feasible
Add a hook to allow tests to bypass the CAPTCHA
We can work closely with the development team to set a predefined OTP for the test environment
________________________________________________
03:45 Scenario 2:
During test automation, you encounter an element that doesn't have unique attributes. How would you locate and interact with such an element?
Answer:
Use XPath with the contains() function
Use CSS selectors with the contains() function
Use the element's text content
Use the element's position
Use a combination of the above methods
Discuss with Developers
________________________________________________
05:43 Scenario 3:
You're testing an e-commerce website, and you need to automate a scenario where a user adds multiple products to their cart. How would you design and execute this test case efficiently?
Answer:
To efficiently automate adding multiple products to a cart:
Create a test data set with various products to add
Use a loop in your automation script to iterate through the products in the data set.
For each product, navigate to the product page, click the "Add to Cart" button, and verify the item is added
Repeat the loop for each product
After all products are added, go to the shopping cart page to verify the correct items are listed
Ensure the test environment is reset between test iterations to avoid interference
________________________________________________
07:30 Scenario 4:
In an agile development environment, how do you ensure that your automation scripts remain up-to-date as the application evolves with frequent changes?
Answer:
To keep automation scripts up-to-date in an agile environment:
Collaborate: communication with developers & testers to stay informed about changes
Version Control: Store automation scripts in VCS like Git to track changes and easily roll back if needed
Continuous Integration: Integrate automation into the CI/CD pipeline to run tests automatically with each code change
Regular Maintenance: Schedule regular script reviews and updates to align with the evolving application
Use Page Object Model: Implement a Page Object Model to separate UI elements from test logic, making updates more manageable
Automated Test Data Generation: Automate the creation of test data or use data generation tools to adapt to changes
Use Dynamic Locators: Employ dynamic locators that can adapt to UI changes, such as relative XPath or CSS selectors
Monitor Logs: Keep an eye on test execution logs for failures caused by changes, and update scripts accordingly
________________________________________________
12:50 Outro
Every Like & Subscription gives me great motivation to keep working for you
You can support my mission for education by sharing this knowledge and helping as many people as you can
If my work has helped you, consider helping any animal near you, in any way you can
Never Stop Learning
Raghav Pal
All Free Tutorials 🟢 AutomationStepByStep.com/
---

[@bestcricketbowling9947]

Thanks for this type of video, great work, keep it up❤️

[@RaghavPal]

Thank you! Will do Shekhar

[@SineQuaNon1]

Many thanks. As always, very useful video. Can you do more of this kind of videos.

[@RaghavPal]

Sure thing!

[@user-qf3ii6wu2x]

Awesome!

[@RaghavPal]

Thanks Stefanini

[@shilpav2882]

Please explain about 1.challenges faced during automation 2.what to do if automation script fails after few days of successful test execution

[@RaghavPal]

Shilpa, I will take these questions in the coming episodes of #AskRaghav

[@kristy904]

Hello Raghav , thank you so much for this videos ! You explained very well ! Can you please also explain about automated test data generation and how to do it ? thank you.

[@RaghavPal]

Kinjal Let me know what tool/platform you are using.. I will explain accordingly

[@kristy904]

I was using javascript/cypress for automating web application ! Recently , for my personal project , I also used selenium/python for e-commerce website.@@RaghavPal

[@kristy904]

I was using cypress /javascript for automating web application in previous role ! recently , I used selenium /python for my personal project to automate e commerce website!

[@RaghavPal]

Automated test data generation is a process that involves creating a substantial volume of realistic test data that can be used to test the functionality and performance of a software application. The goal is to generate data that closely mimics production data in terms of structure and variability, which helps in identifying potential issues in the software. Here's a high-level overview of how automated test data generation can be done: 1. Identify the Test Data Requirements: Determine what kind of data the application requires for testing. This includes understanding the data types, formats, and the relationships between different data entities. 2. Choose a Test Data Generation Method: There are several methods for generating test data, including: - Manual Test Data Creation: Testers create data manually based on their understanding of the application's requirements. - Automated Test Data Generation Tools: These tools can automatically generate test data based on predefined rules and patterns. Some popular tools include DATPROF, EMS Data Generator, and Redgate SQL Data Generator⁹. - Back-end Data Injection: This involves writing SQL queries or scripts to insert data directly into the database. 3. Generate the Test Data: Using the chosen method, generate the test data that will be used for testing. Ensure that the data covers various test scenarios, including edge cases. 4. Validate the Test Data: Check the generated data to ensure it meets the requirements and is suitable for the test cases. 5. Use the Test Data in Test Cases: Incorporate the generated data into your test cases and execute them to validate the application's behavior. 6. Analyze Test Results: After testing, analyze the results to identify any defects or improvements that can be made in the application. Automated test data generation can significantly reduce the time and effort required to create test data, while also improving the quality and coverage of testing. It's important to choose the right tools and methods that align with the specific needs of your project. ..

[@kristy904]

@@RaghavPal Thank you so much for this explanation Raghav !

[@kristy904]

I am new to your channel ! I also have a doubt about test case creation , in my previous roles , I have been creating a rough test cases and testing it so far ! even when writing automation tests ,I was not creating it properly ! So can you please suggest how can I implement that in better way which can be shared after with team ! Thank you !

[@RaghavPal]

Creating effective and shareable test cases is crucial for successful testing. Let's explore some best practices for writing test cases that are clear, concise, and useful for both manual and automated testing: 1. Understand the Feature or Requirement: - Before writing test cases, thoroughly understand the feature, functionality, or requirement you are testing. - Discuss with stakeholders, review documentation, and clarify any doubts. 2. Identify the Feature to Be Tested: - Clearly identify the specific feature or functionality you want to test. - For example, if you're testing a login page, focus on that particular feature. 3. Define Test Scenarios: - Identify different scenarios to verify all aspects of the feature. - Consider both positive (valid input) and negative (invalid input) scenarios. - For a login feature, scenarios might include: - Successful login with valid credentials - Failed login with incorrect credentials - Account lockout after multiple failed attempts 4. Write Clear and Concise Test Steps: - Each test case should have a unique identifier (e.g., TC001, TC002). - Use a descriptive title that summarizes the purpose of the test case. - Write step-by-step instructions for executing the test. - Include preconditions (e.g., "User is on the login page") and expected results (e.g., "User is redirected to the dashboard"). 5. Use a Standard Format or Template: - Follow industry standards such as IEEE 829 or ISTQB for test case formats. - Use a consistent template for all test cases within your team. - Include fields like test ID, description, steps, expected results, and priority. 6. Prioritize Test Cases: - Prioritize test cases based on risk, business impact, and criticality. - Focus on high-priority features first. 7. Link Test Cases to Requirements or User Stories: - Associate each test case with the corresponding requirement or user story. - This helps track coverage and ensures alignment with project goals. 8. Review and Validate Test Cases: - Review test cases with team members to ensure clarity and correctness. - Validate that each test case covers the intended functionality. 9. Version Control and Shareability: - Store test cases in a version-controlled repository (e.g., Git). - Use a test management tool (e.g., TestRail, Jira) to organize, share, and track test cases. 10. Update Test Cases Regularly: - As the application evolves, update test cases to reflect changes. - Maintain a balance between reusability and specificity. Remember, well-structured test cases improve collaboration, reduce ambiguity, and enhance overall testing efficiency. Share them with your team, gather feedback, and continuously improve your testing process .

[@kristy904]

Thank you so much Raghav for quick response ! You explained very well ! I would really appreciate if you can share a video if you already have created some testcase using testrail ! It would be really helpful !@@RaghavPal

[@RaghavPal]

Not yet done on TestRail

[@andywolan]

For Scenario #1, we got dev to implement a flag to toggle OTP off and on in the test environment after we warned management it would cause problems with performance testing.

[@RaghavPal]

Good, I also answered this ques here - kzbin.info/www/bejne/h3q8k6VuZsl9fbMsi=m4myGuvDGGzcCCY7

[@romeemperor]

Hi, I’m in the market now in the US. What do you think about market in the US for SDET/SQA roles? Thank you Raghav!

[@RaghavPal]

Marcus The market for SDET/SQA roles in the US is strong and growing. According to the U.S. Bureau of Labor Statistics, software quality assurance (SQA) analyst employment is projected to grow 22% from 2020 to 2030, much faster than the average for all occupations. This growth is being driven by the increasing demand for software applications and the need to ensure that they are of high quality. SDETs and SQAs play a critical role in the software development process. They are responsible for testing software applications to identify and fix defects before they are released to users. This helps to ensure that the software is reliable, secure, and meets the needs of its users. SDETs and SQAs are in high demand in the US, and there are many opportunities for qualified candidates. According to Indeed, the average salary for an SDET in the US is $118,000 per year. The average salary for an SQA in the US is $102,000 per year. The job market for SDETs and SQAs is especially strong in major tech hubs like San Francisco, New York City, and Seattle. However, there are also many opportunities in other parts of the country. Here are some tips for breaking into the SDET/SQA field in the US: * Get a degree in computer science or a related field. * Take courses in software testing and quality assurance. * Gain experience in software testing by working on personal projects or contributing to open source projects. * Get certified in software testing by an organization such as the Association for Software Testing and Quality Assurance (ASTQB). * Network with other SDETs and SQAs at industry events and online forums. If you are interested in a career in SDET/SQA, the US is a great place to start. There are many opportunities for qualified candidates, and the job market is expected to grow in the coming years.

[@romeemperor]

Thank you@@RaghavPal

[@raghuchebolu7913]

Sir Namaste🙏...I have doubt irrelevant to this video........my ques is " what is salesforce automation " and is this also one type of testing ...? what is the scope of this testing...can i switch from selenium automation to salesforcce automation...? Thanks in advance

[@RaghavPal]

Raghu Salesforce automation is the use of software tools and scripts to automate tasks and processes within the Salesforce platform. This can include tasks such as: * Creating and updating accounts, leads, and opportunities * Managing tasks and events * Generating reports * Sending emails * Integrating Salesforce with other systems Salesforce automation can help businesses to improve efficiency, reduce errors, and streamline their operations. Salesforce automation testing is a type of software testing that focuses on testing the functionality of Salesforce automation scripts and processes. This type of testing is important to ensure that Salesforce automation is working as intended and that it is not introducing any errors into the Salesforce system. The scope of Salesforce automation testing can vary depending on the specific needs of the business. However, some common areas of focus include: * Testing the accuracy and completeness of data being processed by Salesforce automation * Testing the functionality of Salesforce automation scripts in different scenarios and conditions * Testing the performance of Salesforce automation scripts under load * Testing the security of Salesforce automation scripts and processes Switching from Selenium automation to Salesforce automation is possible, but it will require learning new skills and knowledge. Selenium is a general-purpose web automation framework, while Salesforce automation is specific to the Salesforce platform. If you are interested in switching to Salesforce automation, there are a few things you can do to prepare: * Take a Salesforce automation training course * Learn about the Salesforce API * Get involved in the Salesforce community * Start by automating simple tasks and processes, and gradually work your way up to more complex ones There is a high demand for Salesforce automation skills, so switching to this field could be a good career move.

[@rajeshrao5099]

How raghav please let me know how to convert test report (extent) to CSV for each automation run .I searched all Google and youtube but I didn't get any solution. Please help me.I am using Rest Assured framework with TestNG

[@RaghavPal]

Rajesh To convert a test report (extent) to CSV for each automation run using the Rest Assured framework with TestNG, you can use the following steps: 1. Create a new class called `ExtentReporter`. This class will be responsible for generating the extent report and converting it to CSV. 2. In the `ExtentReporter` class, add the following imports: ``` import com.aventstack.extentreports.ExtentReports; import com.aventstack.extentreports.model.Report; import com.aventstack.extentreports.reporter.csv.CSVReporter; import java.io.File; import java.io.FileWriter; import java.io.IOException; ``` 3. Create a method called `generateCSVReport()` in the `ExtentReporter` class. This method will take the extent report as input and generate a CSV report. The following is a sample implementation of the `generateCSVReport()` method: ``` public static void generateCSVReport(ExtentReports extentReports) throws IOException { // Create a new CSVReporter object CSVReporter csvReporter = new CSVReporter("extent-report.csv"); // Add the CSVReporter object to the extent report extentReports.attachReporter(csvReporter); // Flush the extent report extentReports.flush(); } ``` 4. In your TestNG test class, create an instance of the `ExtentReporter` class and call the `generateCSVReport()` method after the test has finished running. The following is a sample implementation of this: ``` public class MyTest extends TestNG { private ExtentReporter extentReporter; @BeforeClass public void beforeClass() { // Create a new ExtentReports object ExtentReports extentReports = new ExtentReports(); // Initialize the extent reporter this.extentReporter = new ExtentReporter(); extentReporter.generateCSVReport(extentReports); } @Test public void test() { // Perform the test } @AfterClass public void afterClass() throws IOException { // Flush the extent report this.extentReporter.generateCSVReport(extentReports); } } ``` 5. Run your TestNG test suite. This will generate a CSV report called `extent-report.csv` in the same directory as your test class. The CSV report will contain the following information: * Test name * Test status (pass/fail) * Test execution time * Test start time * Test end time * Test description * Test exceptions (if any) You can use this CSV report to analyze your test results and identify any areas that need improvement.

[@rajeshrao5099]

Hi @@RaghavPal thanks for your response i tried implementing same in my code but CSV import package is not recognizing. Here is my code sample .Please let me know what i need to do for CSV importing package .Also i am using latest extent spark report for my framework. Here error is :The import com.aventstack.extentreports.reporter.csv cannot be resolved import java.io.IOException; import org.testng.ITestResult; import org.testng.annotations.AfterMethod; import org.testng.annotations.AfterTest; import org.testng.annotations.BeforeMethod; import org.testng.annotations.BeforeTest; import com.aventstack.extentreports.ExtentReports; import com.aventstack.extentreports.ExtentTest; import com.aventstack.extentreports.Status; import com.aventstack.extentreports.markuputils.ExtentColor; import com.aventstack.extentreports.markuputils.MarkupHelper; import com.aventstack.extentreports.reporter.ExtentSparkReporter; import com.aventstack.extentreports.reporter.configuration.Theme; import com.aventstack.extentreports.model.Report; import com.aventstack.extentreports.reporter.csv.CSVReporter; import io.restassured.RestAssured; import java.io.File; import java.io.FileWriter; public class TestBase { public ExtentSparkReporter spark; public ExtentReports extent; public ExtentTest logger; public ConfigProperties config; @BeforeTest public void startReport() { extent = new ExtentReports(); spark = new ExtentSparkReporter(System.getProperty("user.dir") + "path"); extent.attachReporter(spark); extent.setSystemInfo("Host Name", " "); extent.setSystemInfo("Environment", " "); extent.setSystemInfo("User Name", " "); spark.config().setDocumentTitle(""); // Name of the report spark.config().setReportName(" "); // Dark Theme spark.config().setTheme(Theme.STANDARD); } @BeforeMethod public void connectServer() { config = new ConfigProperties(); RestAssured.baseURI = config.getBearerURL(); } @AfterMethod public void getResult(ITestResult result) throws Exception { if (result.getStatus() == ITestResult.FAILURE) { // MarkupHelper is used to display the output in different colors logger.log(Status.FAIL, MarkupHelper.createLabel(result.getName() + " - Test Case Failed", ExtentColor.RED)); logger.log(Status.FAIL, MarkupHelper.createLabel(result.getThrowable() + " - Test Case Failed", ExtentColor.RED)); } else if (result.getStatus() == ITestResult.SKIP) { logger.log(Status.SKIP, MarkupHelper.createLabel(result.getName() + " - Test Case Skipped", ExtentColor.ORANGE)); } else if (result.getStatus() == ITestResult.SUCCESS) { logger.log(Status.PASS, MarkupHelper.createLabel(result.getName() + " Test Case PASSED", ExtentColor.GREEN)); } } @AfterTest public void generateCSVReport(ExtentReports extent) { CSVReporter csvReport=new CSVReporter("extent-report.csv"); extent.attachReporter(csvReport); extent.flush(); } } Error in TestNG class as its not recognising the method written in extentreporter class TestNg class import org.testng.annotations.AfterClass; import org.testng.annotations.BeforeClass; import org.testng.annotations.Test; import com.aventstack.extentreports.ExtentReports; import com.aventstack.extentreports.reporter.ExtentSparkReporter; public class xyz { private ExtentReports extent; @BeforeClass public void beforeClass() { ExtentReports extent=new ExtentReports(); this.spark= new ExtentSparkReporter(); spark.generateCSVReport(extent); } @Test public void xyz() { } @AfterClass public void afterClass()throws IOException{ this.spark.generateCSVReport(extent); } pom .xml io.rest-assured rest-assured 5.0.0 test org.testng testng 7.7.0 test org.apache.logging.log4j log4j-core 2.21.0 com.aventstack extentreports 5.0.9 com.googlecode.json-simple json-simple 1.1.1 org.json json 20230618 com.opencsv opencsv 5.8 org.apache.commons commons-csv 1.10.0 org.apache.logging.log4j log4j-slf4j2-impl 2.21.0

[@RaghavPal]

The error message "The import com.aventstack.extentreports.reporter.csv cannot be resolved" indicates that the Rest Assured framework is unable to find the CSV import package. This is because the CSV import package is not part of the Rest Assured framework. It is part of the ExtentReports framework. To resolve this error, you need to add the ExtentReports dependency to your project. You can do this by adding the following Maven dependency to your pom.xml file: ```xml com.aventstack extentreports 5.0.9 ``` Once you have added the ExtentReports dependency, you should be able to import the CSV import package: ```java import com.aventstack.extentreports.reporter.csv.CSVReporter; import java.io.IOException; ``` **Note:** The latest version of ExtentReports is 5.0.9. You may need to update your version of ExtentReports to resolve this error. Here is an example of how to use the CSV import package to import a CSV file into your Rest Assured test cases: ```java import com.aventstack.extentreports.reporter.csv.CSVReporter; import java.io.IOException; public class CSVImportExample { @Test public void testImportCSV() throws IOException { CSVReporter reporter = new CSVReporter("report.csv"); // Import the CSV file reporter.importCSV("data.csv"); // Generate the report reporter.flush(); } } ``` This code will import the CSV file `data.csv` and generate the report `report.csv`. I hope this helps

[@user-uz4oj5mo7l]

Hello sir how to automate web alert box

[@RaghavPal]

Pabitra To automate a web alert box with Selenium, you can use the following steps: 1. Wait for the alert box to appear. You can do this using the `ExpectedConditions.alertIsPresent()` method. 2. Get the text of the alert box. You can do this using the `Alert.getText()` method. 3. Accept or dismiss the alert box. You can do this using the `Alert.accept()` or `Alert.dismiss()` methods. The following code shows how to automate a web alert box with Selenium Java: ```java import org.openqa.selenium.Alert; import org.openqa.selenium.WebDriver; import org.openqa.selenium.chrome.ChromeDriver; import org.openqa.selenium.support.ui.ExpectedConditions; import org.openqa.selenium.support.ui.WebDriverWait; public class AutomateAlertBox { public static void main(String[] args) { WebDriver driver = new ChromeDriver(); // Wait for the alert box to appear WebDriverWait wait = new WebDriverWait(driver, 10); Alert alert = wait.until(ExpectedConditions.alertIsPresent()); // Get the text of the alert box String alertText = alert.getText(); // Accept the alert box alert.accept(); // Close the browser driver.quit(); } } ``` You can also use the `Alert` class to send text to the alert box. To do this, you can use the `Alert.sendKeys()` method. The following code shows how to automate a web alert box with Selenium Java and send text to it: ```java import org.openqa.selenium.Alert; import org.openqa.selenium.WebDriver; import org.openqa.selenium.chrome.ChromeDriver; import org.openqa.selenium.support.ui.ExpectedConditions; import org.openqa.selenium.support.ui.WebDriverWait; public class AutomateAlertBox { public static void main(String[] args) { WebDriver driver = new ChromeDriver(); // Wait for the alert box to appear WebDriverWait wait = new WebDriverWait(driver, 10); Alert alert = wait.until(ExpectedConditions.alertIsPresent()); // Send text to the alert box alert.sendKeys("My text"); // Accept the alert box alert.accept(); // Close the browser driver.quit(); } } ``` I hope this helps

[@anushabasavaraj8458]

Hello Raghav… how to handle pop ups when we don’t know when they occurs in the applications while running the test scripts…… I have answered like we have to create if condition to check for any pop up before performing any steps, then if pop up occurs dismiss it Then go for next step… but my interviewer told that is not ideal solution… Could u please help me for this question…

[@RaghavPal]

Anusha Your interviewer is right, creating an if condition to check for a popup is not the ideal solution to handle popups in Selenium automation. This is because it is not always possible to predict when a popup will occur, and even if you can, it can make your test code cluttered and difficult to read. A better approach is to use a *WebDriverWait* object to wait for the popup to appear before dismissing it. This will allow your test code to continue executing even if the popup does not appear immediately. Here is an example of how to handle popups using a WebDriverWait object: ```python import time from selenium import webdriver driver = webdriver.Chrome() driver.get("example.com") # Wait for the popup to appear wait = WebDriverWait(driver, 10) popup = wait.until(lambda driver: driver.find_element_by_class_name("popup")) # Dismiss the popup popup.dismiss() # Continue with the test ``` This code will wait for the popup to appear for up to 10 seconds. If the popup does not appear within 10 seconds, the test will fail. Once the popup appears, the code will dismiss it and continue executing the test. You can also use a WebDriverWait object to wait for the popup to disappear before continuing with the test. This is useful if you need to perform any actions on the popup before it disappears. Here is an example of how to wait for a popup to disappear before continuing with the test: ```python import time from selenium import webdriver driver = webdriver.Chrome() driver.get("example.com") # Wait for the popup to appear wait = WebDriverWait(driver, 10) popup = wait.until(lambda driver: driver.find_element_by_class_name("popup")) # Wait for the popup to disappear wait.until_not(lambda driver: driver.find_element_by_class_name("popup").is_displayed()) # Continue with the test ``` This code will wait for the popup to appear for up to 10 seconds. If the popup does not appear within 10 seconds, the test will fail. Once the popup appears, the code will wait for it to disappear before continuing with the test. I hope this helps

[@anushabasavaraj8458]

@@RaghavPal thank you Raghav.. it was very nice explanation 👍🏻 for selenium Java can we use below code for the same... WebDriverWait wait=new WebDriverWait(getDriver(), Duration.ofSeconds(10)); //WebElement popUp=wait.until(ExpectedConditions.visibilityOf(getDriver().findElement(By.className("popup")))); Alert alert=wait.until(ExpectedConditions.alertIsPresent()); if(alert!=null) { alert.dismiss(); }else { // proceed with the next steps }

[@RaghavPal]

Yes, the code you have provided can be used to wait for a popup to appear before dismissing it in Selenium Java.