Hi Pascal,
Glad you got it working.
I can see your problem, the javascript may want to do something before the
html page got fully loaded. For jQuery, you can put the
javascript inside the following block.
$(document).ready(function() {
});
Thanks,
Jian
On Thu, Feb 4, 2010 at 12:41 PM, Pascal Gandilhon <
[email protected]> wrote:
> Hi Jian,
>
> I use now TelluriumTestNGTestCase and it's working fine, didn't have to
> change anything in my code (excepts extends and imports of course).
>
> This didn't solve the initial IE "document.body" null problem.
> Sorry I can't send to you html source because it seems to occur in a script
> (html code is around 300 lines and the alert talks about a problem around
> line 3000...). I won't send you all the scripts.... I think this problem
> maybe comes from the fact that the page loads JQuery library + dojo library
> and I don't think taht it's a very good solution.
>
> Thank you again for your fast and smart advices.
>
> Regards,
>
> Pascal
>
> 2010/2/1 Jian Fang <[email protected]>
>
>> Good question. We don't provide any test suite and you need to rely on
>> JUnit test suite instead. I can understand why
>> you need to work on the BaseTelluriumTestCase. Perhaps you want to share
>> the same browser session across all tests in
>> a test suite. Right now, TelluriumJUnitTestCase does not provide that kind
>> of browser session sharing.
>>
>> However, if you are familiar with TestNG, you can use
>> TelluriumTestNGTestCase instead. In that test case, we provide
>> a @BeforeTest method to start up the browser session so that you can share
>> the same browser session for all test cases
>> in a test suite. The bad thing is that I cannot find a similar way for
>> JUnit. Perhaps, you need to do some test suite level
>> startup and tear down, which is not so elegant compared with TestNG.
>>
>> Another big missing piece in JUnit and TestNG is to configure the testing
>> flow. For example, we can divide the testing into multiple
>> phases, such as "Get customer information", "Get Production Information",
>> "Get payment information", "place order", and "generate
>> invoice" for a typical placing order system. Then we can bind one or
>> multiple test methods into different phases by annotation
>> or configuration. In this way, we can control how the test code will
>> actual run and make the flow configurable. In future Tellurium versions,
>> perhaps 0.8.0 or 0.9.0, we will provide this type of support.
>>
>> Thanks,
>>
>> Jian
>>
>>
>>
--
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.
