Seaside Testing Framework with Seaside 2.7

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Seaside Testing Framework with Seaside 2.7

Berger Stefan-2
Hi all,

I tried to test a seaside application with Seaside2.7a1-mb.115 and
SeasideTesting-R1.4-cds.1

The WACounterTest and all other applications failed, because the Session
could not get initialized.

I figured that in SCBrowserSimulator>>httpGetRequestStreamFor:url a
readStream was given. But later on in the HttpRequest>>initRemoteAddress
will try to access a socket from the stream. Unfortunately the
readStream doesn't support a socket.

Does anyone know the problem and does anyone have a conclusion to solve
it? I tried to change the readStream to a socketStream but more problems
awake after that ;)

Thanks for your help!
Stefan
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside Testing Framework with Seaside 2.7

cdavidshaffer
Berger Stefan wrote:

> Hi all,
>
> I tried to test a seaside application with Seaside2.7a1-mb.115 and
> SeasideTesting-R1.4-cds.1
>
> The WACounterTest and all other applications failed, because the Session
> could not get initialized.
>
> I figured that in SCBrowserSimulator>>httpGetRequestStreamFor:url a
> readStream was given. But later on in the HttpRequest>>initRemoteAddress
> will try to access a socket from the stream. Unfortunately the
> readStream doesn't support a socket.
>
> Does anyone know the problem and does anyone have a conclusion to solve
> it? I tried to change the readStream to a socketStream but more problems
> awake after that ;)
>
> Thanks for your help!
> Stefan
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>  
Attached is a Kom patch.  I was hoping to get this fixed in the Kom base
but it looks like I will include it as an override in the next release
of SeasideTesting.

David


'From Squeak3.9gamma of ''23 July 2006'' [latest update: #7060] on 26 September 2006 at 7:59:37 am'!

!HttpRequest methodsFor: 'initialize-release' stamp: 'cds 9/23/2006 00:59'!
initRemoteAddress
        (stream respondsTo: #socket)
                ifTrue: [self remoteAddress: stream socket remoteAddress]! !


_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside Testing Framework with Seaside 2.7

Adrian Lienhard
In reply to this post by Berger Stefan-2
you might also be interested in a slightly different testing approach  
provided by Albatross:
http://lists.squeakfoundation.org/pipermail/seaside/2006-October/ 
009259.html

Now there is also Andrea's report available online: http://
www.iam.unibe.ch/~scg/Archive/Projects/Brue06a.pdf

Cheers,
Adrian

On Nov 7, 2006, at 15:37 , Berger Stefan wrote:

> Hi all,
>
> I tried to test a seaside application with Seaside2.7a1-mb.115 and
> SeasideTesting-R1.4-cds.1
>
> The WACounterTest and all other applications failed, because the  
> Session
> could not get initialized.
>
> I figured that in SCBrowserSimulator>>httpGetRequestStreamFor:url a
> readStream was given. But later on in the  
> HttpRequest>>initRemoteAddress
> will try to access a socket from the stream. Unfortunately the
> readStream doesn't support a socket.
>
> Does anyone know the problem and does anyone have a conclusion to  
> solve
> it? I tried to change the readStream to a socketStream but more  
> problems
> awake after that ;)
>
> Thanks for your help!
> Stefan
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside Testing Framework with Seaside 2.7

Martin Beck-3
In reply to this post by cdavidshaffer
David Shaffer schrieb:

> Berger Stefan wrote:
>> Hi all,
>>
>> I tried to test a seaside application with Seaside2.7a1-mb.115 and
>> SeasideTesting-R1.4-cds.1
>>
>> The WACounterTest and all other applications failed, because the Session
>> could not get initialized.
>>
>> I figured that in SCBrowserSimulator>>httpGetRequestStreamFor:url a
>> readStream was given. But later on in the HttpRequest>>initRemoteAddress
>> will try to access a socket from the stream. Unfortunately the
>> readStream doesn't support a socket.
>>
>> Does anyone know the problem and does anyone have a conclusion to solve
>> it? I tried to change the readStream to a socketStream but more problems
>> awake after that ;)
>>
>> Thanks for your help!
>> Stefan
>> _______________________________________________
>> Seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>  
> Attached is a Kom patch.  I was hoping to get this fixed in the Kom base
> but it looks like I will include it as an override in the next release
> of SeasideTesting.
>
> David
>

Thanks for the patch. This error went away. But another problem is, that
SCTestRunner and SCTestCaseViewer use the old Seaside Rendering API
(WAHtmlRenderer) and not the new WARenderCanvas. If we change the
rendererClass manually, it seems to work... Do you plan a new version or
a patch?

Regards,
Martin
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside Testing Framework with Seaside 2.7

cdavidshaffer
Martin Beck wrote:
>
> Thanks for the patch. This error went away. But another problem is,
> that SCTestRunner and SCTestCaseViewer use the old Seaside Rendering
> API (WAHtmlRenderer) and not the new WARenderCanvas. If we change the
> rendererClass manually, it seems to work... Do you plan a new version
> or a patch?

...a new version.   Thanks for pointing out this problem.  I am
currently only supporting Seaside 2.5 and 2.6 but this would be an easy
fix to make 2.7 work as well.

David


_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside