My bad, I was using find_elements_by_xpath instead of find_element_by_xpath Copy paste error from using another line of code

It might be the case that the exact locator is not found. As when you mouse over > then the element appears, and it would be disappearing if you are moving out. Pausing or debugging will help to find out the locator. You can try this: Hover over the element by using Action class: Actions action = new Actions(driver); action.moveToElement(we).build().perform(); Use the Debugger in the Network of your browser(after clicking F12) Move to the element mentioned in the step one and right click on the 3 dots(see picture below) and click > break on subtree modification This will pause you execution whenever there is a change in the DOM i.e in case of Mouse over. Then you can use the arrow keys to navigate to the hidden elements of the DOM

I am thinking of grabbing account no. from the message box and storing in a variable but not able to write a x-path which uses this variable to click on newly added account only during execution. Psuedo-Code: accountPage.aCreateNew.click(); var newAccountId = messageModal.divMessage.getText(); driver.findElement(By.Xpath("//a[contains(@href, '" + newAccountId + "')).click();

You can use the String replace method. String city = prop.getProperty("data"); // New Delhi String locatorTemplate = prop.getProperty("locatorKey"); // div[contains(text(),'<state Name>')] String locator = locatorTemplate.replace(locatorPattern, city); // div[contains(text(),'New Delhi')] WebElement element = driver.findElement(locator); locatorPattern in your case would be . The method syntax is as follows: public String replace(char searchChar, char newChar)

I think you can use parent: //div[contains(text(),'(123)')]/parent::div/following-sibling::bride_with_veil: ```

<div class="input group"> <input id="end_time"></input> <span class="input-group-btn"> <button class="btn btn-default"> <i class="fa fa-clock"></i> </button> <span> </div> You would want to use the following selector for the button (not the icon in the button, because the button has the click/event handler): //input[@id='end_time']/following-sibling::span/button Which reads something like: "//" starting anywhere on the page, find an "input" whose "id" is "end_time", then get the "following-sibling" element that is a "span", and then finally the "button" under that.

You can use //mat-option/span[condition1 or condition2 or condition3] With XPath 2.0 or higher you could also use //mat-option/span[matches(., 'aaa|bbb|ccc')] But sadly the developers of Selenium are still stuck on XPath 1.0. Are you sure you want "text()" here rather than "."? With text(), the text must all be in one text node: no intervening comments or element tags allowed.

There're usually more options, e.g.: // CSS currentDriver.FindElement(By.CssSelector("td > div.linkButton")); currentDriver.FindElement(By.CssSelector("div.linkButton")); // xPath currentDriver.FindElement(By.XPath("//div[text()='Revenue Report']")); ``` Another problem might be with element visibility, you can search this site for more information on that. Selenium WebDriver with C# binding doesn't have any retry policy, so you basically need to wait for elements and their states.

What you get in the console (a.username) is the CSS selector, if you are using xpath you will need a[@class='username']. Try something like this $x("//a[@class='username']")[0].innerText The $x("//a[@class='username']") will return a list of zero-indexed elements. So [0] will select the first element of that list and so on.

As mentioned in previous answer using custom loctors or tools to find xpath is not a recommended approach. Learn the xpath functions and appraoches. You can always use parent elemeent to refer a child element uniquely or combine different attributes together. in your case you can use : //*[contains(text(),"Paper") and @class="a-size-small a-color-secondary sc-product-binding" ] here: // - means start from root tag and find element any where in the html * - means any tag contains - checks for text() node with content "Paper" and - is used to check for multiple conditions @class - checks the value for class attribute so as we are using and , only element with text containing Paper and class as specified will be returned

for(int i=1; i<sections.size()+1; i++) Why are you adding 1 to sections size, remove 1 for(int i=1; i<sections.size(); i++) and also why starting from i=1 ? index starts from 0 to size-1 , so it should be i=0 ?

You should use contains: equals validates the attribute value is exactly equal to given value. As the attribute class value is "ng-untouched ng-pristine ng-invalid igx-input-group__input" you cannot say @class="ng-invalid" You should use contains instead driver.findElement(By.xpath("//div/input[(@formcontrolname='nic_no') and contains(@class,'ng-invalid')]"); Or use CSS: In css class can be mentioned as tag.classname: driver.findElement(By.cssSelector("div>input.ng-invalid[formcontrolname='nic_no']") If you want to have exact class match : you can use [attribute='value'] syntax: driver.findElement(By.cssSelector("div>input[class='ng-untouched ng-pristine ng-invalid igx-input-group__input'][formcontrolname='nic_no']")

Xpath can find the previous sibling of any field in the DOM. Try using xpath like this: "//div[text() = '" + user_login.email + "']/preceding-sibling::div/a"

Use the below keyword and locator: Click Element //span[text()='kw']/../*[@class="Select-value-icon"] Click Link match is based on "on link text and href." as span is not a link it may not work

Try to use developer APIs to perform this kind of actions against public sites like Facebook. For multiple reasons, logging into sites like Gmail and Facebook using WebDriver is not recommended. Aside from being against the usage terms for these sites (where you risk having the account shut down), it is slow and unreliable. The ideal practice is to use the APIs that email providers offer, or in the case of Facebook the developer tools service which exposes an API for creating test accounts, friends and so forth. Although using an API might seem like a bit of extra hard work, you will be paid back in speed, reliability, and stability. The API is also unlikely to change, whereas webpages and HTML locators change often and require you to update your test framework. See Selenium Worst Practices documentation