[JBoss-dev] RE: wsrp integration

2006-03-25 Thread Thomas Diesler
 [...]/jbpm/bpel and [...]/portal/wsrp seem fine to me

Yes, that's fine.

 neither Portal nor jBPM is an integral component of the Appserver.

Whether these components are shipped with the AS binary distribution is
one aspect, whether they have automated integration tests is another.
The latter is a MUST.

Our testsuite has the ability to create specialized jboss
configurations, start/stop these configurations and run tests in those
configurations.

Every component that is expected to work in the AS should have automated
integration tests. An integration test is a test that checks whether
stuff that you depend on works in the way you expect. How you setup
fuctional tests for your component is up to you.

 Cheers
-thomas

 -Original Message-
 From: Alejandro Guizar
 Sent: 24 March 2006 19:56
 To: Thomas Diesler; Chris Laprun
 Cc: Julien Viet; Dev - JBossWS
 Subject: RE: wsrp integration
 
 Thomas,
 
 I saw a WSRP folder under testsuite/src/main/org/jboss/test/webservice
and
 testsuite/src/resources/webservice and thought the place for BPEL
 integration tests should also be there.
 
 Does your comment imply that both the WSRP and BPEL tests should be
placed
 elsewhere? If so, what is your suggestion? [...]/jbpm/bpel and
 [...]/portal/wsrp seem fine to me, except that neither Portal nor jBPM
is
 an integral component of the Appserver.
 
 -Alejandro
 
  -Original Message-
  From: Thomas Diesler
  Sent: Friday, March 24, 2006 3:54 AM
  To: Chris Laprun
  Cc: Julien Viet; Anil Saldhana; Dev - JBossWS
  Subject: RE: wsrp integration
 
 
  The WSRP integration testsuite would probably also have integration
 tests
  other than for jbossws.
 
  -thomas
 
 
  -Original Message-
  From: Thomas Diesler
  Sent: Friday, March 24, 2006 10:52
  To: Chris Laprun
  Cc: Julien Viet; Anil Saldhana; Dev - JBossWS
  Subject: RE: wsrp integration
  
  
  But these tests would still be located in the webservice testsuite
  though, right?
  
  No, WSRP is just another jbossws client and should have its
  own integration testsuite.
  
  xxx
  Thomas Diesler
  Web Service Lead
  JBoss Inc.
  xxx
  
  
  -Original Message-
  From: Chris Laprun
  Sent: Friday, March 24, 2006 10:48
  To: Thomas Diesler
  Cc: Julien Viet; Anil Saldhana; Dev - JBossWS
  Subject: Re: wsrp integration
  
  
  On Mar 24, 2006, at 4:17 AM, Thomas Diesler wrote:
  
   IMHO, you need to identify the integration requirements and
  create for
   these aspects in the main test suite. WSRP functional
  aspects do not
   need to be tested in the main testsuite.
  
  I agree.
  
   A practical approach would be to create tests when issues
actually
   occur. i.e. you run your wsrp testsuite with jbossws, for
  every issue
   you see you create a test in the wsrp integration testsuite.
  
  Makes sense in the shorter term. However, complete coverage would
be
  ideal in the long run both for WS and WSRP.
  
   There should be a tests-wsrp target in the testsuite that runs
the
   collection of integration tests. wsrp integration tests do
  not belong
   in the webservice testsuite. i.e. should not run as part of
   tests-webservice
  
  But these tests would still be located in the webservice testsuite
  though, right?
  
  Best,
  Chris
  
  ==
  JBoss Portal Developer / WSRP Architect
  
  
  
  


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Re: wsrp integration

2006-03-25 Thread Julien Viet

we all agree on that.

Thomas Diesler wrote:

[...]/jbpm/bpel and [...]/portal/wsrp seem fine to me


Yes, that's fine.


neither Portal nor jBPM is an integral component of the Appserver.


Whether these components are shipped with the AS binary distribution is
one aspect, whether they have automated integration tests is another.
The latter is a MUST.

Our testsuite has the ability to create specialized jboss
configurations, start/stop these configurations and run tests in those
configurations.

Every component that is expected to work in the AS should have automated
integration tests. An integration test is a test that checks whether
stuff that you depend on works in the way you expect. How you setup
fuctional tests for your component is up to you.

 Cheers
-thomas


-Original Message-
From: Alejandro Guizar
Sent: 24 March 2006 19:56
To: Thomas Diesler; Chris Laprun
Cc: Julien Viet; Dev - JBossWS
Subject: RE: wsrp integration

Thomas,

I saw a WSRP folder under testsuite/src/main/org/jboss/test/webservice

and

testsuite/src/resources/webservice and thought the place for BPEL
integration tests should also be there.

Does your comment imply that both the WSRP and BPEL tests should be

placed

elsewhere? If so, what is your suggestion? [...]/jbpm/bpel and
[...]/portal/wsrp seem fine to me, except that neither Portal nor jBPM

is

an integral component of the Appserver.

-Alejandro


-Original Message-
From: Thomas Diesler
Sent: Friday, March 24, 2006 3:54 AM
To: Chris Laprun
Cc: Julien Viet; Anil Saldhana; Dev - JBossWS
Subject: RE: wsrp integration


The WSRP integration testsuite would probably also have integration

tests

other than for jbossws.

-thomas



-Original Message-
From: Thomas Diesler
Sent: Friday, March 24, 2006 10:52
To: Chris Laprun
Cc: Julien Viet; Anil Saldhana; Dev - JBossWS
Subject: RE: wsrp integration



But these tests would still be located in the webservice testsuite
though, right?

No, WSRP is just another jbossws client and should have its
own integration testsuite.

xxx
Thomas Diesler
Web Service Lead
JBoss Inc.
xxx



-Original Message-
From: Chris Laprun
Sent: Friday, March 24, 2006 10:48
To: Thomas Diesler
Cc: Julien Viet; Anil Saldhana; Dev - JBossWS
Subject: Re: wsrp integration


On Mar 24, 2006, at 4:17 AM, Thomas Diesler wrote:


IMHO, you need to identify the integration requirements and

create for

these aspects in the main test suite. WSRP functional

aspects do not

need to be tested in the main testsuite.

I agree.


A practical approach would be to create tests when issues

actually

occur. i.e. you run your wsrp testsuite with jbossws, for

every issue

you see you create a test in the wsrp integration testsuite.

Makes sense in the shorter term. However, complete coverage would

be

ideal in the long run both for WS and WSRP.


There should be a tests-wsrp target in the testsuite that runs

the

collection of integration tests. wsrp integration tests do

not belong

in the webservice testsuite. i.e. should not run as part of
tests-webservice

But these tests would still be located in the webservice testsuite
though, right?

Best,
Chris

==
JBoss Portal Developer / WSRP Architect









--
Julien Viet
JBoss Portal Project Lead


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] RE: wsrp integration

2006-03-25 Thread Tom Baeyens
| Whether these components are shipped with the AS binary 
| distribution is one aspect, 

was already agreed: jbpm will not be in the jboss download.

| whether they have automated 
| integration tests is another. The latter is a MUST.

was already agreed.

| Our testsuite has the ability to create specialized jboss 
| configurations, start/stop these configurations and run tests 
| in those configurations.

Currently we are working on creating such a configuration in
testsuite/build-thirdparty.xml.  I still have to take a closer look into
the jboss test suite(s?). 
 
| Every component that is expected to work in the AS should 
| have automated integration tests. An integration test is a 
| test that checks whether stuff that you depend on works in 
| the way you expect. How you setup fuctional tests for your 
| component is up to you.

agreed as well.

regards, tom.
[EMAIL PROTECTED]
+32 14 880 900
 

| -Original Message-
| From: Thomas Diesler 
| Sent: zaterdag 25 maart 2006 9:44
| To: Alejandro Guizar; Chris Laprun; Tom Baeyens
| Cc: Julien Viet; Dev - JBossWS; 
| jboss-development@lists.sourceforge.net
| Subject: RE: wsrp integration
| 
|  [...]/jbpm/bpel and [...]/portal/wsrp seem fine to me
| 
| Yes, that's fine.
| 
|  neither Portal nor jBPM is an integral component of the Appserver.
| 
| Whether these components are shipped with the AS binary 
| distribution is one aspect, whether they have automated 
| integration tests is another. The latter is a MUST.
| 
| Our testsuite has the ability to create specialized jboss 
| configurations, start/stop these configurations and run tests 
| in those configurations.
| 
| Every component that is expected to work in the AS should 
| have automated integration tests. An integration test is a 
| test that checks whether stuff that you depend on works in 
| the way you expect. How you setup fuctional tests for your 
| component is up to you.
| 
|  Cheers
| -thomas
| 
|  -Original Message-
|  From: Alejandro Guizar
|  Sent: 24 March 2006 19:56
|  To: Thomas Diesler; Chris Laprun
|  Cc: Julien Viet; Dev - JBossWS
|  Subject: RE: wsrp integration
|  
|  Thomas,
|  
|  I saw a WSRP folder under 
| testsuite/src/main/org/jboss/test/webservice 
|  and testsuite/src/resources/webservice and thought the 
| place for BPEL 
|  integration tests should also be there.
|  
|  Does your comment imply that both the WSRP and BPEL tests should be 
|  placed elsewhere? If so, what is your suggestion? 
| [...]/jbpm/bpel and 
|  [...]/portal/wsrp seem fine to me, except that neither 
| Portal nor jBPM 
|  is an integral component of the Appserver.
|  
|  -Alejandro
|  
|   -Original Message-
|   From: Thomas Diesler
|   Sent: Friday, March 24, 2006 3:54 AM
|   To: Chris Laprun
|   Cc: Julien Viet; Anil Saldhana; Dev - JBossWS
|   Subject: RE: wsrp integration
|  
|  
|   The WSRP integration testsuite would probably also have 
| integration
|  tests
|   other than for jbossws.
|  
|   -thomas
|  
|  
|   -Original Message-
|   From: Thomas Diesler
|   Sent: Friday, March 24, 2006 10:52
|   To: Chris Laprun
|   Cc: Julien Viet; Anil Saldhana; Dev - JBossWS
|   Subject: RE: wsrp integration
|   
|   
|   But these tests would still be located in the 
| webservice testsuite 
|   though, right?
|   
|   No, WSRP is just another jbossws client and should have its own 
|   integration testsuite.
|   
|   xxx
|   Thomas Diesler
|   Web Service Lead
|   JBoss Inc.
|   xxx
|   
|   
|   -Original Message-
|   From: Chris Laprun
|   Sent: Friday, March 24, 2006 10:48
|   To: Thomas Diesler
|   Cc: Julien Viet; Anil Saldhana; Dev - JBossWS
|   Subject: Re: wsrp integration
|   
|   
|   On Mar 24, 2006, at 4:17 AM, Thomas Diesler wrote:
|   
|IMHO, you need to identify the integration requirements and
|   create for
|these aspects in the main test suite. WSRP functional
|   aspects do not
|need to be tested in the main testsuite.
|   
|   I agree.
|   
|A practical approach would be to create tests when issues 
|actually occur. i.e. you run your wsrp testsuite with 
| jbossws, 
|for
|   every issue
|you see you create a test in the wsrp integration testsuite.
|   
|   Makes sense in the shorter term. However, complete 
| coverage would 
|   be ideal in the long run both for WS and WSRP.
|   
|There should be a tests-wsrp target in the testsuite 
| that runs 
|the collection of integration tests. wsrp integration tests do
|   not belong
|in the webservice testsuite. i.e. should not run as part of 
|tests-webservice
|   
|   But these tests would still be located in the 
| webservice testsuite 
|   though, right?
|   
|   Best,
|   Chris
|   
|   ==
|   JBoss Portal Developer / WSRP Architect
|   
|   
|   
|   
| 


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends