Abstract: The disclosure discloses a dry garbage collection system and method with compressing and packing function, the system includes a central control display, a garbage putting bin, a compression and hot-melting bin, a packing bin, a forwarding bin, an air purification bin, a garbage can and a box; the garbage put in the system is compressed to form a cake shape and then performed a packing, and the garbage bags are hot-melted to shape, and vacuumized during packing process; the weight of the garbage before and after compression is compared to determine whether there is more wet garbage in the input dry garbage, so that an alarm can be sent out when the garbage classification is not standardized. The present disclosure realizes effectively compression and packing of garbage, significantly reduces the volume of garbage, prevents the garbage bin from overfilling, reduces subsequent garbage transfer times and transportation costs.

Abstract: A generated object model engine abstracts actions, used in test cases, in a manner to produce new object model types that are independent of an underlying code implementation. The generated object model engine analyzes action classes to aggregate a set of actions having similarly-related class types. Action classes having similarly-related class types are then used to form a new object model type. The new object model type may be used in a test case to hide the action's code implementation from the test case.

Abstract: A test case can be run with actions from the test case being executed in multiple execution paths. This can be done with the aid of an action broker. For example, the broker may identify available automation implementations for the actions and use a priority list to select between available automation implementations for executing an action from the test case. The broker may also perform conversions of results of actions for use by implementations executing other actions in different execution paths, as well as passing results between implementations in different execution paths.

Abstract: A generated object model engine abstracts actions, used in test cases, in a manner to produce new object model types that are independent of an underlying code implementation. The generated object model engine analyzes action classes to aggregate a set of actions having similarly-related class types. Action classes having similarly-related class types are then used to form a new object model type. The new object model type may be used in a test case to hide the action's code implementation from the test case.

Abstract: A test case can be run with actions from the test case being executed in multiple execution paths. This can be done with the aid of an action broker. For example, the broker may identify available automation implementations for the actions and use a priority list to select between available automation implementations for executing an action from the test case. The broker may also perform conversions of results of actions for use by implementations executing other actions in different execution paths, as well as passing results between implementations in different execution paths.