Hi Jian,

Thanks for your reply.

I tried build 28 and 31, and got the exception using either build:


java.lang.NullPointerException: Cannot invoke method open() on null object
        at 
org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77)
        at 
org.codehaus.groovy.runtime.InvokerHelper.invokePogoMethod(InvokerHelper.java:750)
        at 
org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:727)
        at 
org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:17)
        at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40)
        at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117)
        at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
        at 
org.tellurium.connector.SeleniumConnector.connectUrl(SeleniumConnector.groovy:47)
        at 
org.tellurium.test.java.BaseTelluriumJavaTestCase.connectUrl(BaseTelluriumJavaTestCase.java:56)
        at 
org.mybjc.art.test.AbstractMyBJCTestCase.connectPatientLogin(AbstractMyBJCTestCase.java:98)
        at 
org.mybjc.art.test.MT96_PasswordLogin_BlankSpaces.setUpForMethod(MT96_PasswordLogin_BlankSpaces.java:57)
        at 
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62)
        at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141)
        at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
        at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
        at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
... Removed 26 stack frames

The browser can't lauched. Do you have any hint for that?

Thanks,
Liang

On Wed, Sep 30, 2009 at 10:46 PM, Jian Fang <[email protected]>wrote:

> I made the changes to TelluriumConfig.groovy and add couple more server
> options there.
> Now the embedded server options are as follows.
>
> tellurium{
>     //embedded selenium server configuration
>     embeddedserver {
>         //port number
>         port = "4444"
>         //whether to use multiple windows
>         useMultiWindows = false
>         //whether to trust all SSL certs, i.e., option
> "-trustAllSSLCertificates"
>         trustAllSSLCertificates = true
>         //whether to run the embedded selenium server. If false, you need
> to manually set up a selenium server
>         runInternally = true
>         //By default, Selenium proxies every browser request; set this flag
> to make the browser use proxy only for URLs containing '/selenium-server'
>         avoidProxy = false
>         //stops re-initialization and spawning of the browser between tests
>         browserSessionReuse = false
>         //enabling this option will cause all user cookies to be archived
> before launching IE, and restored after IE is closed.
>         ensureCleanSession = false
>         //debug mode, with more trace information and diagnostics on the
> console
>         debugMode = false
>         //interactive mode
>         interactive = false
>         //an integer number of seconds before we should give up
>         timeoutInSeconds = 30
>         //profile location
>         profile = ""
>         //user-extension.js file
>         userExtension = "target/test-classes/extension/user-extensions.js"
>     }
> ...
> }
>
> The latest TelluriumConfig.groovy sample is available here.
>
>
> http://code.google.com/p/aost/source/browse/trunk/core/TelluriumConfig.groovy
>
> Please use the core 0.7.0 snapshot from our Maven repo or download it
> directly from
> the following URL.
>
>
> http://kungfuters.org/nexus/content/repositories/snapshots/tellurium/tellurium-core/0.7.0-SNAPSHOT/tellurium-core-0.7.0-20090930.144130-28.jar
>
> Thanks,
>
> Jian
>
>
>
> On Wed, Sep 30, 2009 at 9:19 AM, Jian Fang <[email protected]>wrote:
>
>> If it is a selenium server option, we may have not included yet. We can
>> add it to TelluriumConfig.groovy very quickly. What other server options do
>> we need to add?
>>
>> Thanks,
>>
>> Jian
>>
>>
>> On Wed, Sep 30, 2009 at 4:27 AM, Liang HE <[email protected]> wrote:
>>
>>> I just saw in an old email, Jian says setTimout is included in
>>> DslContext. But I can't find this method in tellurium core 0.6.0. I am not
>>> sure if there is any updated version released. Further more, I need to use
>>> it in the testcases inherited from BaseTelluriumJavaTestCase instead of
>>> DslContext. How should I handle this problem?
>>>
>>> Thanks a lot!
>>> Liang
>>>
>>>   On Wed, Sep 30, 2009 at 4:10 PM, Liang HE <[email protected]> wrote:
>>>
>>>> Hi guys,
>>>>
>>>> I am using Tellurium to automate the testing of a slow website. The
>>>> default timeout is 30 seconds and the response time oftern exceeds it. In
>>>> traditional Selenium, I can use setTimeout to override the value, but I
>>>> don't know how to deal with this problem in Selenium. Is there any way to
>>>> set up it in TelluriumConfig.groovy? If yes, what is the context?
>>>>
>>>> I also tried started Selenium sever like:
>>>>
>>>> java -jar seleniumXXX.te.jar -timeout 60
>>>>
>>>> but it doesn't work and the test case still timeout in 30 seconds?
>>>>
>>>> Anyone can give me some hints?
>>>>
>>>> Thanks,
>>>> Liang
>>>>
>>>
>>>
>>>
>>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"tellurium-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/tellurium-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to