TCK next steps?

[Mark Struberg <st...@yahoo.de>]

Hi Gurkan!

It seems we have been working on the same part - but your implementation is a _lot_ more readable than my quickly hacked one ;)

One thing which I also experienced so far: There are a LOT of things to be resolved at the @BeforeClass initialisation. This is the reason why most of the tests are simply skipped.


LieGrue,
strub 

PS: I will not have that much time the next week since I'm skiing.


      

Re: TCK next steps?

[Mark Struberg <st...@yahoo.de>]

getting all TCK tests working will be a lot of work ;)
But I think we are on track now, since we have something we can put our hands on. 

My plans for the next time:

a.) digging in to the TCK to get more and more working
b.) setup Geronimo with OWB + writing SPI for getting the TransactionalEntityManager and stuff from OpenEJB.

But as said yesterday, I will not have much time this week since I'm on skiing holidays until saturday. So don't hesitate to hack the TCKs :)


LieGrue,
strub

--- Gurkan Erdogdu <gu...@yahoo.com> schrieb am Sa, 28.2.2009:

> Von: Gurkan Erdogdu <gu...@yahoo.com>
> Betreff: Re: TCK next steps?
> An: openwebbeans-dev@incubator.apache.org
> Datum: Samstag, 28. Februar 2009, 11:35
> Hi Mark;
> 
> I really appreciated your work about TCK implementation.
> Its very good start to check TCK tests. As you said, I have
> faced lots of exceptions, skipping tests etc while I was
> running the tests. I have resolved some of them but it takes
> lots of time, because I had to dig into the details via
> Eclipse debugger. I have also some questions that I am going
> to ask in the @webbeansdev list.
> 
> I realized that when TestNG throws exception before
> starting to tests, it simply skipped the tests. I debugged 
> exceptional cases, I noticed that some of the concepts 
> maybe   not understand by us or jboss guys :)
> 
> 
> Moreover, some tests are written for the "Enterprise
> Beans" that OpenWebBeans do not handle them, so tests
> throw exceptions.
> 
> I think that in the minumum our implementation must pass
> the core tests that are related with the our implemented
> artifacts, such as "Contexts, Injection, Resolution,
> Observers etc." 
> 
> Moreover, we have to implement the other parts of the
> specification, including  Enterprise Beans, JMS  and
> remaining XML stuff to run TCK tests fully. Actually we are
> on the very good track. Maybe you can continue to implement
> our TCK if you wish and I try to continue to finish the
> remaining parts of the specification.
> 
> What do you think guys? I think we may run a bit faster :) 
> 
> Help is very appreciated!
> 
> Thanks;
> 
> /Gurkan
> 
> 
> 
> 
> ________________________________
> From: Mark Struberg <st...@yahoo.de>
> To: openwebbeans-dev@incubator.apache.org
> Sent: Saturday, February 28, 2009 1:46:30 AM
> Subject: TCK next steps?
> 
> Hi Gurkan!
> 
> It seems we have been working on the same part - but your
> implementation is a _lot_ more readable than my quickly
> hacked one ;)
> 
> One thing which I also experienced so far: There are a LOT
> of things to be resolved at the @BeforeClass initialisation.
> This is the reason why most of the tests are simply skipped.
> 
> 
> LieGrue,
> strub 
> 
> PS: I will not have that much time the next week since
> I'm skiing.


      

Re: TCK next steps?

[Gurkan Erdogdu <gu...@yahoo.com>]

Hi Mark;

I really appreciated your work about TCK implementation. Its very good start to check TCK tests. As you said, I have faced lots of exceptions, skipping tests etc while I was running the tests. I have resolved some of them but it takes lots of time, because I had to dig into the details via Eclipse debugger. I have also some questions that I am going to ask in the @webbeansdev list.

I realized that when TestNG throws exception before starting to tests, it simply skipped the tests. I debugged  exceptional cases, I noticed that some of the concepts  maybe   not understand by us or jboss guys :)


Moreover, some tests are written for the "Enterprise Beans" that OpenWebBeans do not handle them, so tests throw exceptions.

I think that in the minumum our implementation must pass the core tests that are related with the our implemented artifacts, such as "Contexts, Injection, Resolution, Observers etc." 

Moreover, we have to implement the other parts of the specification, including  Enterprise Beans, JMS  and remaining XML stuff to run TCK tests fully. Actually we are on the very good track. Maybe you can continue to implement our TCK if you wish and I try to continue to finish the remaining parts of the specification.

What do you think guys? I think we may run a bit faster :) 

Help is very appreciated!

Thanks;

/Gurkan




________________________________
From: Mark Struberg <st...@yahoo.de>
To: openwebbeans-dev@incubator.apache.org
Sent: Saturday, February 28, 2009 1:46:30 AM
Subject: TCK next steps?

Hi Gurkan!

It seems we have been working on the same part - but your implementation is a _lot_ more readable than my quickly hacked one ;)

One thing which I also experienced so far: There are a LOT of things to be resolved at the @BeforeClass initialisation. This is the reason why most of the tests are simply skipped.


LieGrue,
strub 

PS: I will not have that much time the next week since I'm skiing.