TECHNICAL FIELD

&null;0001&null; This invention relates generally to command line processing and, more particularly, to the use of macros in command line processing.

BACKGROUND OF THE INVENTION

&null;0002&null; A command line interface is a user interface to a program that allows a user to directly input lines of text, hereinafter referred to as &null;command lines,&null; that include commands and any required parameters. The program then responds to the input by acting on the commands. The user may manually input command lines one at a time directly into a keyboard, or store several command lines in a file, such as a batch file, that can then automatically be input to the command line interface. A well-known example of a command line interface is the MICROSOFT Disk Operating System (MS-DOS) prompt.

&null;0003&null; Conventional command line interfaces are very easy to implement and require minimal overhead, but are limited in functionality. One limitation is that command line interfaces do not allow input parameters to be flexibly defined. In other words, if a user wishes to change the parameters input via the command line interface, he or she may be required to reenter then manually, or incorporate them into a new version of an executable file.

&null;0004&null; One area in which command line interfaces are frequently used is software testing. To run a software test, a test engineer typically enters the name of a batch file on the command line. The batch file then causes a series of commands to be entered. For example, the batch file may have the following series of commands:

&null;0005&null; Dir c:&null;test

&null;0006&null; Set param1&null;0

&null;0007&null; Mytest param2 param3 testlog.txt.

&null;0008&null; These commands change the current disk directory to &null;test,&null; set the value of &null;param1,&null; and execute the program &null;mytest.exe&null; with &null;param2 and param3&null; as inputs, and with the results of the test being stored in &null;testlog.txt.&null; If the test engineer wishes to make changes in the test itself, he or she may have code the new test and recompile it as &null;test.exe.&null; Similarly, to change one or more of the input parameters, the test engineer may have to manually edit the batch file. Both of these procedures can be very cumbersome, especially if the test engineer needs to run dozens of variations of the test.

&null;0009&null; Thus, it can be seen that there is a need for a method and system for processing command line input that avoids these limitations.

SUMMARY OF THE INVENTION

&null;0010&null; In accordance with the foregoing, a method and system for processing input from a command line is provided, in which the command line contains a macro that gets parsed by a command line processor. The processor replaces the macro with the appropriate command and executes the command line. The macro may contain a message that the processor displays to prompt the user to identify the command that is to replace the macro. Other possible functions that the macro may perform include, but are not limited to: executing a function to generate a string to replace the macro, executing a function to generate another macro with which the first macro may be replaced, and prompting the user to enter the name of a dynamic-linked library (DLL) from which the replacement string for the macro may be obtained.

&null;0011&null; Additional features and advantages of the invention will be made apparent from the following detailed description of illustrative embodiments that proceeds with reference to the accompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

&null;0012&null; While the appended claims set forth the features of the present invention with particularity, the invention, together with its objects and advantages, may be best understood from the following detailed description taken in conjunction with the accompanying drawings of which:

&null;0013&null; FIG. 1 is an example of a network;

&null;0014&null; FIG. 2 is an example of a computer;

&null;0015&null; FIG. 3 is an example of an architecture that may be used in an embodiment of the invention;

&null;0016&null; FIG. 4 is a flowchart showing steps that may be executed in an embodiment of the invention; and,

&null;0017&null; FIG. 5 is an example of command line files that may be used in a software test scenario according to an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

&null;0018&null; The invention is generally directed to a method and system for processing a command line from a command line interface that allows macros to be included within the text of command line. The macros may be expanded to generate commands and parameters that are included in the command line.

&null;0019&null; Although it is not required, the invention may be implemented by computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures and the like that perform particular tasks or implement particular abstract data types.

&null;0020&null; The invention may be implemented on a variety of types of computers, including personal computers (PCs), hand-held devices, multi-processor systems, microprocessor-based on programmable consumer electronics, network PCs, minicomputers, mainframe computers and the like. The invention may also be employed in distributed computing environments, where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, modules may be located in both local and remote memory storage devices.

&null;0021&null; An example of a networked environment in which this system may be used will now be described with reference to FIG. 1. The example network includes several computers 100 communicating with one another over a network 102, represented by a cloud. Network 102 may include many well-known components, such as routers, gateways, hubs, etc. and may allow the computers 100 to communicate via wired and/or wireless media.

&null;0022&null; Referring to FIG. 2, an example of a basic configuration for a computer on which the system described herein may be implemented is shown. In its most basic configuration, the computer 100 typically includes at least one processing unit 112 and memory 114. Depending on the exact configuration and type of the computer 100, the memory 114 may be volatile (such as RAM), non-volatile (such as ROM or flash memory) or some combination of the two. This most basic configuration is illustrated in FIG. 2 by dashed line 106. Additionally, the computer may also have additional features/functionality. For example, computer 100 may also include additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to stored the desired information and which can be accessed by the computer 100. Any such computer storage media may be part of computer 100.

&null;0023&null; Computer 100 may also contain communications connections that allow the device to communicate with other devices. A communication connection is an example of a communication medium. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. The term computer readable media as used herein includes both storage media and communication media.

&null;0024&null; Computer 100 may also have input devices such as a keyboard, mouse, pen, voice input device, touch input device, etc. Output devices such as a display 1 16, speakers, a printer, etc. may also be included. All these devices are well known in the art and need not be discussed at length here.

&null;0025&null; The invention may include the use of many different types of macros. In one embodiment, a macro may be used to call a run-time line library from within the command line. Functions of the run-time library can then be used to generate new commands and new parameters for the command line. For example, a programmer may wish to write a batch file having a series of command lines that, when executed, cause a computer to enter the proper disk directory and to run a particular program. The conventional format of these command lines in the MS-DOS environment is:

&null;0026&null; dir c:&null;MyDirectory

&null;0027&null; MyProgram.exe

&null;0028&null; However, there may be times that the programmer won't know in advance the directory in which &null;MyProgram.exe&null; is located. It may therefore be necessary for the programmer to run a special function that checks the system registry to determine where &null;MyProgram.exe&null; is located. An embodiment of the invention allows the programmer to insert a macro into the &null;dir&null; command line that, when expanded, executes a run-time library function to retrieve the directory path from the system registry and substitute the correct path for the macro. For example, the batch file may look like this:

&null;0029&null; dir<function name>

&null;0030&null; MyProgram.exe

&null;0031&null; A command line processor operating in accordance with this embodiment of the invention identifies the macro by the brackets and calls the function whose name is inside the brackets. The function then searches the system registry and finds the name of the directory in which &null;MyProgram.exe&null; is located. The function returns the name to the command line processor. The command line processor then substitutes the directory name for the macro. After the macro has been expanded, the batch file now looks like this:

&null;0032&null; dir c:&null;MyDirectory

&null;0033&null; MyProgram.exe.

&null;0034&null; The command lines inside the batch file can now be executed properly.

&null;0035&null; In another embodiment of the invention, a macro is used on a command line to display the dialog box that allows the user to enter information at the time the command line is processed. The information can then be included in the command line prior to the command line being executed. To illustrate this feature, the previous batch file example will be modified slightly. It is assumed in this example that the programmer does not know the directory in which &null;MyProgram.exe&null; is located. However, it is assumed that the programmer does not need to run a special function to obtain the name of the directory, but instead can obtained it verbally from a colleague. The batch file may initially look like this:

&null;0036&null; Dir<dialog box &null;Please type in name of directory&null;>

&null;0037&null; MyProgram.exe

&null;0038&null; When processing the command lines of the batch file, the command line processor displays a dialog box with the message &null;please type in name of directory.&null; The user then types in the name of &null;c:&null;MyDirectory.&null; The command line processor expands the macro by replacing it with &null;c:&null;MyDirectory.&null; The batch file now looks like this:

&null;0039&null; Dir c:&null;MyDirectory

&null;0040&null; MyProgram.exe

&null;0041&null; The batch file can now be executed properly.

&null;0042&null; A command line language that may be used in an embodiment of the invention will now be described. The language is made up of tags and macros. A tag is a unit of execution that can involve a program or function to perform a task. The syntax is as follows:

&null;0043&null; <&null;tag_type &null;command&null; &null;optional parameters&null;/&null;>

&null;0044&null; where tag_type describes type of tag (for example, command, special directive, etc.), command defines the command to be executed in this tag, and optional parameters are a list of optional parameters with special meaning for tag/command.

&null;0045&null; Examples of possible tags include:

&null;0046&null; <&null;CMD timeout&null;100, runas&null;thisUser, run-my-test param1 param2 param3/&null;> After parsing this command line, the command line processor executes &null;run-my test param1 param2&null; under the credentials of user &null;thisUser&null; with a timeout set to 100 milliseconds.

&null;0047&null; <&null;Directive reboot, require_confirm&null;yes/&null;>

&null;0048&null; This command reboots the computer with user confirmation.

&null;0049&null; <&null;SCRIPT&null;parameter&null;

&null;0050&null; . . .

&null;0051&null; /&null;>

&null;0052&null; This tag contains script to be executed by external scripting engine.

&null;0053&null; Macros are tokens that are replaced by strings when parsed. In this embodiment, macros can be embedded, so that, for example, one macro can include another macro. Also, recursive executions allow one macro to generate another macro, giving this language implementation the flexibility of run-time generated code

&null;0054&null; The syntax for macros is as follows:

&null;0055&null; <$macro_type &null;parameters&null;>

&null;0056&null; If the command line processor is implemented as a multi-pass processor, the &null;parameters&null; in this tag may include a code for telling the processor the phase in which the macro is to be expanded.

&null;0057&null; Examples of possible macros include:

&null;0058&null; <$DLL-special.dll EntryPoint&null;FuncParam, param&null;&null;local&null;, timeout&null;30>

&null;0059&null; The &null;DLL&null; macro specifies which DLL (dynamic-linked library) is to be loaded, and which functions within the DLL are to be called. In this case, the DLL &null;special.dll&null; will be loaded. Then, the function FuncParams called using the parameter &null;local.&null; The timeout is set to 30 seconds. The function called (e.g. FuncParam) may return a character string that will be used by the command line processor to replace the macro.

&null;0060&null; <DGX&null;Enter file name:, type&null;F, timeout&null;30, default&null;&null;file.txt&null;>

&null;0061&null; When the command line processor expands the &null;DGX&null; macro, it displays a dialog box with a prompt and a default value. In this case, the dialog box will have the prompt &null;Enter file name&null; with edit box containing default string &null;file.txt.&null; The dialog box will be displayed for 30 seconds if user does not edit it, based on the timeout parameter. The parameter &null;Type&null; value being entered. In this case, the value entered is of type &null;F,&null; which signifies that it is a filename. This tells the command line processor to enable and process &null;Browse&null; button in dialog box. Other possible file types include, but are not limited to: T (text), N (number), and P (password). The command line processor may modify its functionality based on type of value entered.

&null;0062&null; An example of a command line that uses a macro in accordance with an embodiment of the invention is as follows:

&null;0063&null; <&null;CMD run-my-test. Exe <$DGX&null;Enter file name:, type&null;F, default&null;&null;test.txt&null;>/&null;>

&null;0064&null; When the command line processor encounters this command line, it displays dialog box with the edit box pre-filled with &null;test.txt.&null; The &null;Browse&null; button will also be enabled. After the user edits the text, the dialog box is dismissed and value macro is replaced with the value entered by the user. The resulting command line, assuming that the default is used, is as follows:

&null;0065&null; run-my-test.exe test.txt.

&null;0066&null; A software architecture that may be used to implement on embodiment of the invention will now be described, with appropriate reference to FIGS. 3 and 4. The architecture includes a command line processor 150, a set of optional plug-ins 156, run-time libraries 158, optional script 160 and a user interface 152. A command line file 154 contains a series of command lines, included macros, where appropriate. The processor 150 receives the command line file 154 as input and parses its contents. The processor 150 is capable of understanding and interpreting a number of tag and macro types. However, this embodiment of the invention is extensible in that it allows programmers to define their own tags and macro types through the addition of one or more plug-ins 156. When the processor 150 encounters a tag or macro that it does not recognize, it calls the appropriate plug-in to assist in the parsing process. The run time libraries 158 contain functions that can be called by the processor 150 in response to the appropriate macro. If required the processor 150 may invoke one or more scripts 160 by sending then to an appropriate scripting engine in response to the appropriate macro or macros. Finally, the processor 150 receives input from a user (from a dialog box, for example) via the user interface 152. The user interface 152 may also be used to display messages and results to the user.

&null;0067&null; Referring to FIG. 4, an example of a procedure that may be followed by the command line processor 150 will be now described. In this procedure, the processor 150 processes the command line file 154 in at least two passes. The first pass is referred to as the &null;schedule phase&null; and the second pass is referred to as the &null;execution phase.&null; At step 170, the processor reads a line from the file. If the processor does not recognize either command tag or a macro in the command line, the flow moves to step 176, at which the processor loads the plug-ins 156. If, after loading the plug-ins 156, the processor 150 still cannot recognize one or more tags or plug-ins, the processor ends with an error. If the processor 150 recognizes all of the commands and macros, the flow moves to step 180, at which the processor 150 processes the command line expanding macros as necessary, and, if it is the execution phase, executing the commands. If the processor has reached the end of the command line file 154 and there are no more passes, the procedure ends. Otherwise, the procedure returns to step 170.

&null;0068&null; The processor goes through the entire file once for the schedule phase and once for the execution phase. The processor determines whether a macro line is to be expanded during the schedule phase or during the execution phase based on optional parameters that may be included with the macro. This allows macros to be nested. For example, if a programmer wishes to have the user type in, at runtime, the name of a DLL to be used to generate a macro, he could structure a command line as follows:

&null;0069&null; <&null;CMD dir <$DXS &null;Enter name of DLL&null;>

&null;0070&null; When the processor sees this command line, it knows that it is supposed to expand the &null;$DX&null; macro in the scheduling pass, since there is an &null;s&null; immediately after the macro name. Thus, during the scheduling pass, the processor 150 prompts the user to enter the name of the DLL. If the user enters &null;MyDLL.dll,&null; the processor expands the macro so that the command line reads;

&null;0071&null; <&null;CMD dir <$DL MyDLL.dll>/&null;>

&null;0072&null; On the execution pass, the command processor runs MyDLL.dll to obtain the correct directory and expand the $DL macro so that the command line appears as follows just before it is executed:

&null;0073&null; <&null;CMD dir c:&null;MyDirectory/&null;>

&null;0074&null; Referring to FIG. 5, an example of a scenario in which an embodiment of the invention is used will now be described. In this example, it is assumed that client-server software is being tested, and that, prior to the execution of the test, a client computer and a server computer linked together in a network need to obtain their own assigned names and provide those names to one another. Command line files 200c and 200s are being processed at the client and server computer respectively. These files each include CMD tags, which have been previously discussed, as well as the tags VAR and SYNC. The VAR tag tells the command line processor to assign a value to a variable, while the SYNC tag tells the command line processor to synchronize with other processes according to a synchronization variable.

&null;0075&null; At line 204s, the command line processor running on the server first expands the <$DL ServerIs.dll, get_name> macro. This involves calling the &null;get_name&null; function of ServerIs.dll to obtain a character string. Once the processor has received the string as a result of the function call it replaces the macro with the result, which, in this case, is the name of the server. At line 206s, the command line processor on the server waits at a barrier for the client to complete lines 204c and 206c, as indicated by the synchronization object &null;Name Ready.&null; At line 208s the command line processor expands the macro <$VAR Client Name> by substituting the value for Client Name obtained in line 204c on the client. The processor then executes the server side of the test using the client name at line 208s. At line 208c, the command line processor running on the client performs the equivalent procedure and obtains the value for Server Name. At lines 210s and 210c, the server and client both wait for the other to be finished. At the end of this example, the server and client have each performed their respective parts of the test using each other's name.

&null;0076&null; The invention may advantageously be employed in a software testing environment. Companies that produce software may have scores of test engineers organized into various testing groups. When developing software tests, the test engineers may make certain assumptions regarding the software environment, the hardware and other variables. As tests are re-used over time and among different groups, many of these assumptions may not hold true. The embodiments of the invention described herein may be used to allow &null;on-the fly&null; modification of these variables without requiring engineers to write completely new tests. For example, a test procedure may have been developed and compiled into &null;test.exe.&null; However, the original developer of the test might have assumed that the test would be run from the &null;c:&null; drive in a directory containing the files &null;file1.inf&null; and &null;file2.lib.&null;

&null;0077&null; The developer may also have assumed that the results would be stored as a text file called &null;log.txt.&null; However, when the test is passed to a different test group, it may be run from the &null;m:&null; drive in a directory that does not contain &null;file1.inf&null; and &null;file2.lib.&null; Furthermore, the new group may want the results stored as an HTML file. Instead of rewriting the rest, the developer could simply put the test execution command line in a file along with other command lines that contain macros for allowing the new group to specify these variables when the test is run. The file might be structured as follows:

&null;0078&null; 1. Pre-process: macros that allow group to specify directory and import file1 and file2.

&null;0079&null; 2. test.exe.

&null;0080&null; 3. post process: macros that allow group to specify test log format.

&null;0081&null; It can thus be seen that a new a useful method and system for processing input from a command line interface has been provided. In view of the many possible embodiments to which the principles of this invention may be applied, it should be recognized that the embodiments described herein with respect to the drawing figures is meant to be illustrative only and should not be taken as limiting the scope of invention. For example, those of skill in the art will recognize that the elements of the illustrated embodiments shown in software may be implemented in hardware and vice versa or that the illustrated embodiments can be modified in arrangement and detail without departing from the spirit of the invention. Therefore, the invention as described herein contemplates all such embodiments as may come within the scope of the following claims and equivalents thereof.