We should avoid hard coding of paths in tests as this adds to portability of test from one machine other.
I generally prefer CSS selectors over XPath when writing Selenium locators. CSS selectors are concise, readable, and usually provide everything I need. However, there are situations where XPath is a better fit—particularly when I need to navigate through an element's hierarchy, such as moving from an element to its parent, grandparent, or sibling. This post shows one such real-world example. The Problem I came across a situation where I needed to click a link based on the value of an input field. The HTML structure contained multiple similar groups of elements. The input field and the link I wanted to click were not directly related, but they shared a common parent structure. In the following example above, the input element is highlighted, and I need to click the corresponding anchor ( <a> ) element . The challenge is that there may be multiple similar structures on the page. I therefore need to locate the link relative to the particular input element rather than using a f...
FYI: You can use Environment("varname"), you don't need the ".Value".
ReplyDeleteGood work otherwise!
How can we follow same practice in Selenium Automation Project?
ReplyDeleteExample: System.setProperty("webdriver.chrome.driver",
"D:/automation/myproject/src/chromedrivers/win7/chromedriver_2.exe"); or in pom.xml
C:/Users/OfficePC21/workspace/deletexslt/testxslt/testng.xml