incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexis Willemyns" <alexiswillem...@gmail.com>
Subject Re: JEUT Champion Recruitment
Date Fri, 16 May 2008 12:15:26 GMT
"it is a model regression testing tool"

Yes, but I don't like the word "regression". In a first step, it's
a "checking" testing framework, and in a second step, it becomes a
"regression" testing framework in the lifecyle of an application.

I am happy that my some examples help you to have a deeper view of the JEUT
goals.

Thanks for your interest.

Alexis


2008/5/16, Andrus Adamchik <andrus@objectstyle.org>:
>
> Hi Alexis,
>
> Thanks for clarifying. It matches my earlier understanding - it is a model
> regression testing tool. I am not saying it is not useful, just wanted to
> define the terms so that we have an understanding of what JEUT is.
>
> Andrus
>
>
> On May 16, 2008, at 6:27 AM, Alexis Willemyns wrote:
>
>> On a technical note, the best solution is to explain you an example. As
>> for
>> every layer in an application, unit tests are welcome. This is too true
>> for
>> the entities mapped via JPA. So if you want to test an entity, you will
>> create an unit test class (for example with JUnit). In this class, you
>> will
>> add some tests. For example, you will write a test that create an instance
>> of the entity, set values, persist the entity, retrieve the entity, and
>> check if the retrieved object is exactly the same as the persisted entity.
>> It allows you to control that your annotations are matching the definition
>> of the real table in the database. You can do extra tests: check the
>> nullable attribute, the length attribute, the unique constraints, and so
>> on... But if you want to test every aspect of your entity, you will write
>> a
>> big piece of code for each entity! If you have a model with 10, 20 or more
>> entities, you see directly the quantity of work. JEUT is designed to
>> automate for you the testing of an entity. You have just to create a test
>> class that extends a specific JEUT test class and all the work is done for
>> you. The framework uses the annotations discovered via reflection API or
>> the
>> XML files (orm.xml).
>>
>> Do you understand the goal of JEUT?
>>
>>
>> 2008/5/15, Andrus Adamchik <andrus@objectstyle.org>:
>>
>>>
>>> Hi Alexis,
>>>
>>> I think it would really help if you started developing in the open using
>>> one of the free open source sites. This would provide the project history
>>> to
>>> a potential Champion, including access to the source code and general
>>> feel
>>> of whether you are really interested in building community around your
>>> code.
>>>
>>> On a technical note, what exactly does this framework test? Is this
>>> regression testing (i.e. checking that the ORM schema matches the actual
>>> DB
>>> schema), or is there a value beyond that? We had a similar framework
>>> submitted to the Cayenne project some time back, and I could never
>>> understand what exactly is being tested.
>>>
>>> Andrus
>>>
>>>
>>> On May 15, 2008, at 9:57 AM, Alexis Willemyns wrote:
>>>
>>> Hello all,
>>>>
>>>> I was a little bit hesitant before posting this project proposition. But
>>>> let's go! I hope that this attempt will be a success.
>>>>
>>>> JEUT stands for "JPA Entity Unit Test" and is currently in development.
>>>> So
>>>> there is no public website and the code is ended up to 70%. JEUT is a
>>>> testing framework for JPA entities and its main goal is to automate the
>>>> test
>>>> of entities without the need to write long and boring home tests.
>>>>
>>>> The mission is to provide a framework which is able to test the matching
>>>> between entities using annotations and/or xml descriptors and the real
>>>> database. A framework 100% compliant with all the existing annotations
>>>> in
>>>> JPA, for the current version 1 (and the future version 2... in the
>>>> future).
>>>>
>>>> JEUT analyzes all the annotations and creates instances of entites with
>>>> random values. It tries to persist these instances via the entity
>>>> manager
>>>> and reports the problems if existing. JEUT can be used as an extension
>>>> of
>>>> JUnit or TestNG, or maybe all others test frameworks.
>>>>
>>>> For the moment, the team is only composed with me, and I have discussed
>>>> with
>>>> my self about what is means to become an Apacha project. I am aware what
>>>> are
>>>> the conditions, responsabilities and impacts to become an Apache
>>>> project.
>>>> I
>>>> am looking a Champion to go in the proposal phase (if the proposal makes
>>>> sense) and to build a community around JEUT.
>>>>
>>>> Thank you for any feedback and recommendations (and sorry for my english
>>>> coming from Belgium).
>>>>
>>>> I look forward to your responses.
>>>>
>>>> Regards,
>>>>
>>>> Alexis Willemyns
>>>> JEUT project founder
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message