|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
See:
Description
| Class Summary | |
|---|---|
| API_010_PublisherTest | This test is jUDDI specific, as the publisher methods are an extension to the UDDI api. |
| API_020_TmodelTest | |
| API_030_BusinessEntityTest | |
| API_040_BusinessServiceTest | |
| API_050_BindingTemplateTest | |
| API_060_PublisherAssertionTest | |
| API_070_FindEntityTest | |
| API_080_SubscriptionTest | |
| API_090_SubscriptionListenerIntegrationTest | |
| API_091_RMISubscriptionListenerIntegrationTest | |
| API_100_ClientSubscriptionInfoTest | |
Unit tests to test the api implementation. Theses tests go all the way down into the persistence layer. By default they are using an embedded Java-based database called Derby.
The order in which the tests are run is irrelevant however some tests are more basic then others. For example, you will need to have a Publisher, before you can persist a Business, and you need to have a Business before you can persist a Service. So it makes sense to test persisting a Publisher first.
By default JUnit executes tests in alphabetical order, so to control test execution order we use the JUDDI_###_ prefix.
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||