[Grok-dev] Grok Research

[Noe Nieto]

Yes.

When you generate a grok project it also generates a test suite for you.

--
Noe

2012/9/2 Holger S. <holger.s at fu-berlin.de>

>  Hi,
>
> thank you very much for the quick responsde and the link, I hadn't found
> it before :)
>
> Another question: Is testing common practice among grok developers?
>
> Regards,
> Holger
>
> Am 28.08.2012 14:33, schrieb Noe Nieto:
>
> Grok is centered about the ZODB and the Zope Component Architecture. This
> is very unique with respect to frameworks that are built around SQL
> statements.
>
> So, yes, Its better to think about components. There are four basic
> concepts: Interfaces, Adapters, Utilities and Persistence. Every major
> piece of your application is a component.
>
> I recommend reading this:
> http://www.muthukadan.net/docs/zca.html*
>
> --
> Noe
>
> *
> 2012/8/28 Holger S. <holger.s at fu-berlin.de>
>
>>  Hello,
>>
>> we at the Free University Berlin *are holding a contest, where *top-class
>> teams of three programmers compete to implement the same requirements for a
>> web-based system within two days, using different technology platforms (
>> https://www.plat-forms.org/). *Its purpose* is not to determine "the"
>> best platform, but rather to provide new insights into the real (rather
>> than purported) pros, cons, and emergent properties of each platform.
>>
>> We used to discern platforms by language, but found that similar web
>> frameworks can make properties of solutions similar over different
>> languages. So, because it is one, we are also investing the properties of
>> grok :-)
>> And this is where I need your help on two questions:
>>
>>     - what is the typical development procedure when developing a web
>> application with grok?
>>         We want to find out in what steps a developer implements an
>> application in a framework, for example whether they start with models,
>> templates or tests.
>>         Is this somewhat similar to the procedure in this tutorial?
>>         http://grok.zope.org/documentation/tutorial/grok-poller-tutorial
>>
>>         1. bootstrap grok
>>         2. write model classes
>>         3. for each user story
>>             a. write views
>>             b. write tests
>>             c. write templates
>>
>>     - what is the mental model when writing a grok application? Do you
>> think in terms of URLs, actions, form, components?
>>
>> Regards,
>> Holger
>>
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev at zope.org
>> https://mail.zope.org/mailman/listinfo/grok-dev
>>
>>
>
>
> --
> ---
> Noe Nieto
> NNieto Consulting Services
> M: nnieto at noenieto.com
> W: http://noenieto.com
> T:  @tzicatl <https://twitter.com/#%21/tzicatl>
> Li: Perfil en LinkedIn <http://www.linkedin.com/profile/view?id=84300665>
>
>
>


-- 
---
Noe Nieto
NNieto Consulting Services
M: nnieto at noenieto.com
W: http://noenieto.com
T:  @tzicatl <https://twitter.com/#%21/tzicatl>
Li: Perfil en LinkedIn <http://www.linkedin.com/profile/view?id=84300665>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.zope.org/pipermail/grok-dev/attachments/20120902/5a4302cf/attachment.html>