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

Which location strategy to use with mobile apps

Locator Strategy for native mobile apps IDs and accessibility locators are still king. NSPredicate (iOS) and UIAutomator (Android) are great—mainly better than XPath —but they do not beat a good accessibility id or resource-id . And CSS selectors don’t exist for native apps (only for WebViews). Locator Strategy Ranking Rank iOS (native) Android (native) Why 1 Accessibility ID → name / label (via MobileBy.AccessibilityId or @iOSXCUITFindBy(accessibility = "Mehr anzeigen") ) Accessibility ID → content-desc (via MobileBy.AccessibilityId ) or @AndroidFindBy(accessibility = "Letzte Aktivitäten, Überschrift") ) Fast, readable, stable when set intentionally; improves a11y. 2 Stable identifiers (rare on iOS) resource-id (via new UiSelector().resourceId(...) ) or @AndroidFindBy(id = "load_more") id is just shorthand for matching the native Android resource-id attribute. Appium automatically maps id → resource-id If you pass only "load_more"...

Verify email confirmation using Selenium

Note: If you are new to java and selenium then start with selenium java training videos .     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

Selenium Tutorial: Get attribute of an element

With Selenium 1.0 Let us consider Google Search Box for example and its "max length"is to be retrieved. Using xPath -         String var = selenium.getAttribute("//input[@name='q']/@maxlength");         System.out.println(var); Using css locator -                        String var = selenium.getAttribute("css=input[name='q']@maxlength");         System.out.println(var);        With Selenium 2.0 (WebDriver)        Using xPath -         String var = webDriver.findElement(By.xpath("//input[@name='q']")).getAttribute("maxlength")         System.out.println(var); Using css locator -                     ...