[Grok-dev] testing apps with grok-1.1a1

[Souheil CHELFOUH]

I got lost during the week end so I couldn't work on all the things I
was supposed to
To summarize, I still need to adapt the grokcore.view to the latest
zope.browserresource
I need to work on the deprecation imports of Grok itself too.

I moved all snappy/dolmen packages to grok 1.1a
It required so changes and I released all the modified packages already.
It simplified everything and I didn't run into any show stoppers.

One thing that is / might be bothering for people, is that zodbupdate
doesn't run with the ztk 1.0dev
This is unfortunate if you need to change a class by another,
following the migration

- Souheil


2009/11/30 Jan-Wijbrand Kolman <janwijbrand at gmail.com>:
> Hi,
>
> I'd like to hear from you guys... :-)
>
> Are your apps running on grok-1.1a1, based on ZTK?
>
>
> Our applications are. It took little a bit of work, but not much:
>
>
> * hurry.query:
>
> The 0.9.2 release of hurry.query still uses the "old" zapi imports.
> These are gone in ZTK. Today I released hurry.query 1.0 since the trunk
> already had the clean ups required to make it "ZTK compatible".
>
>
> * (Functional)tests that rely on repr() of folder and sites:
>
> zope.app.folder.folder.Folder has been moved to zope.site.folder.
>
>
> * Testbrowser/mechanize error messages have changed slightly:
>
> What used to be:
>
>   httperror_seek_wrapper: HTTP Error 403: Forbidden
>
> Now is:
>
>   HTTPError: HTTP Error 403: Forbidden
>
> And other HTTP error message have changed in a similar fashion.
>
>
> * zope.session cookie-setting behaviour has changed slightly.
>
> In some of our functional tests we checked the HTTP response headers,
> and saw that the headers related to setting cookies (by the client id
> manager) were a bit different. As it turns out, zope.session will
> trigger this cookie only when it actually is needed and when it does, it
> will also set a series of response headers that shoudl prevent any
> caching of the response. NO biggy, but we had to play around a little to
> get our test output correct again.
>
>
> Tomorrow I'll migrate another bigger app to grok-on-ZTK and see what
> happens there. So far, the migration is rather painless. Good!
>
> Do people have more test results? What about doing an second alpha
> quickly, where hopefully some of the deprecated imports have been removed?
>
> regards,
> jw
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev
>