Skip to main content

What ??? - "com.thoughtworks.selenium.SeleniumException: syntax error"

At times during development of Selenium tests you come across errors which don't give you any clue what so ever. One such error is -

com.thoughtworks.selenium.SeleniumException: syntax error
or -
missing ) after argument list

One such occurnce of this error is when you use waitForCondition method.
This is one awesome selenium method which saved you from using ugly sleep statements in your scripts. Having read it's API you might consider using it as -

waitForCondition("selenium.isElementPresent(//a[text()='Dashboard'])", "60000");

where first argument - selenium.isElementPresent(//a[text()='Dashboard']), is the condition you expect to be true. And second argument - 60000, is the max wait period till selenium would wait for condition to be true (You don't hard code time in your scripts, do you?).

Looks simple, is not it? Execute (well, after changing locator - //a[text()='Dashboard'] to match your application) it and you end up with -

com.thoughtworks.selenium.SeleniumException: syntax error

Let's try to understand it. Thing, which you should instantly doubt on is the argument - 

selenium.isElementPresent(//a[text()='Dashboard'])

Do you usually use it this way? No you do not. isElementPresent is itself a method which takes String argument. So you use it as -

selenium.isElementPresent("//a[text()='Dashboard']")

But then this entire statement is itself first argument for waitForCondition method. So if you try to write -

waitForCondition("selenium.isElementPresent("//a[text()='Dashboard']")", "60000");

in java editor (Eclipse, IntelliJ etc), you would see compilation errors, because in argument -

"selenium.isElementPresent("//a[text()='Dashboard']")"

you used quotation twice. once with "selenium.isElem.... and then with "//a[text()='Dashboar....
And now you realize that you need to escape the second instance of quotation in your argument as

"selenium.isElementPresent(\"//a[text()='Dashboard']\")"

Whole method would look as -

waitForCondition("selenium.isElementPresent(\"//a[text()='Dashboard']\")", "60000");

And you test executes with out any error.

But then you don't hard code locators in the you test, which is - //a[text()='Dashboard'] in our case.
Consider that you are storing them in a class as static methods, returning String locators. 
In the following example there is third set of quotation introduced in first argument of waitForCondition method to concatenate UserDashboard.getDashboardLocator() with rest of the string.


Comments

  1. hii.. I went though the tutorials online and i have developed a few tests. But when I use Selenium with html5 modules, it does not record every action properly.
    So could you please tell me how do i use selenium to test my html5 modules?
    and also, how do i automate my tests???

    ReplyDelete
  2. Not quite sure of Selenium support for HTML 5. Yet I suggest you to post your question here - http://www.seleniumtests.com/p/selenium-2-forum.html

    ReplyDelete

Post a Comment

No spam only genuine comments :)

Popular posts from this blog

How can you save resources when instantiaing driver?

I asked on my previous post about what was wrong in instantiating driver on set up method? And here is the solution video on my YouTube channel (After 5 years of gap I finally added new video tutorial :)) The solution described on video tutorial uses following set up - public class BaseClassOnDemandDriverSetup { private WebDriver driver ; @BeforeMethod public void setupTest () { // Any other set up goes here } @AfterMethod public void teardown () { if ( driver != null ) { driver .quit() ; } } public WebDriver getDriver () { if ( driver == null ) { WebDriverManager. chromedriver ().setup() ; driver = new ChromeDriver() ; } return driver ; } }

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro

Using xPath to reach parent of an element

Well, I am big fan of css locator my self 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 highlighted in image) Herein first I need to reach div parent (class = 'left couponmainarea