Soumya Ranjan Dash

Testing will never go out of fashion!!! In the past few years, we have seen various organisations cutting down their QA teams by shifting the onus of quality towards developers instead. However a lot of teams have found this approach counterproductive due to steap rise in number of prod issues and are revamping their Quality teams. It's good to have developers who can think from a quality standpoint, but this can never replace the need of Quality experts. #Testing #SoftwareEngineering #QualityAndDev

31

some feedback: 1. implicit waits are a bad practice as they do not go well with explicit waits 2. static driver is a bad practice as it conflicts with running tests in parallel 3. logging info to file/console is not useful; if you have 100 tests running in parallel, all the logging will be meaningless 4. using a main() method is a bad idea in a selenium project; use unit tests instead 5. try/catch used in the performTest() method is a bad idea as it ignores the exception (does nothing about it); also catch clause should use a specific exception instead of Exception 6. there is no synchronization before finding the element; if the page is slow, finding the element will fail. https://lnkd.in/gcqtETFa

19

📌 Frequently Asked Selenium Interview Question: 💡 Q: Where have you used collection in your Selenium automation project? 📝 Answer: Collections in Java are highly versatile and are extensively used in Selenium automation projects for efficient data handling. Below are some common scenarios where I utilized collections: 1️⃣ Storing Web Elements: Used List<WebElement> to store multiple web elements like options in a dropdown or links in a webpage for iteration and validation. Example: List<WebElement> links = driver.findElements(By.tagName("a")); for (WebElement link : links) { System.out.println(link.getText()); } 2️⃣ Handling Test Data: Utilized HashMap to store key-value pairs for managing test data dynamically during runtime. Example: HashMap<String, String> testData = new HashMap<>(); testData.put("username", "test_user"); testData.put("password", "test_pass"); 3️⃣ Dynamic Table Validation: Used ArrayList to store dynamic rows and columns data fetched from web tables for validation. Example: List<String> rowData = new ArrayList<>(); List<WebElement> rows = driver.findElements(By.xpath("//table/tbody/tr")); for (WebElement row : rows) { rowData.add(row.getText()); } 4️⃣ Managing Wait Conditions: Implemented Set<String> to handle unique window handles during multi-tab automation. Example: Set<String> windowHandles = driver.getWindowHandles(); for (String handle : windowHandles) { driver.switchTo().window(handle); } Collections simplify data management and enhance code reusability, making automation scripts efficient and robust. 📢 Share your experiences! How have you used collections in your projects? Let’s discuss and learn from each other! #java #collection #interviewQuestion #automation #QA

10

1 Comment

 Handling Alerts, Pop-Ups, and iFrames in Selenium : 📌 Alerts and Pop-Ups 1. Switch to the Alert Use driver.switchTo().alert() to grab control. This simple command lets us handle pop-ups by either accepting or dismissing them. Alert alert = driver.switchTo().alert(); alert.accept(); // or alert.dismiss(); 2. Fetching Alert Text Sometimes, we need to verify the alert text. alert.getText() retrieves it, which can be crucial for validation. 3. Send Data in Alerts For prompts that require input, use alert.sendKeys("input"). 📌 Handling iFrames iFrames require switching focus, or Selenium will have trouble finding elements within them. Here’s what works best: 1. Switch by Index, Name, or WebElement By Index: driver.switchTo().frame(0); By Name/ID: driver.switchTo().frame("frameName"); By WebElement: driver.switchTo().frame(driver.findElement(By.id("frameID"))); 2. Returning to Main Content After completing actions within the iframe, switch back to the main content with driver.switchTo().defaultContent() to avoid future errors. 3. Nested iFrames Complex sites often have iframes within iframes. First, switch to the parent iframe, then navigate to the inner one: driver.switchTo().frame("outerFrame"); driver.switchTo().frame("innerFrame"); Note: Always check your application’s DOM structure to understand the hierarchy of iframes, especially when dealing with complex web applications.   #Selenium #TestAutomation #SDET #SoftwareTesting #QualityAssurance #CodingTips #WebTesting #AutomationScripts

31

#Selenium #Training #New #Batch Register : https://t.ly/kRNPk Struggling with dynamic elements in Selenium? Dealing with dynamic elements in web applications can be tricky, especially when elements frequently change their IDs, classes, or positions. Here's a more detailed approach I follow to handle them effectively : 1. **Use XPath Axes (following-sibling, preceding-sibling, ancestor, etc.): When an element’s attributes like ID or class change dynamically, using **XPath axes** helps identify elements based on their relative position to a stable element. For example, if an element’s ID is dynamic, but it is always next to a static label or button, you can use `following-sibling::` or `preceding-sibling::` to locate it in relation to a more stable element. Example: ```python //label[text()='Username']/following-sibling::input ``` This selects the input field that follows the label "Username," making the locator more stable even if the input field's attributes change. 2. **CSS Selectors for Partial Matches:** If you can't rely on IDs or classes because they are dynamic, **CSS selectors** with partial matches are a good option. For example, use `^=`, `*=` or `$=` to match the start, middle, or end of a dynamic class or attribute. ```python driver.find_element(By.CSS_SELECTOR, "div[class^='dynamic-part-']") ``` 3. **Dynamic Attributes Using Contains():** For elements that have dynamic attributes, using `contains()` in XPath can help capture the portion of the attribute that remains consistent, even if part of the attribute is dynamically generated. ```python //div[contains(@class, 'partial-static-class')] ``` 4. **Handling Delays with Explicit Waits:** Dynamic elements often load asynchronously, which can lead to stale element exceptions. Using **explicit waits** with conditions like `visibilityOfElementLocated()` ensures that your test waits for the element to be fully loaded before interacting with it. ```python WebDriverWait(driver, 10).until(EC.visibility_of_element_located((By.XPATH, "//input[@id='dynamic']"))) ``` 5. **Avoid Over-Reliance on Absolute XPaths:** Absolute XPaths (`/html/body/...`) are more likely to break with UI changes, while **relative XPaths** (`//tagname`) are much more flexible and maintainable. By combining these techniques, you can create robust and resilient locators that adapt to dynamic web pages, significantly reducing test failures due to UI changes. Thanks Prisha Yadav

100

5 Comments

Title: Understanding the Difference Between Cypress and Selenium In the world of web testing, Cypress and Selenium are two of the most widely used frameworks for automating browser interactions. Both serve similar purposes but differ significantly in their design, features, and capabilities. In this article, we’ll explore the key differences to help you choose the right tool for your project. What is Selenium? Selenium is a long-established, open-source tool that allows for web application automation across multiple browsers and platforms. It supports a wide range of programming languages, including Java, Python, C#, JavaScript, and Ruby. Selenium is versatile and works with all major browsers (Chrome, Firefox, Safari, Internet Explorer, and Edge). Key features of Selenium: Multi-language support (Java, Python, C#, Ruby, etc.) Cross-browser compatibility (Chrome, Firefox, Edge, etc.) Integration with frameworks like TestNG, JUnit, and Mocha. What is Cypress? Cypress is a newer tool focused on providing fast, reliable testing for modern JavaScript frameworks like React, Angular, and Vue. Unlike Selenium, Cypress runs directly inside the browser, offering a faster and more integrated experience. Key features of Cypress: Built for JavaScript (Node.js environment). Fast execution and real-time reloading. Tight integration with modern web applications. Key Differences Between Cypress and Selenium 1. Architecture Selenium operates externally, using WebDriver to send commands to the browser. This can result in slower execution and less reliability in handling complex interactions. Cypress, on the other hand, runs directly inside the browser, interacting with the DOM in real-time. This tight integration makes Cypress faster and more reliable for testing modern web apps. 2. Language Support Selenium supports multiple languages, including Java, Python, C#, Ruby, and JavaScript. This flexibility allows teams to work with various programming languages. Cypress is built exclusively for JavaScript, meaning it's ideal for teams using JavaScript-based technologies like Node.js and modern frameworks. 3. Cross-Browser Compatibility Selenium supports a wide range of browsers and operating systems, making it a go-to tool for cross-browser testing. Cypress currently supports Chrome, Chromium-based browsers, and Edge, with limited support for Firefox. It doesn’t offer full cross-browser compatibility like Selenium. 4. Speed and Performance Selenium communicates with the browser externally, which can lead to slower test execution, especially for larger test suites. Cypress operates within the browser, leading to faster execution and immediate feedback. It’s particularly beneficial for developers who need to run tests frequently. #Cypress #Selenium

16

1 Comment

#selenium #seleniumwebdriver You must have used below statements in Selenium WebDriver - Java WebDriver driver = new ChromeDriver(); JavascriptExecutor jsExecutor = (JavascriptExecutor) driver; TakesScreenshot screenshot = (TakesScreenshot) driver; We always do not need to use these. Let's understand upcasting, down casting in Java and when to use them with Selenium WebDriver in this video - #39. Upcasting & Down casting in Selenium WebDriver | WebDriver driver = new ChromeDriver() | https://lnkd.in/ehdfAhfV

29

Just submitted a proposal for the Selenium Conference 2024,please upvote if you like to know more about it . How to Build Intelligence in Test Automation to maximise on ROI https://lnkd.in/gmmHr-M3 Vineet Kansal Narinder Kumar #TestAutomation #Intelleigence #AI/ML

11

🎯🔍𝐌𝐚𝐬𝐭𝐞𝐫𝐢𝐧𝐠 𝐍𝐞𝐬𝐭𝐞𝐝 𝐅𝐫𝐚𝐦𝐞𝐬 𝐢𝐧 𝐒𝐞𝐥𝐞𝐧𝐢𝐮𝐦:𝐂𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐞𝐬 & 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬🚀 Welcome back to my "Frames in Selenium" series! In this post, I'll tackle one of the more intricate aspects of frame automation: 𝐝𝐞𝐚𝐥𝐢𝐧𝐠 𝐰𝐢𝐭𝐡 𝐧𝐞𝐬𝐭𝐞𝐝 𝐟𝐫𝐚𝐦𝐞𝐬. Nested frames occur when frames are embedded within other frames, creating a hierarchy of frames that can be challenging to navigate. But fear not! I'll provide you with the knowledge and examples you need to conquer this hurdle with confidence! 🎡🚀 𝑷𝒍𝒆𝒂𝒔𝒆 𝒈𝒐𝒕 𝒕𝒉𝒆 𝑪𝒂𝒓𝒐𝒖𝒔𝒆𝒍 𝒕𝒐 𝒌𝒏𝒐𝒘 𝒂𝒃𝒐𝒖𝒕 𝑪𝒉𝒂𝒍𝒍𝒆𝒏𝒈𝒆𝒔 𝒇𝒂𝒄𝒆𝒅 𝒂𝒏𝒅 𝑺𝒐𝒍𝒖𝒕𝒊𝒐𝒏𝒔 𝒑𝒓𝒐𝒗𝒊𝒅𝒆𝒅 𝒘𝒉𝒆𝒏 𝒅𝒆𝒂𝒍𝒊𝒏𝒈 𝒘𝒊𝒕𝒉 𝑵𝒆𝒔𝒕𝒆𝒅 𝑭𝒓𝒂𝒎𝒆𝒔. You can just hit the🔔 icon and follow ➡ 𝐍𝐚𝐠𝐚 𝐕𝐞𝐧𝐤𝐚𝐭𝐚 𝐑𝐚𝐠𝐡𝐮𝐯𝐞𝐞𝐫 𝐂𝐡𝐞𝐛𝐫𝐨𝐥𝐮 ⬅ if you want to be notified of such practical & use full content. Have any questions or insights to share? Drop them in the comments below, and let's dive into the fantastic world of frames together! 🗣️🤝 🔹 Final Words 🗣️🤝 Handling nested frames in Selenium requires a clear understanding of the frame hierarchy and the correct sequence of switching operations. Armed with these solutions and examples, you're now well-prepared to tackle even the most complex frame setups in your automation projects! 💪👩‍💻👨‍💻 If you have any questions or need further assistance, please ask in the comments below. Stay tuned for my next post.💡 #seleniumautomation #testautomation #automationjourney #webautomation #qualityassurance #softwaretesting #learningopportunity #selenium #qualityassurance #testing #qamanual #qatraining #seleniumwebdriver #testingtools #seleniumtraining #testingcommunity #helpinghands #automationtesting #seleniumwebdriver #sdet

32

Could you clarify which specific Selenium commands or functionality you're referring to? This will help me delve deeper into the topic and provide the ultimate guidance.

1

For me, Software Testing is an Investment not towards of error free software, it is an Investment on Risk Assessment and informed decision making.

4

I've recently gone through a series of interviews and realized that I sometimes struggle with real-time QA scenario-based questions. One challenging scenario I encountered was as follows: asked in Round 4 for SDET profile result [rejected] Scenario: you discover a bug that could potentially impact the functional operation in production. However, the development team does not consider it a bug in production. How would you handle this situation and ensure the issue is prevented in production? ___________________________ I know there are various approaches to handling such scenarios. I would appreciate your suggestions on how a tester should approach this process. Please share your thoughts in the comments below. ** If you have any documents or materials on similar scenarios, that would be incredibly helpful. Thank you in advance for your insights. Jatin Shharma Japneet Sachdeva Akhil Jain Mukesh Otwani Pramod Dutta #SoftwareTesting #InterviewPreparation #LearningAndDevelopment

36

18 Comments

Dear Connections Whoever interested in Selenium and Automation Interview questions or if you preparing for an interview,I am going to post 4 or 5 Important questions and Answers as a Series ,Pls learn it whenever you see it -- Starts Episode 1 What is Stale element exception? StaleElementReferenceException is one of the most common Selenium exceptions when the web element you are trying to interact with is no longer associated in the DOM Reason 1: When element you are finding is moved Reason 2 :When element your are finding is deleted Solution1 : Use Explicit WebDriverwait Method 1: Wait until the element is present wait.until(ExpectedConditions.presenceOfElementLocated(Web element locator"))) Solution2. Use the try-catch block WebElement element = driver.findElement(By.id("web element locator")); try {     element.click(); } catch (StaleElementReferenceException e) {   // Refresh the page   driver.navigate().refresh();    // Try to locate the element again   element = driver.findElement(By.id("web element locator "));   element.click(); } Solution 3. Use Page Object Model Solution 4: Refresh the web page How do you optimize the code for selenium? ·      Use concise code ·      Give proper Naming conversion, ·      No hard coded values ·      //Commenting code with details ·      Avoid code duplicates ·      Use fast locators - wherever applicable use css ·      Use parallel testing ·      Use headless browser testing - improves performance ·      Prioritize test cases: Focus on critical functionality first, and split large test suites into smaller chunks. ·      Remove redundant tests: Remove redundant and outdated tests. ·      Write shorter tests: Keep the number of steps in each test under 20. How to run parallel tests in TestNG? Pre--requisite:  Step 1 To create a testing.xml file, right click on the ParallelTest class and select TestNG >> Convert To TestNG. Executing Test Classes in Parallel using TestNG Step 1 To run classes in parallel mode, create two class files as ChromeTest and FirefoxTest with three test methods. Step 2 In the testing.xml file, add class names and update parallel value as classes and run it. Example -<suite name="Suite" parallel="classes"> How to do datadriven testing in testing? ·      Using dataprovider annotations ,we can achieve data driven testing by the parameterizing the tests ·      We allowing the same test method to be executed multiple times with different sets of input data. Different types of framework? Linear Scripting Framework is a basic level test automation framework that is in the form of ‘Record and Playback’ in a linear fashion. Modular Testing Framework: In the modular testing framework, testers create test scripts module wise by breaking down the complete application under test into smaller, independent tests. Data-driven Framework: It allows us to create test automation scripts by passing different sets of test data.

5

How we can back promote changes in Jenkins CICD from one dev sandbox to another dev sandbox once changes deployed to QA sandbox. e.g. if Dev1 team made changes and deployed to QA then same changes I have to deploy from QA to Dev2 sandbox. Any thought? what is best approach as I have 5 dev teams, also we need to add separate sandbox for Hotfix and BAU dev as well. #Salesforce #SalesforceDevOps #SalesforceRelease #Jenkins #DevOps

1

3 Comments

My take on why test Automation with BDD Cucumber does not work at all(in complex and semi complex projects) : 1) Cucumber’s Gherkin syntax aims to make tests readable for non-technical stakeholders, but they rarely engage with them, making the added readability redundant. 2) It introduces high maintenance costs since feature files and step definitions must stay in sync, adding unnecessary technical debt. 3) Its separation of intent and implementation limits flexibility, complicating the addition of complex logic. 4) The heavy reliance on step definitions makes test creation slower and more cumbersome than direct scripting.

4

2 Comments

✍ Practical Guide on Continuous Integration for automation tests This blog describes the best practices and serve as a practical guide to implement test pyramid and integrate CI/CD process in the automation pipeline. It covers the following points 1. What is Continuous Integration? 2. What is an automated test? 3. Why write automated tests? 4. What is an Automated Pipeline? 5. How to integrate automated tests with Continuous Integration workflow? Link to the blog 👇 https://lnkd.in/ggPCKYBY #cicd #automationtesting #testautomation #qa #sdet #learning #knowledgesharing #pipeline #softwaretesting

5

𝗥𝗲𝗿𝘂𝗻𝗻𝗶𝗻𝗴 𝘁𝗵𝗲 𝗳𝗮𝗶𝗹𝗲𝗱 𝘁𝗲𝘀𝘁 𝗰𝗮𝘀𝗲𝘀: Hello Family, When we 𝘄𝗼𝗿𝗸 𝗶𝗻 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻, we come across a scenario for 𝗿𝗲-𝗲𝘅𝗲𝗰𝘂𝘁𝗶𝗻𝗴 only 𝗳𝗮𝗶𝗹𝗲𝗱 𝘁𝗲𝘀𝘁 cases in BDD cucumber? ☑ 𝗙𝗶𝗿𝘀𝘁 𝗨𝘀𝗲 𝗖𝗮𝘀𝗲: Rerun 𝗙𝗮𝗶𝗹𝗲𝗱 Test Cases, 𝗣𝗼𝘀𝘁 Execution is completed 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻𝘀: 📌 𝗖𝘂𝗰𝘂𝗺𝗯𝗲𝗿 𝗗𝗲𝗳𝗮𝘂𝗹𝘁 𝗙𝗲𝗮𝘁𝘂𝗿𝗲 : Rerun Plugin to generate rerun.txt 📌 𝗧𝗲𝘀𝘁𝗡𝗚 Feature to generate 𝗙𝗮𝗶𝗹𝗲𝗱𝗧𝗲𝘀𝘁𝗡𝗚.𝘅𝗺𝗹 👉 Link to Video: https://lnkd.in/dRvrzYvS ☑ 𝗦𝗲𝗰𝗼𝗻𝗱 𝗨𝘀𝗲 𝗖𝗮𝘀𝗲: 𝗥𝗲𝗿𝘂𝗻 𝗙𝗮𝗶𝗹𝗲𝗱 Test Cases 𝗗𝘂𝗿𝗶𝗻𝗴 𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻 𝘁o avoid 𝗙𝗹𝗮𝗸𝗶𝗻𝗲𝘀𝘀 due to some ongoing performance issues at application side. 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Use 𝗜𝗥𝗲𝘁𝗿𝘆𝗔𝗻𝗮𝗹𝘆𝘇𝗲𝗿 Feature of 𝗧𝗲𝘀𝘁𝗡𝗚 𝗦𝘁𝗲𝗽𝟭: Integrate cucumber with TestNG 𝗦𝘁𝗲𝗽𝟮: Implement IRetryAnalyzer interface of TestNG 👉 Link to Video: https://lnkd.in/ghUUq35c Note: We should not use this second use case to achieve positive results only. it should be used in above mentioned condition only. Link to Repo: 👉 https://lnkd.in/e-ESS2Ky Regards, PrinceAutomationDestination

1