Having written a number WebLogic Startup classes in the past I can say that Lasse's second suggestion is probably the best way to go. Extract the functionality of the Startup class into a separate class. This new class could then be tested easily outside of WebLogic. You also get the additional benefit that it would be easy to port the Startup class to a number of other
J2EE Servers, which isn't usually necessary but never hurts.