Application testing

1. A method, comprising:

generating a command to define a generic test for an application in response to user input, the generic test comprises a reusable module defining a plurality of test commands, wherein the plurality of test commands are agnostic with respect to a test engine and the application, wherein the reusable module comprises a test layer that specifies functionality of the application to be tested by a test procedure comprising the plurality of test commands,

wherein the functionality is defined by a function layer that comprises a function database table comprising a column for a run mark to indicate whether a function is running, a related to identifier to indicate to which process the function is associated, a host to identify a list of application options, a process identifier to indicate a level of the process, a function position to indicate a location in the process, a description to explain a purpose of the function, an expected result to indicate a value expected to be received from the function, an actual value to indicate test data received after the function has executed, or a function name to differentiate the function from other functions;

converting, by a processor, the plurality of test commands into the test procedure in a programming language compatible with the test engine and the application; and

performing, by the processor, an automated test of the application using the test procedure.

2. The method of claim 1 , wherein the performing the automated test further comprises emulating the application via a simulator.

3. The method of claim 2 , further comprising exercising the simulator via the test engine.

4. The method of claim 1 , wherein the performing the automated test further comprises utilizing database tables to store the plurality of test commands and an associated parameter resulting from the automated test.

5. A non-transitory computer readable medium comprising computer readable instructions comprising:

a process application layer to define a generic test comprising a reusable module defining a plurality of test commands, wherein the plurality of test commands are agnostic with respect to a test engine; and

a test code generator to convert the plurality of test commands into a test procedure in a programming language compatible with the test engine to perform an automated test of the application;

wherein the reusable module comprises a test layer that specifies functionality of the application to be tested by the test procedure,

wherein the functionality is defined by a function layer that comprises a function database table comprising a column for a run mark to indicate whether a function is running, a related to identifier to indicate to which process the function is associated, a host to identify a list of application options, a process identifier to indicate a level of the process, a function position to indicate a location in the process, a description to explain a purpose of the function, an expected result to indicate a value expected to be received from the function, an actual value to indicate test data received after the function has executed, or a function name to differentiate the function from other functions.

6. The non-transitory computer readable medium of claim 5 , wherein the plurality of test commands are stored in a plurality of rows of a database table, and

wherein the database table includes a column corresponding to the plurality of rows to enter a parameter for the plurality of test commands.

7. The non-transitory computer readable medium of claim 5 , wherein the test code generator resides within the test layer that comprises a test database table, wherein the test database table comprises a column for a component name of a test, an identifier to index the test, a name to represent content of the test, a description to define a purpose of the test, a designer name for who created the test, a date to list when the test was created, a coverage percentage to describe an amount of the application that has been tested, or a status to indicate a state of development for the test.

8. The non-transitory computer readable medium of claim 5 , wherein the process application layer comprises a process database table comprising a column for a run mark to indicate whether a process is running, a related to identifier to indicate a test the process is associated with, a test identifier to indicate under what test the process is written, a process position to indicate what order under the test the process is run, a module to identify the process is associated with, a process identifier to uniquely label the process, a process name to describe content for the process, or a process description to explain a purpose for the process.

9. The non-transitory computer readable medium of claim 5 , wherein the test engine is to execute the test procedure on the application.

10. The non-transitory computer readable medium of claim 9 , further comprising a simulator to emulate the application during the test procedure.

11. The non-transitory computer readable medium of claim 5 wherein the process application layer comprises a report generator to generate an analysis report to indicate results from the test procedure.

12. An application testing system comprising:

a memory for storing computer executable instructions; and

a processing unit for accessing the memory and executing the computer executable instructions, the computer executable instructions comprising:

a test interface parameters to define a plurality of test commands, wherein the plurality of test commands comprise generic scripts and parameters that are agnostic with respect to a programming language compatible with an application and a test engine;

a process application layer to convert the plurality of test commands into a reusable module defining the plurality of test commands, wherein the reusable module comprises a test layer that specifies functionality of the application to be tested by a test procedure comprising the plurality of test commands,

wherein a functionality is defined by a function layer that comprises a function database table comprising a column for a run mark to indicate whether a function is running, a related to identifier to indicate to which process the function is associated, a host to identify a list of application options, a process identifier to indicate a level of the process, a function position to indicate a location in the process, a description to explain a purpose of the function, an expected result to indicate a value expected to be received from the function, an actual value to indicate test data received after the function has executed, or a function name to differentiate the function from other functions;

a test code generator to select a programming language and convert the plurality of test commands within the reusable module to a test procedure in a programming language compatible with the application and the test engine, wherein the test layer comprises the test code generator;

the test engine to execute the test procedure in order to test the application; and

a simulator to emulate the application and respond to the test procedure during the test of the application.

13. The application testing system of claim 12 , wherein at least a portion of the test interface generates the generic scripts and parameters are defined based on a user input.

14. The application testing system of claim 12 , wherein the reusable module comprises a plurality of blocks corresponding to a plurality of functions of the application.

15. The application testing system of claim 14 , wherein the plurality of blocks correspond to the plurality of test commands,

wherein a portion of the plurality of test commands corresponds to at least one of the plurality of functions of the application.

16. The application testing system of claim 14 , wherein each of the plurality of blocks corresponds to a data structure.

17. The application testing system of claim 16 , wherein the data structure comprises a database table.