Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc)  » Issue with loading properties from a CDO resource in Library Example project
Issue with loading properties from a CDO resource in Library Example project [message #2635] Mon, 14 November 2005 07:44 Go to next message
Eclipse UserFriend
Originally posted by: tvalence1.cox.net

Greetings,



I have been investigating an issue with populating a model with properties
from a CDO resource that has been persisted in MySql. I believe that I have
been able to reproduce a similar behavior with the Library Example project
using the latest code from CVS.



In this instance, the
org.eclipse.net4j.cdo.test.actions.LoadResourceAction.loadRe source method
succeeds in accessing and printing the name of the first author (Einstein),
but throws an exception when trying to access the second author (Dahl)
object from the library resource. The relevant code snippet and a debug
trace of LoadResourceAction's operation is attached for reference.



Note that an expansion of the persisted library resource using the Library
Model Editor works with no problems in my eClipse 3.1.0/JDK 1.5 development
environment.



Please advise on how I can resolve this issue. I can send additional
configuration and trace information if this can further define the problem.



Thanks!

= Ted




Re: Issue with loading properties from a CDO resource in Library Example project [message #2664 is a reply to message #2635] Mon, 14 November 2005 07:53 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: tvalence1.cox.net

Sorry. The correct code snippet is in the updated attachment.

- Ted


"TVal" <tvalence1@cox.net> wrote in message
news:dl9f91$93j$1@news.eclipse.org...
> Greetings,
>
>
>
> I have been investigating an issue with populating a model with properties
> from a CDO resource that has been persisted in MySql. I believe that I
> have
> been able to reproduce a similar behavior with the Library Example project
> using the latest code from CVS.
>
>
>
> In this instance, the
> org.eclipse.net4j.cdo.test.actions.LoadResourceAction.loadRe source method
> succeeds in accessing and printing the name of the first author
> (Einstein),
> but throws an exception when trying to access the second author (Dahl)
> object from the library resource. The relevant code snippet and a debug
> trace of LoadResourceAction's operation is attached for reference.
>
>
>
> Note that an expansion of the persisted library resource using the Library
> Model Editor works with no problems in my eClipse 3.1.0/JDK 1.5
> development
> environment.
>
>
>
> Please advise on how I can resolve this issue. I can send additional
> configuration and trace information if this can further define the
> problem.
>
>
>
> Thanks!
>
> = Ted
>
>
>
>
>


Re: Issue with loading properties from a CDO resource in Library Example project [message #2697 is a reply to message #2664] Mon, 14 November 2005 10:33 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: stepper.sympedia.de

Hi Ted,

You are right, I could also observe this issue with the library example
and the newest CDO version. It took me quite some while but I was able
to fix it. Please update to LATEST.

I really hope that I didn't break something else. If only I had time
to settle proper regression tests...

Cheers
/Eike


TVal schrieb:
> Sorry. The correct code snippet is in the updated attachment.
>
> - Ted
>
>
> "TVal" <tvalence1@cox.net> wrote in message
> news:dl9f91$93j$1@news.eclipse.org...
>
>>Greetings,
>>
>>
>>
>>I have been investigating an issue with populating a model with properties
>>from a CDO resource that has been persisted in MySql. I believe that I
>>have
>>been able to reproduce a similar behavior with the Library Example project
>>using the latest code from CVS.
>>
>>
>>
>>In this instance, the
>> org.eclipse.net4j.cdo.test.actions.LoadResourceAction.loadRe source method
>>succeeds in accessing and printing the name of the first author
>>(Einstein),
>>but throws an exception when trying to access the second author (Dahl)
>>object from the library resource. The relevant code snippet and a debug
>>trace of LoadResourceAction's operation is attached for reference.
>>
>>
>>
>>Note that an expansion of the persisted library resource using the Library
>>Model Editor works with no problems in my eClipse 3.1.0/JDK 1.5
>>development
>>environment.
>>
>>
>>
>>Please advise on how I can resolve this issue. I can send additional
>>configuration and trace information if this can further define the
>>problem.
>>
>>
>>
>>Thanks!
>>
>>= Ted
>>
>>
>>
>>
>>
>
>
>
Re: Issue with loading properties from a CDO resource in Library Example project [message #2716 is a reply to message #2697] Tue, 15 November 2005 07:04 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: tvalence1.cox.net

Thanks for the near real-time response Eike.

The LATEST version of the CDO implementation resolved the reported issue
with the Library Example.

Moreover, I also verified that this update also resolved the issues that I
previously observed in the navigation and retrieval of properties in my
application's model. :)

Please let me know if I can be of assistance in setting up your regression
test suites.

Cheers.
- Ted


"Eike Stepper" <stepper@sympedia.de> wrote in message
news:dl9p51$m6u$1@news.eclipse.org...
> Hi Ted,
>
> You are right, I could also observe this issue with the library example
> and the newest CDO version. It took me quite some while but I was able
> to fix it. Please update to LATEST.
>
> I really hope that I didn't break something else. If only I had time
> to settle proper regression tests...
>
> Cheers
> /Eike
>
>
> TVal schrieb:
>> Sorry. The correct code snippet is in the updated attachment.
>>
>> - Ted
>>
>>
>> "TVal" <tvalence1@cox.net> wrote in message
>> news:dl9f91$93j$1@news.eclipse.org...
>>
>>>Greetings,
>>>
>>>
>>>
>>>I have been investigating an issue with populating a model with
>>>properties
>>>from a CDO resource that has been persisted in MySql. I believe that I
>>>have
>>>been able to reproduce a similar behavior with the Library Example
>>>project
>>>using the latest code from CVS.
>>>
>>>
>>>
>>>In this instance, the
>>> org.eclipse.net4j.cdo.test.actions.LoadResourceAction.loadRe source method
>>>succeeds in accessing and printing the name of the first author
>>>(Einstein),
>>>but throws an exception when trying to access the second author (Dahl)
>>>object from the library resource. The relevant code snippet and a debug
>>>trace of LoadResourceAction's operation is attached for reference.
>>>
>>>
>>>
>>>Note that an expansion of the persisted library resource using the
>>>Library
>>>Model Editor works with no problems in my eClipse 3.1.0/JDK 1.5
>>>development
>>>environment.
>>>
>>>
>>>
>>>Please advise on how I can resolve this issue. I can send additional
>>>configuration and trace information if this can further define the
>>>problem.
>>>
>>>
>>>
>>>Thanks!
>>>
>>>= Ted
>>>
>>>
>>>
>>>
>>>
>>
>>
Re: Issue with loading properties from a CDO resource in Library Example project [message #4091 is a reply to message #2716] Tue, 15 November 2005 09:55 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: stepper.sympedia.de

TVal schrieb:
> Thanks for the near real-time response Eike.

Just evaluating my brand new and throughput optimized "Multi Threaded Brain 2.1" ;-)


> The LATEST version of the CDO implementation resolved the reported issue
> with the Library Example.
>
> Moreover, I also verified that this update also resolved the issues that I
> previously observed in the navigation and retrieval of properties in my
> application's model. :)

That's good to hear!


> Please let me know if I can be of assistance in setting up your regression
> test suites.

That's even better to hear ;-)

The most important things to test (by degrading importance) are:
1) Create and/or manipulate various model instances, commit to database and check db state.
2) Prepare various db states, load models from database and check the models.
3) Combinations of 1) + 2) with a focus on InvalidationNotifications in multi client setups.

What do you think?

Cheers
/Eike
Re: Issue with loading properties from a CDO resource in Library Example project [message #4147 is a reply to message #4091] Wed, 16 November 2005 16:21 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: tvalence1.cox.net

Eike,

The list looks like a good start.

Did you have a particular set of models (e.g. Library Example) in mind for
the regression testing?

Thanks.
= Ted

"Eike Stepper" <stepper@sympedia.de> wrote in message
news:dlcb9h$idg$1@news.eclipse.org...
> TVal schrieb:
>> Thanks for the near real-time response Eike.
>
> Just evaluating my brand new and throughput optimized "Multi Threaded
> Brain 2.1" ;-)
>
>
>> The LATEST version of the CDO implementation resolved the reported issue
>> with the Library Example.
>>
>> Moreover, I also verified that this update also resolved the issues that
>> I previously observed in the navigation and retrieval of properties in my
>> application's model. :)
>
> That's good to hear!
>
>
>> Please let me know if I can be of assistance in setting up your
>> regression test suites.
>
> That's even better to hear ;-)
>
> The most important things to test (by degrading importance) are:
> 1) Create and/or manipulate various model instances, commit to database
> and check db state.
> 2) Prepare various db states, load models from database and check the
> models.
> 3) Combinations of 1) + 2) with a focus on InvalidationNotifications in
> multi client setups.
>
> What do you think?
>
> Cheers
> /Eike
>
Re: Issue with loading properties from a CDO resource in Library Example project [message #4218 is a reply to message #4147] Thu, 17 November 2005 07:50 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: stepper.sympedia.de

> Did you have a particular set of models (e.g. Library Example) in mind for
> the regression testing?

No. I think we can use model(s) that are specifically designed to support the test cases.
They should enable the test logic to use all the EMF features that are supported by CDO.
In general we can assume, that each method of the generated model API that leads to
notification sending should be tested with all kinds of argument vales and in various
call orders.

I'm quite sure that we will have some different sorts of test environment. For example
item 3 of my previous scenario list is the only one with multiple clients, the test client
will have to have very fine control over thread sync.

Btw. I will leave for a 2 weeks vacation tomorrow and there will (intentionally ;-) )
be no phone or email. After I returned I can start to think about these environmental
test aspects.

If you are willing you could start to specify the test cases from a pure CDO client's
point of view. In some simple pseudo notation, just to see the requirements of the
needed test framework:

PRECONDITION/EXECUTION
1. create resource R1
2. create object of class X (described somewhere else),
populate it with (a=?, ...)
add it to R1 contents
3. commit

EXPECTED RESULT
- describe client side process state (if applicable)
- describe server side process state (if applicable)
- describe server side database state (if applicable)

Something like that would already be a great deal ;-)
If you have questions, I'm still here today...

Cheers
/Eike
CDO Regression Testing [message #4289 is a reply to message #4218] Thu, 17 November 2005 19:15 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: tvalence1.cox.net

Eike,

Can we draft a test strategy for mapping out the different aspects of the
test effort?

Such a document could help us coordinate a distributed test effort while
ensuring that we satisfy test coverage requirements for a well-defined
scope. The strategy doc would also provide the context and standards for
developing test cases and supporting infrastructure/tools.

The eClipse TPTP project has a nice test strategy document that we could
potentially tailor to suit our needs for CDO testing.
http://eclipse.org/tptp/home/documents/process/TPTP_Testing_ Strategy.html

Your thoughts?

Thanks, and have a great vacation! :)
- Ted


"Eike Stepper" <stepper@sympedia.de> wrote in message
news:dlhcp2$i6h$1@news.eclipse.org...
>> Did you have a particular set of models (e.g. Library Example) in mind
>> for the regression testing?
>
> No. I think we can use model(s) that are specifically designed to support
> the test cases.
> They should enable the test logic to use all the EMF features that are
> supported by CDO.
> In general we can assume, that each method of the generated model API that
> leads to
> notification sending should be tested with all kinds of argument vales and
> in various
> call orders.
>
> I'm quite sure that we will have some different sorts of test environment.
> For example
> item 3 of my previous scenario list is the only one with multiple clients,
> the test client
> will have to have very fine control over thread sync.
>
> Btw. I will leave for a 2 weeks vacation tomorrow and there will
> (intentionally ;-) )
> be no phone or email. After I returned I can start to think about these
> environmental
> test aspects.
>
> If you are willing you could start to specify the test cases from a pure
> CDO client's
> point of view. In some simple pseudo notation, just to see the
> requirements of the
> needed test framework:
>
> PRECONDITION/EXECUTION
> 1. create resource R1
> 2. create object of class X (described somewhere else),
> populate it with (a=?, ...)
> add it to R1 contents
> 3. commit
>
> EXPECTED RESULT
> - describe client side process state (if applicable)
> - describe server side process state (if applicable)
> - describe server side database state (if applicable)
>
> Something like that would already be a great deal ;-)
> If you have questions, I'm still here today...
>
> Cheers
> /Eike
Re: CDO Regression Testing [message #7369 is a reply to message #4289] Thu, 15 December 2005 10:15 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: stepper.sympedia.de

TVal schrieb:
> Eike,
>
> Can we draft a test strategy for mapping out the different aspects of the
> test effort?

There's nothing against it, in general.
I've had a look at the document you referred to below and I
got a little bit the impression that TPTP is bigger than CDO ;-)

What about the following:
- I start to gather some (test) requirements from a very technical point of view,
such as test environments (network, db, ...), test code generation (merlin),
test automation and the like.
- I leave it to you to take these snippets and combine them with appropriate
elements from the TPTP doc.



> Such a document could help us coordinate a distributed test effort while
> ensuring that we satisfy test coverage requirements for a well-defined
> scope. The strategy doc would also provide the context and standards for
> developing test cases and supporting infrastructure/tools.
>
> The eClipse TPTP project has a nice test strategy document that we could
> potentially tailor to suit our needs for CDO testing.
> http://eclipse.org/tptp/home/documents/process/TPTP_Testing_ Strategy.html
>
> Your thoughts?
>
> Thanks, and have a great vacation! :)
> - Ted

Thanks ;-)

/Eike
Re: CDO Regression Testing [message #7390 is a reply to message #7369] Thu, 15 December 2005 17:18 Go to previous message
Eclipse UserFriend
Originally posted by: tvalence1.cox.net

Eike,

Sounds like a great approach.

I look forward to your technical test requirements.

Thanks.
- Ted

"Eike Stepper" <stepper@sympedia.de> wrote in message
news:dnrfnf$6ss$1@news.eclipse.org...
>
> TVal schrieb:
>> Eike,
>>
>> Can we draft a test strategy for mapping out the different aspects of the
>> test effort?
>
> There's nothing against it, in general.
> I've had a look at the document you referred to below and I
> got a little bit the impression that TPTP is bigger than CDO ;-)
>
> What about the following:
> - I start to gather some (test) requirements from a very technical point
> of view,
> such as test environments (network, db, ...), test code generation
> (merlin),
> test automation and the like.
> - I leave it to you to take these snippets and combine them with
> appropriate
> elements from the TPTP doc.
>
>
>
>> Such a document could help us coordinate a distributed test effort while
>> ensuring that we satisfy test coverage requirements for a well-defined
>> scope. The strategy doc would also provide the context and standards for
>> developing test cases and supporting infrastructure/tools.
>>
>> The eClipse TPTP project has a nice test strategy document that we could
>> potentially tailor to suit our needs for CDO testing.
>> http://eclipse.org/tptp/home/documents/process/TPTP_Testing_ Strategy.html
>>
>> Your thoughts?
>>
>> Thanks, and have a great vacation! :)
>> - Ted
>
> Thanks ;-)
>
> /Eike
Re: Issue with loading properties from a CDO resource in Library Example project [message #561393 is a reply to message #2635] Mon, 14 November 2005 07:53 Go to previous message
Eclipse UserFriend
Originally posted by: tvalence1.cox.net

Sorry. The correct code snippet is in the updated attachment.

- Ted


"TVal" <tvalence1@cox.net> wrote in message
news:dl9f91$93j$1@news.eclipse.org...
> Greetings,
>
>
>
> I have been investigating an issue with populating a model with properties
> from a CDO resource that has been persisted in MySql. I believe that I
> have
> been able to reproduce a similar behavior with the Library Example project
> using the latest code from CVS.
>
>
>
> In this instance, the
> org.eclipse.net4j.cdo.test.actions.LoadResourceAction.loadRe source method
> succeeds in accessing and printing the name of the first author
> (Einstein),
> but throws an exception when trying to access the second author (Dahl)
> object from the library resource. The relevant code snippet and a debug
> trace of LoadResourceAction's operation is attached for reference.
>
>
>
> Note that an expansion of the persisted library resource using the Library
> Model Editor works with no problems in my eClipse 3.1.0/JDK 1.5
> development
> environment.
>
>
>
> Please advise on how I can resolve this issue. I can send additional
> configuration and trace information if this can further define the
> problem.
>
>
>
> Thanks!
>
> = Ted
>
>
>
>
>


Re: Issue with loading properties from a CDO resource in Library Example project [message #561412 is a reply to message #2664] Mon, 14 November 2005 10:33 Go to previous message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6657
Registered: July 2009
Senior Member
Hi Ted,

You are right, I could also observe this issue with the library example
and the newest CDO version. It took me quite some while but I was able
to fix it. Please update to LATEST.

I really hope that I didn't break something else. If only I had time
to settle proper regression tests...

Cheers
/Eike


TVal schrieb:
> Sorry. The correct code snippet is in the updated attachment.
>
> - Ted
>
>
> "TVal" <tvalence1@cox.net> wrote in message
> news:dl9f91$93j$1@news.eclipse.org...
>
>>Greetings,
>>
>>
>>
>>I have been investigating an issue with populating a model with properties
>>from a CDO resource that has been persisted in MySql. I believe that I
>>have
>>been able to reproduce a similar behavior with the Library Example project
>>using the latest code from CVS.
>>
>>
>>
>>In this instance, the
>> org.eclipse.net4j.cdo.test.actions.LoadResourceAction.loadRe source method
>>succeeds in accessing and printing the name of the first author
>>(Einstein),
>>but throws an exception when trying to access the second author (Dahl)
>>object from the library resource. The relevant code snippet and a debug
>>trace of LoadResourceAction's operation is attached for reference.
>>
>>
>>
>>Note that an expansion of the persisted library resource using the Library
>>Model Editor works with no problems in my eClipse 3.1.0/JDK 1.5
>>development
>>environment.
>>
>>
>>
>>Please advise on how I can resolve this issue. I can send additional
>>configuration and trace information if this can further define the
>>problem.
>>
>>
>>
>>Thanks!
>>
>>= Ted
>>
>>
>>
>>
>>
>
>
>


Re: Issue with loading properties from a CDO resource in Library Example project [message #561431 is a reply to message #2697] Tue, 15 November 2005 07:04 Go to previous message
Eclipse UserFriend
Originally posted by: tvalence1.cox.net

Thanks for the near real-time response Eike.

The LATEST version of the CDO implementation resolved the reported issue
with the Library Example.

Moreover, I also verified that this update also resolved the issues that I
previously observed in the navigation and retrieval of properties in my
application's model. :)

Please let me know if I can be of assistance in setting up your regression
test suites.

Cheers.
- Ted


"Eike Stepper" <stepper@sympedia.de> wrote in message
news:dl9p51$m6u$1@news.eclipse.org...
> Hi Ted,
>
> You are right, I could also observe this issue with the library example
> and the newest CDO version. It took me quite some while but I was able
> to fix it. Please update to LATEST.
>
> I really hope that I didn't break something else. If only I had time
> to settle proper regression tests...
>
> Cheers
> /Eike
>
>
> TVal schrieb:
>> Sorry. The correct code snippet is in the updated attachment.
>>
>> - Ted
>>
>>
>> "TVal" <tvalence1@cox.net> wrote in message
>> news:dl9f91$93j$1@news.eclipse.org...
>>
>>>Greetings,
>>>
>>>
>>>
>>>I have been investigating an issue with populating a model with
>>>properties
>>>from a CDO resource that has been persisted in MySql. I believe that I
>>>have
>>>been able to reproduce a similar behavior with the Library Example
>>>project
>>>using the latest code from CVS.
>>>
>>>
>>>
>>>In this instance, the
>>> org.eclipse.net4j.cdo.test.actions.LoadResourceAction.loadRe source method
>>>succeeds in accessing and printing the name of the first author
>>>(Einstein),
>>>but throws an exception when trying to access the second author (Dahl)
>>>object from the library resource. The relevant code snippet and a debug
>>>trace of LoadResourceAction's operation is attached for reference.
>>>
>>>
>>>
>>>Note that an expansion of the persisted library resource using the
>>>Library
>>>Model Editor works with no problems in my eClipse 3.1.0/JDK 1.5
>>>development
>>>environment.
>>>
>>>
>>>
>>>Please advise on how I can resolve this issue. I can send additional
>>>configuration and trace information if this can further define the
>>>problem.
>>>
>>>
>>>
>>>Thanks!
>>>
>>>= Ted
>>>
>>>
>>>
>>>
>>>
>>
>>
Re: Issue with loading properties from a CDO resource in Library Example project [message #561451 is a reply to message #2716] Tue, 15 November 2005 09:55 Go to previous message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6657
Registered: July 2009
Senior Member
TVal schrieb:
> Thanks for the near real-time response Eike.

Just evaluating my brand new and throughput optimized "Multi Threaded Brain 2.1" ;-)


> The LATEST version of the CDO implementation resolved the reported issue
> with the Library Example.
>
> Moreover, I also verified that this update also resolved the issues that I
> previously observed in the navigation and retrieval of properties in my
> application's model. :)

That's good to hear!


> Please let me know if I can be of assistance in setting up your regression
> test suites.

That's even better to hear ;-)

The most important things to test (by degrading importance) are:
1) Create and/or manipulate various model instances, commit to database and check db state.
2) Prepare various db states, load models from database and check the models.
3) Combinations of 1) + 2) with a focus on InvalidationNotifications in multi client setups.

What do you think?

Cheers
/Eike


Re: Issue with loading properties from a CDO resource in Library Example project [message #561472 is a reply to message #4091] Wed, 16 November 2005 16:21 Go to previous message
Eclipse UserFriend
Originally posted by: tvalence1.cox.net

Eike,

The list looks like a good start.

Did you have a particular set of models (e.g. Library Example) in mind for
the regression testing?

Thanks.
= Ted

"Eike Stepper" <stepper@sympedia.de> wrote in message
news:dlcb9h$idg$1@news.eclipse.org...
> TVal schrieb:
>> Thanks for the near real-time response Eike.
>
> Just evaluating my brand new and throughput optimized "Multi Threaded
> Brain 2.1" ;-)
>
>
>> The LATEST version of the CDO implementation resolved the reported issue
>> with the Library Example.
>>
>> Moreover, I also verified that this update also resolved the issues that
>> I previously observed in the navigation and retrieval of properties in my
>> application's model. :)
>
> That's good to hear!
>
>
>> Please let me know if I can be of assistance in setting up your
>> regression test suites.
>
> That's even better to hear ;-)
>
> The most important things to test (by degrading importance) are:
> 1) Create and/or manipulate various model instances, commit to database
> and check db state.
> 2) Prepare various db states, load models from database and check the
> models.
> 3) Combinations of 1) + 2) with a focus on InvalidationNotifications in
> multi client setups.
>
> What do you think?
>
> Cheers
> /Eike
>
Re: Issue with loading properties from a CDO resource in Library Example project [message #561493 is a reply to message #4147] Thu, 17 November 2005 07:50 Go to previous message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6657
Registered: July 2009
Senior Member
> Did you have a particular set of models (e.g. Library Example) in mind for
> the regression testing?

No. I think we can use model(s) that are specifically designed to support the test cases.
They should enable the test logic to use all the EMF features that are supported by CDO.
In general we can assume, that each method of the generated model API that leads to
notification sending should be tested with all kinds of argument vales and in various
call orders.

I'm quite sure that we will have some different sorts of test environment. For example
item 3 of my previous scenario list is the only one with multiple clients, the test client
will have to have very fine control over thread sync.

Btw. I will leave for a 2 weeks vacation tomorrow and there will (intentionally ;-) )
be no phone or email. After I returned I can start to think about these environmental
test aspects.

If you are willing you could start to specify the test cases from a pure CDO client's
point of view. In some simple pseudo notation, just to see the requirements of the
needed test framework:

PRECONDITION/EXECUTION
1. create resource R1
2. create object of class X (described somewhere else),
populate it with (a=?, ...)
add it to R1 contents
3. commit

EXPECTED RESULT
- describe client side process state (if applicable)
- describe server side process state (if applicable)
- describe server side database state (if applicable)

Something like that would already be a great deal ;-)
If you have questions, I'm still here today...

Cheers
/Eike


CDO Regression Testing [message #561514 is a reply to message #4218] Thu, 17 November 2005 19:15 Go to previous message
Eclipse UserFriend
Originally posted by: tvalence1.cox.net

Eike,

Can we draft a test strategy for mapping out the different aspects of the
test effort?

Such a document could help us coordinate a distributed test effort while
ensuring that we satisfy test coverage requirements for a well-defined
scope. The strategy doc would also provide the context and standards for
developing test cases and supporting infrastructure/tools.

The eClipse TPTP project has a nice test strategy document that we could
potentially tailor to suit our needs for CDO testing.
http://eclipse.org/tptp/home/documents/process/TPTP_Testing_ Strategy.html

Your thoughts?

Thanks, and have a great vacation! :)
- Ted


"Eike Stepper" <stepper@sympedia.de> wrote in message
news:dlhcp2$i6h$1@news.eclipse.org...
>> Did you have a particular set of models (e.g. Library Example) in mind
>> for the regression testing?
>
> No. I think we can use model(s) that are specifically designed to support
> the test cases.
> They should enable the test logic to use all the EMF features that are
> supported by CDO.
> In general we can assume, that each method of the generated model API that
> leads to
> notification sending should be tested with all kinds of argument vales and
> in various
> call orders.
>
> I'm quite sure that we will have some different sorts of test environment.
> For example
> item 3 of my previous scenario list is the only one with multiple clients,
> the test client
> will have to have very fine control over thread sync.
>
> Btw. I will leave for a 2 weeks vacation tomorrow and there will
> (intentionally ;-) )
> be no phone or email. After I returned I can start to think about these
> environmental
> test aspects.
>
> If you are willing you could start to specify the test cases from a pure
> CDO client's
> point of view. In some simple pseudo notation, just to see the
> requirements of the
> needed test framework:
>
> PRECONDITION/EXECUTION
> 1. create resource R1
> 2. create object of class X (described somewhere else),
> populate it with (a=?, ...)
> add it to R1 contents
> 3. commit
>
> EXPECTED RESULT
> - describe client side process state (if applicable)
> - describe server side process state (if applicable)
> - describe server side database state (if applicable)
>
> Something like that would already be a great deal ;-)
> If you have questions, I'm still here today...
>
> Cheers
> /Eike
Re: CDO Regression Testing [message #561988 is a reply to message #4289] Thu, 15 December 2005 10:15 Go to previous message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6657
Registered: July 2009
Senior Member
TVal schrieb:
> Eike,
>
> Can we draft a test strategy for mapping out the different aspects of the
> test effort?

There's nothing against it, in general.
I've had a look at the document you referred to below and I
got a little bit the impression that TPTP is bigger than CDO ;-)

What about the following:
- I start to gather some (test) requirements from a very technical point of view,
such as test environments (network, db, ...), test code generation (merlin),
test automation and the like.
- I leave it to you to take these snippets and combine them with appropriate
elements from the TPTP doc.



> Such a document could help us coordinate a distributed test effort while
> ensuring that we satisfy test coverage requirements for a well-defined
> scope. The strategy doc would also provide the context and standards for
> developing test cases and supporting infrastructure/tools.
>
> The eClipse TPTP project has a nice test strategy document that we could
> potentially tailor to suit our needs for CDO testing.
> http://eclipse.org/tptp/home/documents/process/TPTP_Testing_ Strategy.html
>
> Your thoughts?
>
> Thanks, and have a great vacation! :)
> - Ted

Thanks ;-)

/Eike


Re: CDO Regression Testing [message #562034 is a reply to message #7369] Thu, 15 December 2005 17:18 Go to previous message
Eclipse UserFriend
Originally posted by: tvalence1.cox.net

Eike,

Sounds like a great approach.

I look forward to your technical test requirements.

Thanks.
- Ted

"Eike Stepper" <stepper@sympedia.de> wrote in message
news:dnrfnf$6ss$1@news.eclipse.org...
>
> TVal schrieb:
>> Eike,
>>
>> Can we draft a test strategy for mapping out the different aspects of the
>> test effort?
>
> There's nothing against it, in general.
> I've had a look at the document you referred to below and I
> got a little bit the impression that TPTP is bigger than CDO ;-)
>
> What about the following:
> - I start to gather some (test) requirements from a very technical point
> of view,
> such as test environments (network, db, ...), test code generation
> (merlin),
> test automation and the like.
> - I leave it to you to take these snippets and combine them with
> appropriate
> elements from the TPTP doc.
>
>
>
>> Such a document could help us coordinate a distributed test effort while
>> ensuring that we satisfy test coverage requirements for a well-defined
>> scope. The strategy doc would also provide the context and standards for
>> developing test cases and supporting infrastructure/tools.
>>
>> The eClipse TPTP project has a nice test strategy document that we could
>> potentially tailor to suit our needs for CDO testing.
>> http://eclipse.org/tptp/home/documents/process/TPTP_Testing_ Strategy.html
>>
>> Your thoughts?
>>
>> Thanks, and have a great vacation! :)
>> - Ted
>
> Thanks ;-)
>
> /Eike
Previous Topic:CDO: Oracle JDBC driver
Next Topic:CDO: Oracle JDBC driver
Goto Forum:
  


Current Time: Tue Dec 06 14:23:49 GMT 2022

Powered by FUDForum. Page generated in 0.03225 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top