Abstract: Techniques described herein are directed toward side-by-side handling of providers on a 64-bit system. The request for loading a particular version of the provider may include a provider architecture flag that specifies a 32-bit or 64-bit version of a provider for managing the requested service. The request may also include a required architecture flag specifying that the given instantiation of the provider is required and to be forced. The platform manager loads a particular provider instantiation as a function of the provider architecture flag and the required architecture flag.

Abstract: Systems, methods, data structures and software for testing software, in which the testing code and the verification data are independent from each other A variation map may specify one or more testing (e.g., automation) modules, and may specify the verification data to apply to the testing module(s). For example, the variation map may specify: specific value(s) for variables (e.g., parameters) of a testing module; type(s) of data patterns to apply to the variables; a number of testing iterations to perform using the testing module; and how to record the results of each iteration. A testing framework may be provided that is configured to use a variation map to test software. The testing framework may be configured to generate verification data using this recognition, and to control the execution of the one or more testing modules specified in the variation map, including supplying the generated verification data to the testing module(s).