Abstract: The disclosure concerns systems for use in anastomosis of tubular biological organs within the body, particularly small tubular organs, such as blood vessels, bile duct, lymph duct, nerve ducts, epididymis, etc. The anastomosis system comprises a coupling device with a body, typically within a housing, a coupling assembly linked to the body, a plurality of suturing units within the coupling assembly, and an actuator arrangement formed within the coupling device.

Abstract: System, method, and non-transitory computer-readable medium for generating a test scenario template from runs of test scenarios run on software systems belonging to different organizations, including: clustering the runs to clusters comprising similar runs of test scenarios; selecting from the clusters a certain cluster comprising a first run of a first test scenario and a second run of a second test scenario belonging to different organizations. At least 95% of values used in the first run of the first test scenario are provided automatically by a test script. And generating a test scenario template representing the certain cluster, wherein the test scenario template identifies a transaction used in the first and second runs, and possible values for running the transaction.

Abstract: Methods and computer systems for improving the user friendliness of a non-executable human-readable test scenario by removing unessential test steps, including: receiving a non-executable human-readable test scenario including unessential test steps; identifying the unessential test steps; and generating a user friendlier non-executable human-readable test scenario by removing the identified unessential test steps.

Abstract: System, method, and non-transitory computer-readable medium for generating a test scenario template from runs of test scenarios run on software systems belonging to different organizations, including: clustering the runs to clusters comprising similar runs of test scenarios; selecting from the clusters a certain cluster comprising a first run of a first test scenario and a second run of a second test scenario belonging to different organizations. At least 95% of values used in the first run of the first test scenario are provided automatically by a test script. And generating a test scenario template representing the certain cluster, wherein the test scenario template identifies a transaction used in the first and second runs, and possible values for running the transaction.

Abstract: Identifying missing test scenarios based on authorization policies, including: analyzing the authorization policies applied to non-super-users of a specific data-oriented large-scale software system in order to identify organization-specific in-use scenarios, whereby the non-super-users are usually unauthorized to irrelevant operations; comparing the identified organization-specific in-use scenarios with available test scenarios repairable by a non-programmer user, each available test scenario repairable by a non-programmer user tests at least two transactions; identifying organization-specific in-use scenarios that do not have corresponding test scenarios repairable by a non-programmer user, referred to as first set of missing test scenarios; and providing at least one of the missing test scenarios to a non-programmer user, having proper authorizations, for generating a test scenario repairable by a non-programmer user that covers the at least one missing test scenario.

Abstract: Automatic authorization-based routing of failed test scenarios, including: receiving descriptions of test scenarios that failed while executed by an automatic testing component on a data-oriented large-scale software system, wherein at least half of the test scenarios are expressed by user interaction activities and not code-related language; identifying the test scenarios that failed with abnormal termination as test scenarios to be forwarded to a first programmer authorized to change the data-oriented large-scale software system, wherein abnormal termination does not include normal termination with a value different from an expected value; and identifying the test scenarios that failed without abnormal termination as test scenarios to be forwarded to a second programmer unauthorized to change the data-oriented large-scale software system.

Abstract: Automatic processing of failed test scenarios, including: receiving descriptions of test scenarios that failed while executed by an automatic testing component, wherein at least half of the test scenarios are expressed by user interaction activities and not code-related language; identifying the test scenarios that failed with abnormal termination as test scenarios to be forwarded to a programmer for code change, wherein abnormal termination does not include normal termination with a value different from an expected value; and identifying the test scenarios that failed without abnormal termination as test scenarios to be forwarded to a non-programmer user for re-recording or manual evaluation.

Abstract: Processing failures of executing test scenarios over a data-oriented large-scale software system, including: identifying failures of the test scenarios due to logical errors in the failed test scenarios; forwarding the identified logical related failed test scenarios to a non-programmer user for re-recording or manual evaluation; identifying failures of the test scenarios due to code errors; and forwarding the identified code related failed test scenarios to a programmer for code change.

Abstract: Selecting a transaction for a certain user based on similarity of a profile of the certain user to profiles of users belonging to different organizations involves executing the following: receiving activity data obtained by monitoring activity of the users on software systems; identifying transactions executed by the users on the software systems; generating profiles of the users, based on the transactions, indicating transactions executed by the users; receiving a profile of the certain user, which indicates transactions executed by the certain user; and selecting, based on similarity of at least some of the profiles of the users to the profile of the certain user, a certain transaction that was executed by a user with a similar profile to the profile of the certain user.

Abstract: Utilizing data collected from users belonging to different organizations to select a test scenario template relevant for testing configuration elements involves the following: identifying runs of test scenarios run by users belonging to different organizations; clustering the runs of test scenarios to clusters that include similar runs; generating connections between the configuration elements and the clusters; weighting the connections based on the number of users that acted according to the connections; receiving certain configuration elements; selecting a certain cluster based on a subset of the certain configuration elements and the connections, where each element in the subset is connected to the certain cluster by a connection, and the sum of weights of connections between elements in the subset and the certain cluster, reaches a threshold; and selecting a test scenario template representing the certain cluster.

Abstract: System, method, and non-transitory medium for generating a test scenario template involving the steps of monitoring users belonging to different organizations to identify runs of test scenarios run on software systems belonging to the different organizations; clustering the runs to clusters of similar runs; selecting a certain cluster from the clusters; and generating, based on runs belonging to the certain cluster, a test scenario template. The template may represent the certain cluster and identify a transaction used in runs belonging to the certain cluster, and possible values for running the transaction.

Abstract: System, method, and non-transitory medium for utilizing routes followed by runs of test scenarios to manipulate a test scenario template. Runs of test scenarios run by users belonging to different organizations on software systems associated with the different organizations are analyzed to identify routes that the runs follows; the identified routes may be stored in a database. A route retriever receives a certain template route belonging to a test scenario template and retrieves from the database divergent routes that diverge from the template route. A subset selector selects from the divergent routes a subset of divergent routes that are similar to each other. A template manipulator manipulates the test scenario template according to the subset if the size of the subset reaches a predetermined threshold.

Abstract: System, method, and non-transitory medium for generating a test scenario template from a cluster of similar partial runs of test scenarios involves executing the following: identifying runs of test scenarios run by users on software systems that belong to different organizations; generating partial runs of the test scenarios by extracting from each run of a test scenario data pertaining to a proper subset of the plurality of test steps described in the run; clustering the partial runs of the test scenarios into clusters of similar partial runs; receiving a profile of a user; selecting, based on the profile, from among the clusters a certain cluster suitable for the user; and generating a test scenario template based on partial runs belonging to the certain cluster.

Abstract: Identifying dependencies between configuration elements and transactions involves executing the following: receiving activity data obtained by monitoring activity of users, belonging to different organizations running software systems in which the transactions and the configuration elements are identifiable and can be connected via code elements; generating, based on the activity data, a first set of links between the transactions and code elements associated with the transactions; receiving the configuration elements; receiving code of a software system which includes at least one of the following: procedure invocations, user interface statements, and database access statements; generating, based on static analysis of the code, a second set of links between the configuration elements and code elements influenced by the configuration elements; and identifying dependencies between the transactions and the configuration elements by utilizing the first set of links and the second set of links.

Abstract: System, method, and non-transitory medium for generating a test scenario template from data collected from users running test scenarios to test vendor-customized packaged application modules. Analysis by a module analyzer of descriptions of vendor-customized packaged application modules is utilized to identify similar customizations to the modules. Additionally, a component analyzer identifies, based on the similar customizations, similar components in the modules. Given a specific run of a test scenario run to test a second instance of a certain module, and a description of similar components that include an indication of at least one component of the second instance that is similar to at least one component of a first instance of the certain module, a template generator may generate a test scenario template for testing the first instance. A data cleaner may be used to remove from the generated test scenario template proprietary data.

Abstract: Systems, methods, and non-transitory medium for generating a test scenario template based on similarity between descriptions associated with different organizations. A monitoring module is used to monitor users and to identify runs of test scenarios run on software systems belonging to the different organizations. A processor receives a description of a certain organization (e.g., setup files) and descriptions of the different organizations and identifies, based on similarity between the certain description and the descriptions, organizations that are similar to the certain organization. The processor also identifies a run of a specific test scenario that is utilized by one or more of the organizations. A template generator is used to generate the test scenario template based on the run of the specific test scenario. Additionally, a data cleaner is used to remove from the test scenario template proprietary data associated with at least one of the different organizations.

Abstract: System, method, and non-transitory medium for generating a customized test scenario template based on runs of test scenarios run by users belonging to different organizations. Generating the test scenario template involves the steps of identifying runs of test scenarios run by the users on software systems that belong to the different organizations; clustering the runs to clusters of similar runs; and selecting from the clusters a certain cluster that includes runs associated with different organizations. The runs are used to generate a test scenario template that represents the certain cluster. Additionally, the template may have proprietary data removed from it, and the template may be customized by adding thereto proprietary data relevant to a certain user for whom the test scenario template is customized.

Abstract: System, method, and non-transitory medium for utilizing divergent routes identified in runs of test scenarios to manipulate a test scenario template. A route may define a sequence of one or more elements involved in running a test scenario, such as test steps, transactions, or screens. A certain run of a test scenario, which is instantiated from a test scenario template and which defines a template route, is received. By accessing a database, other routes that diverge from the template route are identified. The divergent routes are used to manipulate the test scenario template, such as updating the test scenario template according to one or more of the divergent routes and/or generating a new test scenario template based on the test scenario template and one or more of the divergent routes.

Abstract: System, method, and non-transitory medium for utilizing divergent routes identified in runs of test scenarios to manipulate a test scenario template, including: identifying runs of test scenarios run by users belonging to the different organizations; receiving a run of a test scenario instantiated from a first test scenario template defining a first template route that instantiations of the first test scenario template are supposed to follow; identifying that the run follows a divergent route that diverges from the first template route; storing the divergent route in a database; receiving a second template route belonging to a second test scenario template; counting number of divergent routes in the database that are similar to the second template route; and manipulating the second test scenario template according to the similar divergent routes.

Abstract: System, method, and non-transitory medium for generating a test scenario template from runs of test scenarios that include a subset of test steps. Executing the method involves the steps of identifying runs of test scenarios run by users on software systems that belong to different organizations; identifying subsets of test steps that are frequently described in the runs; receiving a profile of a user and selecting, based on the profile, a certain subset, from among the subsets, which is appropriate for the user; selecting, from among the identified runs, a first run and a second run; the first and second runs include test steps that are essentially identical to the test steps in the certain subset; and generating a test scenario template based on the first and second subsets of test steps.