Automated context-sensitive operating system switch

• US 7,853,926 B2
• Filed: 11/21/2005
• Issued: 12/14/2010
• Est. Priority Date: 11/21/2005
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Sremaniak, Shawn, Roberts, Paul A., Blouin, Eric E., Kritt, Barry A., Law, Douglas A., Nanda, Kuldip
• Primary Examiner(s): Dam; Tuan Q
• Assistant Examiner(s): Wei; Zheng
• Application Number:
  US11/283,642
• Publication Number:
  US 20070168728A1
• Time in Patent Office: 1,849 Days
• Field of Search: None
• US Class Current: 717/124
• CPC Class Codes: G06F 11/263 Generation of test inputs, e.g. test vectors, patterns or sequences ; with adaptation of the tested hardware for testability with external testers

Abstract

An automated technique for switching operating systems, responsive to current context of an executing test scenario. A test designer specifies, in a process control file, a required operating system for appropriate command blocks. A test sequencer packages the required operating system name with each command to be executed, and sends that information to a test listener on a system under test. The test listener remembers the currently-running operating system, and compares that to the required operating system for each command to be executed. If a mismatch occurs, then the correct operating system is not running, and the listener automatically triggers a reboot.

Claims

1. A test system for a server to cause automated switching of operating systems at a remotely-located system under test (“

SUT”

), comprising;

a computer comprising a processor;

a process control file stored on a storage medium accessible to the server and specifying a plurality of commands to be executed on the SUT, wherein;

the process control file is defined as a hierarchy of test blocks;

the plurality of commands are organized into at least two groups, each of the groups occupying a distinct test block at a leaf level of the hierarchy;

at least one leaf-level test block specifies a leaf-specific operating system which is required for executing the commands in the group occupying the leaf-level test block; and

at least one leaf-level test block omits specifying an operating system which is required for executing the commands in the group occupying the leaf-level test block, while an ancestor test block specifies an ancestor-specific operating system that is different from the leaf-specific operating system; and

a test sequencer that executes at the server, using the processor, to iteratively evaluate the process control file and, responsive to each evaluation;

selects a next-executable one of the commands;

determines, from the hierarchy of test blocks, which operating system is required for executing the selected command by determining, if the selected command is organized into one of the groups that occupies a leaf-level test block which specifies a leaf-specific operating system, that the leaf-specific operating system is required for executing the selected command and otherwise, searching each successive ancestor test block of the selected command until locating an ancestor test block which specifies an ancestor-specific operating system and then determining that the operating system required for executing the selected command is the ancestor-specific operating system;

creates a command message that comprises an identification of the required operating system and a specification of the selected command;

writes the identification of the required operating system in a configuration file readable by a reboot process; and

forwards the created command message to the SUT, such that the SUT will compare the identification of the required operating system to a currently-running operating system at the SUT before executing the selected command and, if a mismatch is detected, will trigger the reboot process to reboot the SUT to the required operating system as written in the configuration file.

2. The test system according to claim 1, wherein the process control file is written in a markup language.

3. The test system according to claim 2, wherein:

the test blocks are identified using tags of the markup language; and

each leaf-specific operating system and each ancestor-specific operating system is specified as an attribute value for an attribute of the tag identifying the leaf-level test block and ancestor test block, respectively.

4. The test system according to claim 1, further comprising a test listener that receives the commands forwarded to the SUT, determines the required operating system for each received command by inspecting the operating system identification specified therein, compares the determined operating system to the currently-running operating system, and triggers the reboot process if the mismatch occurs.

5. The test system according to claim 4, further comprising a repository for communications between the test sequencer and the SUT and wherein the forwarded command messages are written to the repository by the test sequencer and retrieved therefrom by the test listener.

6. The test system according to claim 5, wherein the repository comprises a first-in, first-out queue into which the test sequencer writes the forwarded command messages and from which the SUT retrieves the queued command messages.

7. The test system according to claim 1, further comprising a repository for communications between the test sequencer and the SUT and wherein the forwarded command messages are written to the repository by the test sequencer for retrieval therefrom by the SUT.

8. The test system according to claim 1, wherein the forwarded messages are forwarded using a message broker.

9. The test system according to claim 1, wherein each command message further comprises:

a specification of a storage structure on the SUT; and

a location within the storage structure where the command message is to be stored in a first-in, first-out queue for subsequent retrieval by the SUT in preparation for executing the selected command specified in the command message.

10. The test system according to claim 1, wherein:

the server causes automated switching of operating systems at a plurality of remotely-located SUTs;

each created command message further comprises an identification of a particular one of the SUTs and a storage repository at the particular SUT; and

the test sequencer forwards each created command message to the identified particular one of the SUTs to be stored in the identified storage repository for subsequent retrieval by the particular one of the SUTs in preparation for executing the selected command specified in the command message.

11. The test system according to claim 10, wherein the storage repository comprises a first-in, first-out (“

FIFO”

) queue into which the forwarded command messages for the particular SUT are queued for the subsequent retrieval.

12. A computer-implemented method for a server to cause automated switching of operating systems at a remotely-located system under test (“

SUT”

), comprising;

specifying, in a process control file stored on a storage medium accessible to the server, a plurality of commands to be executed on the SUT, wherein;

the process control file is defined as a hierarchy of test blocks;

the plurality of commands are organized into at least two groups, each of the groups occupying a distinct test block at a leaf level of the hierarchy;

at least one leaf-level test block specifies a leaf-specific operating system which is required for executing the commands in the group occupying the leaf-level test block; and

at least one leaf-level test block omits specifying an operating system which is required for executing the commands in the group occupying the leaf-level test block, while an ancestor test block specifies an ancestor-specific operating system that is different from the leaf-specific operating system; and

iteratively evaluating the process control file by a test sequencer that executes at the server and, responsive to each evaluation;

selecting a next-executable one of the commands;

determining, from the hierarchy of test blocks, which operating system is required for executing the selected command by determining, if the selected command is organized into one of the groups that occupies a leaf-level test block which specifies a leaf-specific operating system, that the leaf-specific operating system is required for executing the selected command and otherwise, searching each successive ancestor test block of the selected command until locating an ancestor test block which specifies an ancestor-specific operating system and then determining that the operating system required for executing the selected command is the ancestor-specific operating system;

creating a command message that comprises an identification of the required operating system and a specification of the selected command;

writing the identification of the required operating system in a configuration file readable by a reboot process; and

forwarding the created command message to the SUT, such that the SUT will compare the identification of the required operating system to a currently-running operating system at the SUT before executing the selected command and, if a mismatch is detected, will trigger the reboot process to reboot the SUT to the required operating system as written in the configuration file.

13. The computer-implemented method according to claim 12, wherein:

the process control file is written in a markup language;

the test blocks are identified using tags of the markup language; and

each leaf-specific operating system and each ancestor-specific operating system is specified as an attribute value for an attribute of the tag identifying the leaf-level test block and ancestor test block, respectively.

14. The computer-implemented method according to claim 12, wherein each command message further comprises:

a specification of a storage structure on the SUT; and

a location within the storage structure where the command message is to be stored in a first-in, first-out queue for subsequent retrieval by the SUT in preparation for executing the selected command specified in the command message.

15. The computer-implemented method according to claim 12, wherein:

the server causes automated switching of operating systems at a plurality of remotely-located SUTs;

each created command message further comprises an identification of a particular one of the SUTs and a storage repository at the particular SUT; and

the test sequencer forwards each created command message to the identified particular one of the SUTs to be stored in the identified storage repository for subsequent retrieval by the particular one of the SUTs in preparation for executing the selected command specified in the command message.

16. The computer-implemented method according to claim 15, wherein the storage repository comprises a first-in, first-out (“

FIFO”

) queue into which the forwarded command messages for the particular SUT arc queued for the subsequent retrieval.

17. A computer program product for a server to cause automated switching of operating systems at a remotely-located system under test (“

SUT”

), the computer program product embodied on at least one computer-readable storage media and comprising computer-readable program code for;

iteratively selecting, by a test sequencer that executes at the server, a next-executable one of a plurality of commands from a process control file stored on a storage medium accessible to the server, the plurality of commands for executing on the SUT, wherein;

the process control file is defined as a hierarchy of test blocks;

the plurality of commands are organized into at least two groups, each of the groups occupying a distinct test block at a leaf level of the hierarchy;

at least one leaf-level test block specifies a leaf-specific operating system which is required for executing the commands in the group occupying the leaf-level test block; and

at least one leaf-level test block omits specifying an operating system which is required for executing the commands in the group occupying the leaf-level test block, while an ancestor test block specifies an ancestor-specific operating system that is different from the leaf-specific operating system; and

for each of the selected commands, performing;

determining, from the hierarchy of test blocks, which operating system is required for executing the selected command by determining, if the selected command is organized into one of the groups that occupies a leaf-level test block which specifies a leaf-specific operating system, that the leaf-specific operating system is required for executing the selected command and otherwise, searching each successive ancestor test block of the selected command until locating an ancestor test block which specifies an ancestor-specific operating system and then determining that the operating system required for executing the selected command is the ancestor-specific operating system;

creating a command message that comprises an identification of the required operating system and a specification of the selected command;

writing the identification of the required operating system in a configuration file readable by a reboot process; and

forwarding the created command message to the SUT, such that the SUT will compare the identification of the required operating system to a currently-running operating system at the SUT before executing the selected command and, if a mismatch is detected, will trigger the reboot process to reboot the SUT to the required operating system as written in the configuration file.

18. The computer program product according to claim 17, wherein:

the process control file is written in a markup language;

the test blocks are identified using tags of the markup language; and

each leaf-specific operating system and each ancestor-specific operating system is specified as an attribute value for an attribute of the tag identifying the leaf-level test block and ancestor test block, respectively.

19. The computer program product according to claim 17, wherein each command message further comprises:

a specification of a storage structure on the SUT; and

a location within the storage structure where the command message is to be stored in a first-in, first-out queue for subsequent retrieval by the SUT in preparation for executing the selected command specified in the command message.

20. The computer program product according to claim 17, wherein:

the server causes automated switching of operating systems at a plurality of remotely-located SUTs;

each created command message further comprises an identification of a particular one of the SUTs and a storage repository at the particular SUT; and

the test sequencer forwards each created command message to the identified particular one of the SUTs to be stored in the identified storage repository for subsequent retrieval by the particular one of the SUTs in preparation for executing the selected command specified in the command message.

21. The computer program product according to claim 17, wherein the storage repository comprises a first-in, first-out (“

FIFO”

) queue into which the forwarded command messages for the particular SUT are queued for the subsequent retrieval.