Difference between revisions of "Integration and Interoperability Facilities Framework: Client Libraries Management Model"
From Gcube Wiki
(→Integration Testing) |
m |
||
| Line 3: | Line 3: | ||
=Testing of client libraries= | =Testing of client libraries= | ||
==Unit Testing using My-Container== | ==Unit Testing using My-Container== | ||
| − | ==When== | + | ===When=== |
When needing to exercise the functional features of a CL against the targeted service, the most convenient way to do it is through in-container testing, using my-container. My-container can be used as a convenience for running the tests through Maven or in Eclipse against a small distribution and for simple interactions, not requiring contacting the outside world. | When needing to exercise the functional features of a CL against the targeted service, the most convenient way to do it is through in-container testing, using my-container. My-container can be used as a convenience for running the tests through Maven or in Eclipse against a small distribution and for simple interactions, not requiring contacting the outside world. | ||
| − | ==How== | + | ===How=== |
==Integration Testing== | ==Integration Testing== | ||
| − | ==When== | + | ===When=== |
| − | ==How== | + | ===How=== |
Revision as of 18:36, 25 June 2012
Contents
Building of Client Libraries
Profiling of client libraries as system components
Testing of client libraries
Unit Testing using My-Container
When
When needing to exercise the functional features of a CL against the targeted service, the most convenient way to do it is through in-container testing, using my-container. My-container can be used as a convenience for running the tests through Maven or in Eclipse against a small distribution and for simple interactions, not requiring contacting the outside world.
