Abstract: A request to sign a provided payload is received, wherein the payload includes an automation script specified to execute on one or more management service instances. The automation script is validated, including by modifying the payload to add metadata data associated with the validation. An encrypted version of a digital signature private key that was received is sent to a credential system. An unencrypted version is received and used to sign the modified payload. The signed modified payload is provided in response to the request to sign the provided payload. The signed modified payload is configured to, in response to a request to execute the automation script on the one or more of the management service instances, be verified using a public key corresponding to the digital signature private key and allow a validation of the automation script at least in part by using the included added metadata.

Abstract: A request to sign a provided payload is received, wherein the payload includes an automation script specified to execute on one or more management service instances. The automation script is validated, including by modifying the payload to add metadata data associated with the validation. An encrypted version of a digital signature private key that was received is sent to a credential system. An unencrypted version is received and used to sign the modified payload. The signed modified payload is provided in response to the request to sign the provided payload. The signed modified payload is configured to, in response to a request to execute the automation script on the one or more of the management service instances, be verified using a public key corresponding to the digital signature private key and allow a validation of the automation script at least in part by using the included added metadata.

Abstract: A system includes software and a computing device configured to test the software in parallel. The computing device may obtain a first test case from a plurality of test cases. The first test case may be configured to cause the software to access a subset of data entries in a database. A plurality of locks facilitates exclusive access to the plurality of data entries. The computing device may further attempt to acquire a subset of the locks that correspond to the subset of the data entries. The computing device may further determine when to execute the first test case. Doing so involves either: (i) failing to acquire all of the subset of the locks and delaying execution of the first test case, or (ii) successfully acquiring all of the subset of the locks and executing the first test case in parallel with the second test case.

Abstract: A system includes software and a computing device configured to test the software in parallel. The computing device may obtain a first test case from a plurality of test cases. The first test case may be configured to cause the software to access a subset of data entries in a database. A plurality of locks facilitates exclusive access to the plurality of data entries. The computing device may further attempt to acquire a subset of the locks that correspond to the subset of the data entries. The computing device may further determine when to execute the first test case. Doing so involves either: (i) failing to acquire all of the subset of the locks and delaying execution of the first test case, or (ii) successfully acquiring all of the subset of the locks and executing the first test case in parallel with the second test case.

Abstract: Systems and methods involving automated test of web pages are described. A computing device may load a web page in a test environment, the web page may having a first underlying representation for rendering. The underlying representation may be analyzed by a page crawler to identify one or more testable components of the web page. A file may be generated, and the identified components may be stored in the file in a second representation that may be more streamlined than the first. The testable components in the file may be displayed as a menu of selectable test options in a graphical user interface (GUI) on a display device. Selection of at least one of the selectable test options may be made via input received at the GUI, the selections corresponding to a set of test steps. The set of test steps may be run in the test environment.

Abstract: Systems and methods involving automated test of web pages are described. A computing device may load a web page in a test environment, the web page may having a first underlying representation for rendering. The underlying representation may be analyzed by a page crawler to identify one or more testable components of the web page. A file may be generated, and the identified components may be stored in the file in a second representation that may be more streamlined than the first. The testable components in the file may be displayed as a menu of selectable test options in a graphical user interface (GUI) on a display device. Selection of at least one of the selectable test options may be made via input received at the GUI, the selections corresponding to a set of test steps. The set of test steps may be run in the test environment.

Abstract: Software updates that cause changes to a database accessible by software can be identified. A first database can be modified using first instructions associated with a first software update to generate a first modified database, and a second database can be modified using second instructions associated with a second software update to generate a second modified database. A difference between the first and second modified databases can be determined, and one or more instructions of the first or second instructions that caused the difference can be identified based on the difference. The first and second instructions can be converted into operations that, when performed against the first and second databases, result in first and second many-to-many tables being generated. The many-to-many tables can be queried to identify the operations associated with the difference between the first and second modified databases.

Abstract: Various embodiments are disclosed herein that provide users of a cloud computing system with the ability to display and/or traverse the various components, e.g., configuration items (CIs), stored in a configuration management database (CMDB), as well as the relationships between such components. The embodiments disclosed herein can visually display, e.g., in the form of tree, the types of relationships between various components stored in the CMDB, such as: business rules, script include files, database tables, user interface pages, and/or update sets. By seeing how the components of a CMDB are interrelated, users may more quickly understand how changes or customizations to one component of the system are likely to affect other components in the system. Likewise, understanding the interrelationships between the various types of components stored within the CMDB may also help users to more quickly troubleshoot issues and/or identify the root causes of problems occurring in their system.

Abstract: Testing behavior of a first instance of web application software can include receiving a request from a first window of a web browser instance executed on a client device indicating a test of one or more components of the first instance. Instructions can be sent to the first window to cause the web browser instance to open a second window of the web browser instance and request a webpage from the first instance from the second window. The webpage can be sent to the client device responsive to another request for the webpage received from the second window. Instructions can be sent to the second window to perform the test using the second window and the webpage. Test results can be received from the second window responsive to a performance of the test against the one or more components.

Abstract: Software updates that cause changes to a database accessible by software can be identified. A first database can be modified using first instructions associated with a first software update to generate a first modified database, and a second database can be modified using second instructions associated with a second software update to generate a second modified database. A difference between the first and second modified databases can be determined, and one or more instructions of the first or second instructions that caused the difference can be identified based on the difference. The first and second instructions can be converted into operations that, when performed against the first and second databases, result in first and second many-to-many tables being generated. The many-to-many tables can be queried to identify the operations associated with the difference between the first and second modified databases.