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 - 


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 -


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 -


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


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.


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

  2. Not quite sure of Selenium support for HTML 5. Yet I suggest you to post your question here -


Post a Comment

No spam only genuine comments :)

Popular posts from this blog

How to write bad UI automation code (a formal guide)

You might find umpteen resources on learning to write UI automation. But rarely you find any guide on writing bad automation code. Bad automation code is not actually "bad" especially when you consider following - Bad automation code keeps you job safe. Well who can understand the code other than you. Gives you an opportunity to ask for more raise as you are the only one who can maintain the code you write Lets you keep your head up as you the geek of your company who knows that abstruse code  Now coming to writing bad automation code, here are some silver bullets - Record and Replay is the core or writing good (read bad) automation code. It has so many advantages which just out do many others. Biggest being you don't have to write any good code (read bad), tool does it for you. The way to convince decision owners in to enlightening is to let them know that record and replay does not require any special skills. Even your HR can do this.

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

Verify email confirmation using Selenium

Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can