We should avoid hard coding of paths in tests as this adds to portability of test from one machine other.
Note: If you are new to java and selenium then start with selenium java training videos . I prefer css locator over xPath but there are times when css locators don't fit requirement. One such requirement is when you want to navigate to parent element of an element and may be parent of parent and even more. Unfortunately css locators don't provide any mechanism to navigate to parent of an element. See this for more. Of late I came across a scenario when I wanted to click on a link depending upon the text in a text box. Herein parent of text box and parent of link were at the same location. More over there could have been many such combinations in application. Fortunately I just need to pick first such instance and Web Driver any way considers only first instance when multiple locators are found matching an element. Element in question is in following html - Here I need to click on highlighted anchor on the basis of input element (which is also hig...
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