Pavani Jandhyala

You don’t trust your QA or SDET if… 1. You skip their feedback in sprint reviews 🗣️ If QA raises concerns during sprint reviews or retrospectives and they’re brushed aside, it might indicate a lack of trust in their perspective. Their job is to identify risks before they become costly problems. 2. You don’t involve them early in the development cycle 🛠️ Leaving QA out of requirements gathering or design discussions signals you don’t see them as key stakeholders. Involving them early ensures they understand the context and can prepare better test strategies. 3. You question every bug they find 🐞 If you spend more time debating the validity of a reported issue than addressing it, it can create friction and discourage thorough testing. Trust their expertise—they're advocating for your product’s success. 4. You don’t empower them with the right tools 🛠️ Automation requires resources. If your SDET is asking for tools or infrastructure upgrades and you're hesitating, it could indicate a lack of trust in their ability to deliver results. 5. You view testing as a bottleneck ⏳ The mindset that QA is “slowing things down” often stems from undervaluing the critical role they play. Testing isn’t a delay—it’s an investment in your product’s quality and user satisfaction. 6. You assume developers should handle everything 👩‍💻👨‍💻 Developers and testers have distinct roles. Assuming developers can “test their own code” is not only unrealistic but also undermines the value of having a dedicated QA team. 7. You skip retrospectives on escaped bugs 🔄 When bugs reach production, it’s not just QA’s responsibility—it’s the entire team’s. Skipping a retrospective or blaming QA shows a lack of trust in their problem-solving ability. Why trust matters 🔑 Trust between developers, testers, and product teams fosters collaboration and innovation. A trusted QA team doesn’t just find bugs—they enhance quality, protect your reputation, and ensure smooth user experiences. Trust is built through inclusion, communication, and acknowledgment of their expertise. What’s your experience? Have you seen these trust issues in action—or overcome them? Let’s discuss in the comments!

Complex QA Interview Questions for Experience Range: 3 to 8 yrs Q 1 - What are un-reproducible bugs? Ans: The following kind of bugs can be categorised as un-reproducible bugs: Defects that surface due to issues of low memory. Errors or bugs that arise due to addresses pointing to memory locations that do not exist. Race conditions are error scenarios that occur when the time of execution of one event impacts another event executing in a sequence. Q 2 - What is a critical bug? Ans: A critical bug is a bug that impacts a major functionality of the given application. This means affecting a large area of the functionality or breaking any functionality and there is no other method to overcome this problem. The application cannot be delivered to the end user unless the critical bug is fixed. Q 3 - How will you determine when to stop testing? Ans: It can be hard to know when to stop testing. Many modern software applications are so complicated and run in such a relaxed environment that thorough testing is impossible. The following are some regular criteria to consider when considering when to end testing: Deadlines are very important (release deadlines, testing deadlines, etc.) Completed test cases with a certain percentage of passing When the test budget runs out When the coverage of code, functionality, or requirements arrives at a certain point, it is said to be complete When the bug rate drops below a specific threshold When the beta or alpha testing stage is over Q 4 - What are the best software quality practices as per your work experience? Ans: These are some best practices I usually follow to deliver a high-quality product and effectively perform my QA roles and responsibilities in software testing Review the requirements in depth before you start with the development This is the time to review the code Write comprehensive test cases as required Perform session-based testing, then risk-based testing Set the priority for bugs based on usage Run a regression cycle Perform sanity tests on pre-prod Focus on QA test reports Q 5 - Describe the defect cycle steps Ans: As a candidate, you should have knowledge of the bug cycle, which typically follows these steps: Defect discovery: A defect is discovered during testing or by a customer. Defect reporting: The tester reports the defect along with a detailed description and steps to reproduce it. Defect prioritisation: The defect is prioritised based on its severity and impact on the product. Defect assignment: The defect is assigned to a developer to investigate and fix. Defect fixing: The developer fixes the defect and verifies the fix. Defect Validation: The tester validates that the defect has been fixed and closes. Defect closure: The defect is closed after being fixed and validated. Note - This is not a defect life cycle #QAInterview #QualityAssurance #TechInterview #InterviewQuestions #SoftwareQuality #BugFixing #SoftwareDevelopment #CriticalBugs

2

Top 15 API Terms every SDET should know! 1) API: Clients request resources or services that the server performs. The way in which these two parts usually communicate is through an API. 2) API Orchestration: Combining data from multiple services and presenting it to client or application for further interactions. 3) API Gateway: A single entry point for all clients. It helps balance the load to the endpoints received from different clients and manages traffic. 4) API Key: One of the authentication mechanism, where unique keys are used by each client for further usage. 5) API Request: API request is the set of details needed to submit to the server to understand and respond properly. 6) API Response: After sending the details as a request, the server interprets and sends the response back to the client. 7) BaseURI: Base Uniform Resource Identifier is the complete path used to locate a specific resource (Base URL, which is the application URL + path) 8) API Contract: Contract: An agreement details what the consumer can expect from the API. Take a look at google outh 2.0 contract: https://lnkd.in/gpZ2ZGZw 9) CORS:  Cross-Origin Resource Sharing (CORS) is an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Note: CORS errors are one of the most common issues in API Testing. 10) HTTP methods: An HTTP request is an action to be performed on a resource identified by a given Request-URL. Request methods are case-sensitive. The most common ones are: GET, POST, PUT, and DELETE. 11) HTTP Headers: Headers are the additional but essential information sent as part of the request details from the client for the server to understand the client. Such as Content-Type, Tokens etc. 12) Pagination of APIs: Offset Pagination: is the simplest method; “limit” and “offset” values are used here. Keyset Pagination: uses the filter values of the previous page to determine the next set of items. 13) Parameters: API Parameters are passed along with the endpoint URL, which helps filter resources. Path/Query params are the most frequently used ones. 14) Status Codes: The list of numeric codes followed by a message returned from the server to the client. Client error codes: starts from 4xx, Server error codes: starts from 5xx. 15) SSL Certificates: SSL certificates create a foundation of trust by establishing a secure connection. It is a small data file that cryptographically establishes an encrypted link between a web server and a browser. -x-x- Get SDET Interview ready with my latest updated package (paid): https://lnkd.in/gusymgFi Read & Follow me on Medium for tech related blogs: https://lnkd.in/dCDi84Q9 #japneetsachdeva

257

8 Comments

Top 15 API Terms every SDET should know! 1) API: Clients request resources or services that the server performs. The way in which these two parts usually communicate is through an API. 2) API Orchestration: Combining data from multiple services and presenting it to client or application for further interactions. 3) API Gateway: A single entry point for all clients. It helps balance the load to the endpoints received from different clients and manages traffic. 4) API Key: One of the authentication mechanism, where unique keys are used by each client for further usage. 5) API Request: API request is the set of details needed to submit to the server to understand and respond properly. 6) API Response: After sending the details as a request, the server interprets and sends the response back to the client. 7) BaseURI: Base Uniform Resource Identifier is the complete path used to locate a specific resource (Base URL, which is the application URL + path) 8) API Contract: Contract: An agreement details what the consumer can expect from the API. Take a look at google outh 2.0 contract: https://lnkd.in/gpZ2ZGZw 9) CORS:  Cross-Origin Resource Sharing (CORS) is an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Note: CORS errors are one of the most common issues in API Testing. 10) HTTP methods: An HTTP request is an action to be performed on a resource identified by a given Request-URL. Request methods are case-sensitive. The most common ones are: GET, POST, PUT, and DELETE. 11) HTTP Headers: Headers are the additional but essential information sent as part of the request details from the client for the server to understand the client. Such as Content-Type, Tokens etc. 12) Pagination of APIs: Offset Pagination: is the simplest method; “limit” and “offset” values are used here. Keyset Pagination: uses the filter values of the previous page to determine the next set of items. 13) Parameters: API Parameters are passed along with the endpoint URL, which helps filter resources. Path/Query params are the most frequently used ones. 14) Status Codes: The list of numeric codes followed by a message returned from the server to the client. Client error codes: starts from 4xx, Server error codes: starts from 5xx. 15) SSL Certificates: SSL certificates create a foundation of trust by establishing a secure connection. It is a small data file that cryptographically establishes an encrypted link between a web server and a browser. -x-x- Note: All services on TopMate are discounted till 31st May. Use it maximize your learning!! Get SDET Interview ready with my latest updated package (paid): https://lnkd.in/gusymgFi Full Stack QA with Test Architect preparation: https://lnkd.in/dWjpT3-3 Read & Follow me on Medium for tech related blogs: https://lnkd.in/dCDi84Q9 #japneetsachdeva

152

10 Comments

Top 15 API Terms every SDET should know! 1) API: Clients request resources or services that the server performs. The way in which these two parts usually communicate is through an API. 2) API Orchestration: Combining data from multiple services and presenting it to client or application for further interactions. 3) API Gateway: A single entry point for all clients. It helps balance the load to the endpoints received from different clients and manages traffic. 4) API Key: One of the authentication mechanism, where unique keys are used by each client for further usage. 5) API Request: API request is the set of details needed to submit to the server to understand and respond properly. 6) API Response: After sending the details as a request, the server interprets and sends the response back to the client. 7) BaseURI: Base Uniform Resource Identifier is the complete path used to locate a specific resource (Base URL, which is the application URL + path) 8) API Contract: Contract: An agreement details what the consumer can expect from the API. Take a look at google outh 2.0 contract: https://lnkd.in/gpZ2ZGZw 9) CORS:  Cross-Origin Resource Sharing (CORS) is an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Note: CORS errors are one of the most common issues in API Testing. 10) HTTP methods: An HTTP request is an action to be performed on a resource identified by a given Request-URL. Request methods are case-sensitive. The most common ones are: GET, POST, PUT, and DELETE. 11) HTTP Headers: Headers are the additional but essential information sent as part of the request details from the client for the server to understand the client. Such as Content-Type, Tokens etc. 12) Pagination of APIs: Offset Pagination: is the simplest method; “limit” and “offset” values are used here. Keyset Pagination: uses the filter values of the previous page to determine the next set of items. 13) Parameters: API Parameters are passed along with the endpoint URL, which helps filter resources. Path/Query params are the most frequently used ones. 14) Status Codes: The list of numeric codes followed by a message returned from the server to the client. Client error codes: starts from 4xx, Server error codes: starts from 5xx. 15) SSL Certificates: SSL certificates create a foundation of trust by establishing a secure connection. It is a small data file that cryptographically establishes an encrypted link between a web server and a browser. -x-x- Get SDET Interview ready with my latest updated package: https://lnkd.in/gusymgFi Become Master in Test Automation Frameworks & Designs: https://lnkd.in/gyFKz5yF My latest course on Udemy, for sale at Rs 399 only, Take a look here: https://lnkd.in/grvCi-ri #japneetsachdeva

144

2 Comments

QA report. For H1 of 2024. Top 3 automation QA tooling: 🔺 Selenium 🔺 Cypress 🔺 Playwright Top 3 QA methodologies: 🔺 Regression testing 🔺 E2E testing 🔺 Unit testing Top 3 QA hacks: 🔺 Host testing parties before major releases 🔺 Integrate QA into CI/CD 🔺 Aim for 80% automation test coverage Insights from managing QA for dev teams of 5-50.

53

9 Comments

Have you worked on Selenium & PlayWright? One of the crucial interview questions to showcase practical experience Selenium Exceptions vs Playwright Exceptions 🔥 ➡ Selenium Exceptions <> NoSuchElementException: Occurs when an element is not found using a locator strategy <> TimeoutException: Arises when a command does not complete its execution within the defined time <> StaleElementReferenceException: Happens when an element is no longer present in the DOM <> ElementNotInteractableException: Occurs when an element is present but not in a state that can receive input <> ElementNotVisibleException: Happens when an element is not visible on the screen but expected to be interacted with <> ElementClickInterceptedException: Occurs when an element is found but cannot be clicked due to another element obscuring it <> UnexpectedAlertPresentException: Arises when an unexpected alert pops up while executing a command <> InvalidSelectorException: Happens when the provided selector is invalid or incorrect <> SessionNotFoundException: Occurs when the WebDriver session is not found or has ended prematurely <> UnhandledAlertException: Happens when an alert is present, and the command used to handle it is not supported ➡ Playwright Exceptions <> TimeoutError: This occurs when an operation does not complete within the specified timeout <> SelectorError: Arises when a provided selector does not match any elements <> PageError: Represents errors related to actions or interactions with a page <> FrameError: Occurs when dealing with frames or iframes and an operation cannot be executed <> RequestFailedError: Represents failures in network requests or response handling <> RouteHandlerError: Represents errors when handling routes or intercepting network requests <> BrowserContextError: Arises when there are issues related to browser contexts, such as creating or manipulating them <> BindingCallError: Occurs when there are issues with function calls or bindings within the Playwright API <> WorkerError: Represents errors occurring within workers or threads in Playwright's execution environment Do follow for more - Japneet Sachdeva -x-x- Become Master of Test Automation Frameworks, Interviewers expect more then Page Object Model now!!! : https://lnkd.in/gyFKz5yF Become Proficient Automation Tester with CI/CD, Learn Industry standard Docker, GitHub Actions, Jenkins: https://lnkd.in/gWmK9Jud #japneetsachdeva

104

5 Comments

Top Tools to keep in your Arsenal as a QA & SDET . 1) Clear Cache: It's a chrome browser extension - Clear your cache and browsing data with a single click of a button. Installation link: https://lnkd.in/g_wCEmNy 2) Exploratory Testing: It's a chrome browser extension - Can help you to take screenshots, report bugs, take notes etc. Installation link: https://lnkd.in/gEcjsdnF 3) Test case studio: It's a chrome browser extension - Helps to store the user actions performed in simple english. Installation link: https://lnkd.in/g3k3F8n2 4) Selectors hub: It's a chrome browser extension - Helps to create and improve your existing locators. Such as xpath, css selectors, normalized texts etc. Installation link: https://lnkd.in/gBAN7Fzf 5) Go Full Page: It's a chrome browser extension - Full page screenshot capability within your browser, then it can be downloaded as png or pdf file. Installation link: https://lnkd.in/gU5Zzqze 6) JsonView: To view and interpret the JSON easily Installation link: https://lnkd.in/gHtWQfx9 7) Session Manager: To manage and restore your sessions/tabs in browser conveniently Installation link: https://lnkd.in/gHtWQfx9 -x-x- I am not sure how many of you are using the above mentioned tools, but these can be a great addition for your existing workflow. Willing to learn more? refer my course for SDET here: https://lnkd.in/gusymgFi Direction less? need career guidance?: https://lnkd.in/gt66_zxA My Latest YouTube video: https://lnkd.in/gZv8fCMb #japneetsachdeva

117

8 Comments

Interview questions series for QA Automation Role Experience level -> 3 to 8 years Duration -> 1.5 hrs. Quick tips - good understanding of programming, QA and Selenium Questions: 1) Brief me about your experience 2) What tools and technologies have you worked on? 3) What’s your favorite programming language? And rate yourself Note - If you rate yourself 6 or above then get ready to face challenging coding questions. 4) Find the longest substrings of these three strings: Example 1 - aab Example 2 - pwwkew Example 3 - abcbcabcda 5) Have you created a dynamic Xpath? If yes then give examples. How to automate the elements which sometimes pass or fail? 6) How to send only lowercase text where data is derived from external source, without using any java functions or libraries. 7) What is the difference in keyword driven vs data driven vs behavior driven frameworks? 8) What is Hashmap? 9) If hashmap is available then why do you need HashSet? 10) How to handle exceptions? 11) Why do you need finally block? 12) Why do you use Array when ArrayList is available? 13) What are different ways to execute parallel tests in selenium? 14) How to execute different suites using Maven and TestNG? 15) Create a dynamic XPath which can find all headlines on Amazon.com Steps - Go to Amazon.com Search for Smart TV Create Xpath to retrieve the name of all products and store in List 16) Why strings are immutable? 17) What is string constant pool? 18) When int a = 20; int b = a ; System.out.println(a); -> o/p - 20 System.out.println(b); -> o/p - 20 a=30; System.out.println(a); -> o/p - 30 System.out.println(b); -> o/p - 20 But when we do same operation in HashMaps Map<String, Integer> map1 = new HashMap<>(); map1.put(“value”, 25); Map<String, Integer> map2 = new HashMap<>(); map1=map2; System.out.println(map1); -> o/p - value,25 System.out.println(map2); -> o/p - 20 - value,25 Now if we update this to - map1.put(“value”, 42) System.out.println(map1); -> o/p - value,42 System.out.println(map2); -> o/p - 20 - value,42 Why does this happen?? 19) Why do you need Throw and Throws keyword when we have Try,catch and finally? 20) Explain Smoke vs Sanity vs Regression differences? 21) What do you understand by git rebase? -x-x- Do follow for more: Japneet Sachdeva Find all the answers for above questions here (paid): https://lnkd.in/gSU-m2F7 Crack Test Automation Interviews using JAVA, Master Package for Clearing QA Automation Interviews: https://lnkd.in/g5hr9bea #japneetsachdeva

313

10 Comments

Interview questions series for QA Automation Role Experience level -> 3 to 8 years Duration -> 1.5 hrs. Quick tips - good understanding of programming, QA and Selenium Questions: 1) Brief me about your experience 2) What tools and technologies have you worked on? 3) What’s your favorite programming language? And rate yourself Note - If you rate yourself 6 or above then get ready to face challenging coding questions. 4) Find the longest substrings of these three strings: Example 1 - aab Example 2 - pwwkew Example 3 - abcbcabcda 5) Have you created a dynamic Xpath? If yes then give examples. How to automate the elements which sometimes pass or fail? 6) How to send only lowercase text where data is derived from external source, without using any java functions or libraries. 7) What is the difference in keyword driven vs data driven vs behavior driven frameworks? 8) What is Hashmap? 9) If hashmap is available then why do you need HashSet? 10) How to handle exceptions? 11) Why do you need finally block? 12) Why do you use Array when ArrayList is available? 13) What are different ways to execute parallel tests in selenium? 14) How to execute different suites using Maven and TestNG? 15) Create a dynamic XPath which can find all headlines on Amazon.com Steps - Go to Amazon.com Search for Smart TV Create Xpath to retrieve the name of all products and store in List 16) Why strings are immutable? 17) What is string constant pool? 18) When int a = 20; int b = a ; System.out.println(a); -> o/p - 20 System.out.println(b); -> o/p - 20 a=30; System.out.println(a); -> o/p - 30 System.out.println(b); -> o/p - 20 But when we do same operation in HashMaps Map<String, Integer> map1 = new HashMap<>(); map1.put(“value”, 25); Map<String, Integer> map2 = new HashMap<>(); map1=map2; System.out.println(map1); -> o/p - value,25 System.out.println(map2); -> o/p - 20 - value,25 Now if we update this to - map1.put(“value”, 42) System.out.println(map1); -> o/p - value,42 System.out.println(map2); -> o/p - 20 - value,42 Why does this happen?? 19) Why do you need Throw and Throws keyword when we have Try,catch and finally? 20) Explain Smoke vs Sanity vs Regression differences? 21) What do you understand by git rebase? -x-x- Do follow for more: Japneet Sachdeva Get answers for all the above questions and more (paid): https://lnkd.in/gSU-m2F7 Become a successful Test Automation Architect with Full Stack QA skills (paid): https://lnkd.in/dWjpT3-3 E2E Test Automation Framework Creation with parallel execution and Cloud Setup: https://lnkd.in/gprAykg4 #japneetsachdeva

197

4 Comments

✨Common Selenium Exceptions ✨ When working with Selenium, facing exceptions is part of the process. Here’s a quick guide to handle them effectively:⬇️ #NoSuchElementException: 🔹Occurs When: The element you are trying to locate does not exist in the DOM. 🔸Handling: - Use explicit waits to ensure the element is present. - Verify that the locator (ID, class, XPath) is correct. #TimeoutException: 🔹Occurs When: An operation exceeds the specified wait time. 🔸Handling: - Increase the wait time or use explict wait with specific condition #ElementNotVisibleException: 🔹Occurs When: The element is in the DOM but not visible. 🔸Handling : - Scroll to the element to bring it into view. - Ensure the element is not hidden via CSS or use JavaScript to make it visible. #StaleElementReferenceException: 🔹Occurs When: The element is no longer attached to the DOM. 🔸Handling: - Relocate the element just before interacting with it. - Ensure the DOM is stable and not frequently changing -Increase the wait time or use explict wait with specific condition #NoSuchFrameException: 🔹Occurs When: Attempting to switch to a non-existent frame. 🔸Handling: - Verify the frame locator is correct. - Ensure the frame exists in the DOM before #Selenium #AutomationTesting #WebDriver

3

#seleniumwebdriver Explicit wait in Selenium WebDriver is not about only using existing methods from ExpectedConditions class. It is to wait for any conditions to be satisfied before your script move to next line. 1. Learn about WebadriverWait class hierarchy. 2. Know about Function interface which is a functional interface 3. How to create own waiting conditions with anonymous class with lambda expression. 4. Any many more… #42. Explicit Wait in Selenium WebDriver With Custom Expected Conditions | WebDriverWait Class | https://lnkd.in/egnVhVCy

19

QA & QA Automation interview questions with answers Experience level - 4 years or more Q1) Describe a time when you missed a bug? Ans: No one can say they never make mistakes. So it’s a red flag if a candidate tries to insinuate their work is 100% error-free. So obviously providing an example in this situation is really useful. Now for me its related to a web application testing. Scenario - I was working in insurance domain and there are different tiles which appear with respect to a user account. So I missed to test a FSA tile. FSA is Flexible Spending Account which a user can use upto a limit granted by its insurance provider. Although there are different ways in the application to get know the remaining amount, but still missing this to test was an issue. But it didn't cause a major issue because it was medium priority Test Scenario. Q2) Do you think manual testing has any advantages? If so, what are they? Ans: Manual testing can be a better choice in some cases because :- <> The cost of manual testing can be lower than that of automated testing <> Manual testing allows you to see the product from the end user’s perspective <> Performing a manual GUI test is more intuitive, and results are more accurate automated GUI testing is tricky because of the accessibility of visuals and preferences <> A manual test can be easier to run for new teams or people new to quality assurance, meaning that it can be rolled out more quickly A lot more points can be added so as per your experience keep on adding. Q3) How do you ensure a bug in production is fixed? Ans: Validating the bug fix in dev or QA or Staging env, Once validated writing a test case and running a regression test immediately is the best course of action. This way, future software tests will be able to detect this specific bug. These can be done with the help of patch updates or hotfix or as a new release. Q4) How are a build and a release number different? Ans: A build number is assigned by the development team to a piece of installed software that goes to the testing team. The release number is assigned by the developer or tester to a piece of installed software before releasing it to the customer. Q5) What is defect triage? Ans: Bug triage is a process in which QA engineers: <> Make sure bug reports are complete <> Assign and analyze bugs <> Identify the proper bug owner and assign the bug to them <> Make necessary adjustments to bug severity <> Determine bug priority Do follow for more - Japneet Sachdeva Get more such scenario based and advance SDET interview questions with answers: https://lnkd.in/gSU-m2F7 #japneetsachdeva

232

12 Comments

#Selenium Online Training #New #Batch Register : https://t.ly/kRNPk ☸ Course Contents :- Java, Selenium, TestNG, Maven, Git, Jenkins, BDD Cucumber, Selenium Grid, Page Object Model, HTML, JavaScript, AutoIT, Log4j, Assertion, Project Explanation, Manual Testing, Agile, JIRA, API Testing, etc. 🚩 Dedicated Framework Design Session from Scratch to Advance Level. ✳ Transposed 10000+ People into Automation across the World. ✳ Customized Notes on All Topics. ✳ Concept Retention With Funny Example. ✳ In Depth Interview Preparation, Resume Writing Assistance and Much More. ☑ First 4 sessions are free

95

13 Comments

#InterviewQuestions02 ⚠️Some basic stuff/interview questions of testing which you should know!‼️These two questions must be in knowledge of every QA. ❓What is data driven testing? Data driven testing is an automation testing framework, which tests the different input values on the AUT. These values are read directly from the data files. The data files may include csv files, excel files, data pools and many more ❓What is a Test Case in Software Testing? A test case refers to the actions required to verify a specific feature or functionality in software testing. The test case details the steps, data, prerequisites, and postconditions necessary to verify a feature #softwaretesting #qa #qualityassurance #testing #testautomation #softskills #productknowledge #collaboration #businessimpact #softwaretester #leadershipinqa #careergrowth #testingskills

23

2 Comments

What is Desired Capabilities? In Selenium, a "Desired Capability" is a set of key-value pairs used to configure the WebDriver instance. These capabilities allow you to specify various browser settings and behaviors before starting a new browser session. Here are some common uses for Desired Capabilities: 1. Browser Name and Version: Specify the browser type (e.g., Chrome, Firefox) and version. 2. Platform: Define the operating system (e.g., Windows, Linux, macOS) where the tests will run. 3. Browser Options: Set specific browser options or preferences, like starting the browser in incognito mode or disabling certain features. 4. Timeouts: Configure timeouts for page loads, script execution, etc. 5. Proxy Settings: Set up proxy settings for the browser. 6. Logging Preferences:Define logging preferences, such as the log level for the browser. 7. Custom Capabilities: Add any custom capabilities required by specific WebDriver implementations or third-party tools.

24

4 Comments

 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 #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

𝗪𝗵𝘆 𝗶𝘀 𝗝𝗮𝘃𝗮 𝗘𝘀𝘀𝗲𝗻𝘁𝗶𝗮𝗹 𝗳𝗼𝗿 𝗮𝗻 𝗦𝗗𝗘𝗧? An aspiring SDET once asked me, "𝗪𝗵𝘆 𝘀𝗵𝗼𝘂𝗹𝗱 𝗜 𝗳𝗼𝗰𝘂𝘀 𝗼𝗻 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗝𝗮𝘃𝗮?" Here’s the list I shared with them to highlight Java’s importance in test automation: - Java + Selenium = Web Automation - Java + Collections Framework = Data Handling - Java + TestNG/JUnit = Test Execution - Java + Streams API = Data Processing - Java + Lambda Expressions = Functional Programming - Java + File I/O = Test Data Management - Java + Multithreading = Parallel Test Execution - Java + Maven/Gradle = Dependency Management - Java + JDBC = Database Testing - Java + RestAssured = API Automation - Java + Reflection API = Dynamic Frameworks - Java + OOP Concepts = Framework Design - Java + Regex = Advanced Validations - Java + Logging Frameworks (e.g., Log4j) = Test Reporting - Java + Design Patterns = Scalable Frameworks (e.g., Page Object Model) - Java + Assertions = Validation Checks - Java + Jenkins Integration = Continuous Integration - Java + Debugging Tools = Efficient Issue Resolution - Java + IDEs (e.g., IntelliJ/Eclipse) = Productivity Java’s versatility makes it a cornerstone for building robust automation frameworks, integrating tools, and ensuring scalability in test engineering. 🧞‍♂️ 𝗟𝗲𝘃𝗲𝗹 𝘂𝗽 𝘆𝗼𝘂𝗿 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝘀𝗸𝗶𝗹𝗹𝘀 𝗵𝗲𝗿𝗲 - https://lnkd.in/giCxnJJ7 If this resonates with you, don’t forget to LIKE and SHARE! 👍 #sidpost #sidpostjava #java #automation #career #sdet #softwaretesting #testautomation #qualityassurance #testing #qa

199

11 Comments