[jboss-dev-forums] [Design of EJB 3.0] - Re: Scope of the Proxy Component

[ALRubinger]

So this debate is actually, "What *is* the scope of the Proxy Component?" :)

I maintain that Carlo's stated requirement is a "business requirement" of EJB3, and therefore should be tested by EJB3 Integration Tests.  Additionally, I believe this is achieved through two "functional requirements" of disparate components:

* jboss-metadata must return Strings of the JNDI Names in correct form
* EJB3 Proxy must return appropriate proxies from whatever addresses are specified by jboss-metadata.

The fundamental difference is that I disagree with:

"wolfc" wrote : Clearly it is the responsibility of the proxy component to satisfy this requirement, so the test is a post condition for the component. 

>From a more generic perspective, I'm not familiar with this notion of "Component Testing":

A is a Component 
B consumes A
This forms another Component (A,B)
B is responsible for testing A to certify (A,B) is OK.

The above is from Carlo's reference http://www.faqs.org/faqs/software-eng/testing-faq/section-14.html

By the above definition, each component we have would be responsible for running acceptance tests on the libraries it consumes (dependent upon the risk factor at stake).

I'm more aligned with the Agile Community's stance on acceptance testing, which says that it's done at the user story (ie. final integration) level (http://en.wikipedia.org/wiki/Acceptance_testing#Acceptance_Testing_in_Extreme_Programming).

S,
ALR

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150836#4150836

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150836