Shipping Price Controller and Modifying Fulfillment Controller
Select the ShippingPriceController domain – its dynamic class exclusivity is 50%
View the dynamic classes, the ShippingService is the non-exclusive class.
Click DETAILS to see what other services use this class (ShippingService) – it is also used by ModifyFulfillmentOrder.
In the pop-up, click on ModifyFulfillmentService.getShippingAmout() and move up the call tree to see the call tree as shown here:
Modify Fulfillment Calltree Make ShippingService$$EnhancerBySpringCGLIB.fetchShippingCharges() an entry point of ShippingPriceController - click on the node in the call tree, click MAKE ENTRY POINT, METHOD and select ShippingPriceController domain.
Go back to the domains view and wait for the analysis to complete. The ShippingPriceController is 100% class exclusive (static and dynamic)
Select the ModifyFulfillmentController; it has 100% dynamic class exclusivity and 33% static exclusivity. Review the non-exclusive classes – there are 3 DTO classes and one repository class – this seems fine, and we don’t need to change it.
Review the left pane of the Analysis Page. The analysis output shows 100% class exclusivity for 100% extracted percentage. This means we have reached a state in which we have eight services that are fully exclusive with respect to the testing flows performed in the Learning phase
Complete Analysis