Java Reference
In-Depth Information
Te s t i n g a p p l i c a t i o n s
This chapter covers
Migrating tests to OSGi for in-container testing
■
Mocking OSGi APIs for bundle testing
■
Performing unit, integration, and management
testing
■
You're now just about halfway through this topic: congratulations! At this point,
you should have confidence in applying
OSG
i to new and existing projects. Migrat-
ing applications to
OSG
i should be especially fresh in your mind from the last chap-
ter. But what can you do to make sure you're on the right track to modularity and
not turning your applications into tangled spaghetti? As is true for any piece of soft-
ware, the best way to track quality is with regular testing. Testing can confirm that
your modularized code meets the same requirements as your original application.
Te s t i n g c a n v e r i f y t h a t y o u r c o d e w i l l c o n t i n u e t o w o r k w h e n d e p l o y e d i n s i d e t h e
target container. It can even help you practice different deployment scenarios in
the safety of your friendly neighborhood test server. Even a simple nonfunctional
test, such as checking the number of shared packages between bundles, can avoid
tangles forming early on in development.
230
