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

Verify email confirmation using Selenium WebDriver

Note: If you are new to java and selenium then start with selenium java training videos .   How to Verify Email Confirmation Using Selenium 4 and JavaMail (2026 Guide) Email confirmation is a critical part of most registration flows — account activation, password reset, multi-factor authentication, and onboarding. Every automation engineer eventually faces the same challenge: How do you verify an email confirmation link inside a Selenium test without making it slow and flaky? The wrong instinct is to automate Gmail's UI with Selenium. It's fragile, slow, and breaks constantly. The right approach: Use Selenium for browser automation Use JavaMail (IMAP) to read the email directly Extract the confirmation link Continue the test in Selenium Why Not Automate Gmail UI With Selenium? Automating the Gmail UI means logging in, searching, clicking a message, and parsing content from a third-party interface that changes frequently. This leads to: Flaky...

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -

Recording curl request with JMeter Recorder

Just use https://jmeter.apache.org/usermanual/curl.html and no JMeter proxy etc needed : )   Though it is quite east to convert curl requests to corresponding JMeter request. At times you might be stuck with issue like I faced when uploading a file with  JMeter HTTP request In a gist I kept getting 404 error when using REStful service to upload a file. After days of investigations I found it that I should be using HTTP request implementation java and not HttpClient4. JMeter HTTPs Test Script recorder was of great help to debug this issue. This post describes the process of recording curl request through JMeter HTTPs Test Script recorder. If you have never used JMeter HTTPs Test Script recorder then create a new JMeter Plan and under WorkBench > Add > Non Test Element > HTTP(s) Test Script Recorder.  Specify Global Setting > Port as 8090 If we were using browser to record web application then we would configure its proxy to 127.0.0.1 (Since http...