A homomorphic encryption-based testing computing system provides a risk-based, automated, one-directional push of production data through a homomorphic encryption tool and distributes the encrypted data to use in testing of applications. Data elements and test requirements are considered when automatically selecting a homomorphic encryption algorithm. A decisioning component selects an algorithm to use to homomorphically encrypt the data set and a push mechanism performs one or both of the homomorphic encryption and distribution of the encrypted data set to at least one intended host. Once delivered, the testing software and/or testing procedures proceed using the encrypted data set, where results of the testing may be stored in a data store. A validation mechanism may validate the test data against production data and communicates whether testing was successful.

A system can identify a file comprising computer-executable instructions, wherein the file has been modified since the file was last transformed into a computer-executable program on which a group of tests was performed. The system can, for respective tests, determine respective line coverage ratios, respective function coverage ratios, and respective branch coverage ratios. The system can select an updated group of tests from the group of tests based on the respective line ratios, the respective function ratios, and the respective branch ratios, the updated group of tests comprising a subgroup of the group of tests. The system can create an updated computer-executable program from the file. The system can test the updated computer-executable program with the updated group of tests.

Various embodiments of the present invention provide methods, apparatuses, systems, computing devices, computing entities, and/or the like for executing efficient and reliable techniques for testing application programming interfaces (APIs) by utilizing at least one of API endpoint modeling data entities and workflow design user interfaces that are generated based at least in part on API endpoint modeling data entities.

Described are methods and systems for predicting and generating impacted scenarios based on a defined set of attributes. The system includes one or more databases. The processors are configured to receive a set of service provider system attributes for a project, generate attribute combinations from the set of service provider system attributes using a machine learning model trained on a reference data model, wherein the reference data model includes multiple test scenarios from the one or more databases, each test scenario associated with a test scenario attribute combination, generate predicted scenarios from the attribute combinations using the machine learning model, determine impacted service provider systems based on the predicted scenarios, determine issues based on each of the predicted scenarios, and generate a complexity score based on the determined impacted service provider systems and the determined issues to determine project viability.

An automatic testing method and apparatus are provided. In the method, a Software Development Kit (SDK) interface is configured and User Interface (UI) rendering data which includes a plurality of UI controls is obtained through the SDK interface. The UI rendering data is a standardized data structure processed through the SDK interface. An operation event of a user on the UI rendering data is received, and a simulation operation of the user on the UI rendering data on a terminal device is determined according to the operation event. Position information of a UI control corresponding to the simulation operation is determined, and a UI automated test script is determined according to the position information and the simulation operation. The UI automated test script is run and debugged using an automated test framework.

The computer-implemented method for producing a test code for automated testing a software comprises providing a high-level test model for modelling a set of requirements for the software to be tested; generating a plurality of high-level test cases on the basis of the high-level test model; providing a human tester with the software to be tested; executing the software; prompting the human tester to execute the high-level test cases by the software under test with using input values arbitrarily selected from an available set of input values of the software in accordance with the high-level test model; producing a plurality of low-level test models for the high-level test cases by the human tester; and generating a computer-executable test program code for the low-level test models.

A test manager is connected to a hosted version control system containing text files stored in a repository. The test manager receives notification by the version control hosted service of one or more files containing formatted plain text. The formatted plain text includes template language constructs that are pre-processed by the test manager, along with optional defined data, to render manual tests instructions for guiding a human tester to perform operations and observe behavior for a system under test. The user interface is also configured to receive status information from the human tester to be associated with the rendered manual test instructions.

Systems and methods for maintaining the safety of a software-based system. One method includes automatically generating a first artifact tree for a hazard for a first version of the system and automatically transforming the first artifact tree into a first augmented tree using a set of heuristics. The method also includes automatically generating a second artifact tree for the hazard for a second version of the system and automatically transforming the second artifact tree for the hazard into a second augmented tree using the set of heuristics. The method further includes automatically comparing the first augmented tree and the second augmented tree to generate a delta view, and automatically generating, based on the delta view, at least one selected from a group consisting of a safety warning for the second version of the software-based system and an actionable recommendation to maintain safety of the second version of the software-based system.

A method of testing a web-based application comprising: at a computing device: receiving a test procedure, the web-based application having an associated web-based application code, the test procedure including at least one testing step comprised of at least an action attribute and an element attribute; for each of the at least one testing steps: identifying an action handler based on the action attribute; generating at least one instruction, by the action handler, and in accordance with a determination that the testing step is an interaction testing step and that there is a value attribute associated with the interaction testing step, modifying the at least one instruction based on the value attribute associated with the interaction testing step; and causing the web-driver to execute the at least one instruction on an identified section of web-based application code corresponding to the element attribute to perform an operation on the web-based application.

A testing scenario (forming part of a computing environment executing a plurality of applications) is initiated to characterize performance of the applications. During the execution of the testing scenario, various performance metrics associated with the applications are monitored. Thereafter, data characterizing the performance metrics is provided (e.g., displayed, loaded into memory, stored on disk, transmitted to a remote computing system, etc.). The testing scenario is generated by monitoring service calls being executed by each of a plurality of automates across the applications, generating a service request tree based on the monitored service calls for all of the applications, and removing cyclic dependencies in the service request tree such that reusable testing components are only used once. Related apparatus, systems, techniques and articles are also described.