Abstract: Disclosed herein are system, method, and computer program product embodiments for generating a unit test for an API or integration of an application by recording a flow of an input through a plurality of message processors of the application. A developer can then view an outline of the recorded flow in a menu, from which the developer can select an individual processor within the recorded flow. By selecting an individual processor, options particular to that processor can be presented to the developer to allow them to control behaviors of the unit test or to validate results.

Abstract: Methods, systems, and devices supporting joint code validation across code repositories are described. Some systems may store code across multiple code repositories, where the code repositories support repository-specific pull requests and validations. However, code stored in one repository may depend on code stored in a different repository. To accurately validate changes to such code, a system may identify a validation trigger for a first pull request (e.g., indicating one or more code changes to a first code repository), determine a second code repository or second pull request related to the first pull request, and generate a test build across the code repositories. For example, the test build may include code updates in the first code repository according to the first pull request and code from the second code repository (e.g., updated according to the second pull request). The system may perform joint validation tests on the test build.

Abstract: Methods, systems, and devices supporting joint code validation across code repositories are described. Some systems may store code across multiple code repositories, where the code repositories support repository-specific pull requests and validations. However, code stored in one repository may depend on code stored in a different repository. To accurately validate changes to such code, a system may identify a validation trigger for a first pull request (e.g., indicating one or more code changes to a first code repository), determine a second code repository or second pull request related to the first pull request, and generate a test build across the code repositories. For example, the test build may include code updates in the first code repository according to the first pull request and code from the second code repository (e.g., updated according to the second pull request). The system may perform joint validation tests on the test build.

Abstract: Provided herein are system, method, and/or computer program product embodiments, and/or combinations and sub-combinations thereof for generating customizable connectors. An API specification may be used to generate a connector descriptor including metadata properties. The connector descriptor maybe customizable. The API specification and connector descriptor may be used to generate a connector configured to connect with the API described in the API specification. The source code of the connector may also be customizable. Furthermore, the source code of the connector may be upgraded based on updates to the API spec, while preserving any customizations.