Systems and methods for using virtualization of operating-system-level components to facilitate software testing

• US 9,116,725 B1
• Filed: 03/15/2011
• Issued: 08/25/2015
• Est. Priority Date: 03/15/2011
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: Symantec Corporation (NortonLifeLock Inc.)
• Inventors: Baird, Bradley
• Primary Examiner(s): Brophy, Matthew
• Application Number:
  US13/048,305
• Time in Patent Office: 1,624 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3696 Methods or tools to render software testable
• CPC Class Codes: G06F 2009/45579 I/O management, e.g. providing access to device drivers or storage
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors

Abstract

A computer-implemented method for facilitating software testing using operating-system component virtualization may include 1) identifying a software product installed on a computing system comprising a base operating system; 2) selecting an operating-system-level component with which the software product is to be tested; 3) isolating the operating-system-level component in a virtualization layer that is distinct from the base operating system; 4) activating the virtualization layer such that access requests directed to the base operating system for the operating-system-level component are redirected to the virtualization layer; 5) testing the software product while the virtualization layer is active to determine how the software product would function if the operating-system-level component was part of the base operating system; and 6) after the testing is complete, deactivating the virtualization layer such that the operating-system-level component is no longer visible to the base operating system or the software product.

Claims

1. A computer-implemented method for using virtualization of operating-system-level components to facilitate software testing, wherein each operating system-level component comprises at least one of a registry key, a hardware driver, a network driver, or an application programming interface (API), at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising:

managing software testing with a virtualized operating system component, wherein the software testing uses a testing module operating on the computing device to automatically, autonomously, and without user intervention, perform direct testing of a software product installed on a computing system comprising a base operating system, the testing comprising;

identifying, by the computing device at the request of the testing module, the software product installed on the computing system comprising the base operating system, wherein;

the base operating system comprises a plurality of operating-system-level components;

the base operating system runs directly on the hardware of the computing system;

selecting, by the computing device at the request of the testing module, from within the plurality of operating-system-level components, an operating-system-level component for use in testing, wherein selecting the operating-system-level component comprises excluding at least one other component from within the plurality of operating-system-level components from use in testing;

isolating, by the computing device at the request of the testing module, an operating-system-level component that corresponds to the selected operating-system-level component in a virtualization layer that is distinct from the base operating system;

activating, by the computing device at the request of the testing module, the virtualization layer such that access requests directed to the base operating system for the selected operating-system-level component are redirected to the virtualization layer;

testing, by the computing device at the request of the testing module, the software product while the virtualization layer is active to determine how the software product would function if the isolated operating-system-level component were part of the base operating system;

after the testing is complete, deactivating, by the computing device at the request of the testing module, the virtualization layer such that the isolated operating-system-level component is no longer visible to the base operating system or the software product;

comparing, by the computing device at the request of the testing module, functionality of the software product when the virtualization layer is inactive to functionality of the software product when the virtualization layer is active to determine whether the software product functions properly when the virtualization layer is active.

2. The method of claim 1, wherein:

the computing system comprises a software development environment;

testing the software product comprises debugging the software product.

3. The method of claim 1, wherein:

determining whether the software product functions properly when the virtualization layer is active comprises determining whether the software product would function properly if the isolated operating system-level component were part of the base operating system.

4. The method of claim 1, wherein:

the isolated operating-system-level component comprises the registry key;

activating the virtualization layer causes the registry key to be functionally merged with a registry of the base operating system.

5. The method of claim 4, wherein:

the registry key enables the software product to interact with an additional software product;

testing the software product further comprises monitoring interactions between the software product and the additional software product to determine whether the software product and the additional software product interact in an expected manner.

6. The method of claim 1, wherein:

the isolated operating-system-level component comprises the hardware driver;

activating the virtualization layer causes a hardware device corresponding to the hardware driver to be accessible to the software product;

determining whether the software product functions properly when the virtualization layer is active comprises determining whether the software product is able to properly interact with the hardware device;

deactivating the virtualization layer causes the hardware device to be inaccessible to the software product.

7. The method of claim 1, wherein:

the isolated operating-system-level component further comprises a user profile;

the user profile includes registry entries associated with a particular user;

activating the virtualization layer causes the user to be logged onto the computing system;

testing the software product comprises determining how the software product functions in context of the user'"'"'s profile;

deactivating the virtualization layer causes the user to not be logged onto the computing system.

8. The method of claim 1, wherein:

the isolated operating-system-level component further comprises a domain state of a network domain;

activating the virtualization layer causes the computing system to be part of the network domain associated with the domain state;

testing the software product comprises determining whether the software product would function properly within the network domain.

9. The method of claim 1, wherein:

the base operating system comprises an integrated component that corresponds to the isolated operating-system-level component in the virtualization layer;

the integrated component would conflict with the isolated operating-system-level component in the virtualization layer if the isolated operating-system-level component were integrated directly into the base operating system;

the method further comprises testing the software product while the virtualization layer is inactive to determine how the software product functions when the integrated component is part of the base operating system.

10. The method of claim 1, further comprising:

isolating an additional operating-system-level component that corresponds to the selected operating-system-level component in an additional virtualization layer that is distinct from the base operating system and the virtualization layer;

activating the additional virtualization layer such that access requests directed to the base operating system for the selected operating-system-level component are redirected to the additional virtualization layer;

testing the software product while the additional virtualization layer is active to determine how the software product would function if the additional isolated operating-system-level component were part of the base operating system.

18. The method of claim 1, wherein:

testing the software product comprises performing remote testing by sending instructions to a communication interface of the computing system.

19. The method of claim 1, wherein:

the selected operating-system-level component comprises an individual element of the base operating system;

during testing, the isolated operating-system-level component comprises the only virtualized component on the computing system.

20. The method of claim 19, wherein the individual element of the base operating system consists of one of:

the registry key;

the hardware driver;

the networking driver;

the API.

11. A testing system for using virtualization of operating system-level components to facilitate software testing, wherein each operating system-level component comprises at least one of a registry key, a hardware driver, a network driver, or an application programming interface (API), the system comprising:

a testing module programmed to manage software testing with a virtualized operating system component, wherein the testing module operates on a computing device to automatically, autonomously, and without user intervention,

perform direct testing of a software product installed on a computing system comprising a base operating system, the testing comprising;

identifying, by the computing device at the request of the testing module, the software product installed on the computing system comprising the base operating system, wherein;

the base operating system comprises a plurality of operating-system-level components;

the base operating system runs directly on the hardware of the computing system;

selecting, by the computing device at the request of the testing module, from within the plurality of operating-system-level components, an operating-system-level component for use in testing, wherein selecting the operating-system-level component comprises excluding at least one other component from within the plurality of operating-system-level components from use in testing;

isolating, by the computing device at the request of the testing module, isolation module programmed to isolate an operating-system-level component that corresponds to the selected operating-system-level component in a virtualization layer that is distinct from the base operating system;

activating, by the computing device at the request of the testing module, the virtualization layer such that access requests directed to the base operating system for the selected operating-system-level component are redirected to the virtualization layer;

testing, by the computing device at the request of the testing module, a test module programmed to test the software product while the virtualization layer is active to determine how the software product would function if the isolated operating-system-level component were part of the base operating system;

after the testing is complete, deactivating, by the computing device at the request of the testing module, the virtualization layer such that the isolated operating-system-level component is no longer visible to the base operating system or the software product;

comparing, by the computing device at the request of the testing module, functionality of the software product when the virtualization layer is inactive to functionality of the software product when the virtualization layer is active to determine whether the software product functions properly when the virtualization layer is active;

at least one processor configured to execute the testing module.

12. The testing system of claim 11, wherein:

the isolated operating-system-level component comprises the registry key;

the testing module is programmed to activate the virtualization layer by causing the registry key to be functionally merged with a registry of the base operating system.

13. The testing system of claim 11, wherein:

the isolated operating-system-level component comprises the hardware driver;

by activating the virtualization layer, the testing module causes a hardware device corresponding to the hardware driver to be accessible to the software product;

the testing module is programmed to test the software product by determining whether the software product is able to properly interact with the hardware device;

by deactivating the virtualization layer, the testing module causes the hardware device to be inaccessible to the software product.

14. The testing system of claim 11, wherein:

the isolated operating-system-level component further comprises a user profile;

the user profile includes registry entries associated with a particular user;

by activating the virtualization layer, the testing module causes the user to be logged onto the computing system;

the testing module is programmed to test the software product by determining how the software product functions in context of the user'"'"'s profile;

deactivating the virtualization layer causes the user to not be logged onto the computing system.

15. The testing system of claim 11, wherein:

the isolated operating-system-level component further comprises a domain state of a network domain;

by activating the virtualization layer, the testing module causes the computing system to be part of the network domain associated with the domain state;

the testing module is programmed to test the software product by determining whether the software product would function properly within the network domain.

16. The testing system of claim 11, wherein:

the testing module is programmed to isolate an additional operating system-level component that corresponds to the selected operating-system-level component in an additional virtualization layer that is distinct from the base operating system and the virtualization layer;

the testing module is programmed to activate the additional virtualization layer such that access requests directed to the base operating system for the selected operating-system-level component are redirected to the additional virtualization layer;

the testing module is programmed to test the software product while the additional virtualization layer is active to determine how the software product would function if the additional isolated operating-system-level component were part of the base operating system.

17. A non-transitory computer-readable-storage medium comprising computer-readable instructions that, when executed by at least one processor of a computing device, cause the computing device to:

manage software testing with a virtualized operating system component, the virtualized operating system component comprising at least one of a registry key, a hardware driver, a network driver, or an application programming interface (API), wherein the software testing uses a testing module operating on the computing device to automatically, autonomously, and without user intervention, perform direct testing of a software product installed on a computing system comprising a base operating system, the testing comprising;

identifying, by the computing device at the request of the testing module, the software product installed on the computing system comprising the base operating system, wherein;

the base operating system comprises a plurality of operating-system-level components;

the base operating system runs directly on the hardware of the computing system;

selecting, by the computing device at the request of the testing module, from within the plurality of operating-system-level components, an operating-system-level component for use in testing, wherein selecting the operating-system-level component comprises excluding at least one other component from within the plurality of operating-system-level components from use in testing;

isolating, by the computing device at the request of the testing module, an operating-system-level component that corresponds to the selected operating-system-level component in a virtualization layer that is distinct from the base operating system;

activating, by the computing device at the request of the testing module, the virtualization layer such that access requests directed to the base operating system for the selected operating-system-level component are redirected to the virtualization layer;

testing, by the computing device at the request of the testing module, the software product while the virtualization layer is active to determine how the software product would function if the isolated operating-system level component were part of the base operating system;

after the testing is complete, deactivating, by the computing device at the request of the testing module, the virtualization layer such that the isolated operating-system-level component is no longer visible to the base operating system or the software product;

comparing, by the computing device at the request of the testing module, functionality of the software product when the virtualization layer is inactive to functionality of the software product when the virtualization layer is active to determine whether the software product functions properly when the virtualization layer is active.