Abstract: A functional test execution engine (“FTEE”) may be configured to execute test scripts with respect to a server stack. The FTEE may be communicatively coupled to a test script storage device, which may store the test scripts. The FTEE may select one or more test scripts for execution with respect to the server stack. The one or more test scripts may carry out maintenance or diagnostic functions for the server stack. The FTEE may determine the processing resources of the server stack and, based on those processing resources, select a first set of test scripts from the one or more test scripts to execute. The FTEE may cause the first set of test scripts selected to execute with respect to the server stack in order to generate test script results. The FTEE may store the test script results for subsequent analysis and use during execution of subsequent test scripts.

Abstract: A functional test execution engine (“FTEE”) may be configured to execute test scripts with respect to a server stack. The FTEE may be communicatively coupled to a test script storage device, which may store the test scripts. The FTEE may select one or more test scripts for execution with respect to the server stack. The one or more test scripts may carry out maintenance or diagnostic functions for the server stack. The FTEE may determine the processing resources of the server stack and, based on those processing resources, select a first set of test scripts from the one or more test scripts to execute. The FTEE may cause the first set of test scripts selected to execute with respect to the server stack in order to generate test script results. The FTEE may store the test script results for subsequent analysis and use during execution of subsequent test scripts.

Abstract: A functional test execution engine (“FTEE”) may be configured to execute test scripts with respect to a server stack. The FTEE may be communicatively coupled to a test script storage device, which may store the test scripts. The FTEE may select one or more test scripts for execution with respect to the server stack. The one or more test scripts may carry out maintenance or diagnostic functions for the server stack. The FTEE may determine the processing resources of the server stack and, based on those processing resources, select a first set of test scripts from the one or more test scripts to execute. The FTEE may cause the first set of test scripts selected to execute with respect to the server stack in order to generate test script results. The FTEE may store the test script results for subsequent analysis and use during execution of subsequent test scripts.

Abstract: A functional test execution engine (“FTEE”) may be configured to execute test scripts with respect to a server stack. The FTEE may be communicatively coupled to a test script storage device, which may store the test scripts. The FTEE may select one or more test scripts for execution with respect to the server stack. The one or more test scripts may carry out maintenance or diagnostic functions for the server stack. The FTEE may determine the processing resources of the server stack and, based on those processing resources, select a first set of test scripts from the one or more test scripts to execute. The FTEE may cause the first set of test scripts selected to execute with respect to the server stack in order to generate test script results. The FTEE may store the test script results for subsequent analysis and use during execution of subsequent test scripts.

Abstract: Aspects disclosed herein are directed to, for example, a system and method of code migration using distributed file system directories. A computing device may send, to a code repository, a request to migrate code. The request may include, for example, an identifier for the code. In response to the request, the computing device may receive, from the code repository, the code. The computing device may generate one or more directories for the code. The computing device may migrate the code to the one or more directories. The code and the one or more directories may be synchronized to one or more other computing devices.

Abstract: Methods, systems, and computer-readable media for determining expiration of a retention period for a document or record and deleting records or documents are provided. In some examples, a record code may be assigned to a record. The record code may indicate a retention period for the record and may be used to determine whether the retention period has expired. If so, a determination may be made as to whether the document is eligible for deletion. If so, the record may be automatically deleted in at least some examples. If not, the record may be further processed.

Abstract: A metrics management module may be employed to determine organizational health based on data collected for control metrics of an organization. The metrics management module may determine a set of metric health ratings based on the control metric data collected and selects a subset of metric health ratings from the set of metric health ratings. The metrics management module may determine one or more aggregate health ratings based, at least in part, on the subset of selected metric health ratings. The aggregate health ratings may indicate the organizational health of at least a portion of the organization.

Abstract: A script repository (embodied, for instance, as a SQL server database) of re-usable scripts may be provided that houses scripts previously developed and/or executed as part of a prior testing effort. The script repository may be searched to view and/or download one or more test scripts based on one or more search criteria, and/or may be checked for duplicate scripts. A development team thus may be able to easily find appropriate scripts for re-use based on particular testing requirements. At the end of testing, the information on the portion (e.g., percentage) of scripts that were re-used by the developers may be collected and reported on a periodic basis.