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, 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 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 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.

Abstract: System, method, and non-transitory medium for selecting a test scenario template useful for testing a configuration change involves execution of the following: identifying runs of test scenarios run by users belonging to different organizations implementing configuration changes on software systems; identifying first connections between configuration changes and the runs; clustering the runs into clusters of similar runs; identifying, from the first connections and the clustering, second connections between configuration changes and the clusters; receiving a certain configuration change of a certain user; identifying a certain cluster of similar runs which correspond to the certain configuration change by comparing the certain configuration change with configuration changes that take part in the second connections; generating test scenario templates based on runs belonging to the certain cluster; and selecting, based on number of different organizations associated with the templates, a representative test sce

Abstract: System, method, and non-transitory medium for identifying a certain transaction likely to be impacted by a certain configuration change. An activity analyzer receives activity data of users belonging to different organizations and identifies, based on the activity data, a first set of code elements associated with transactions. A program analyzer receives the certain configuration change, and program data that describes at least one of the following: procedure invocations, user interface statements, and database access statements. The program analyzer identifies a second set of code elements that are influenced by the certain configuration change. An intersection module calculates an intersection between the first set of code elements and the second set of code elements. A transaction identifier identifies the certain transaction likely to be impacted by the certain configuration change based on a common code element belonging to the intersection.

Abstract: Selecting a test scenario template relevant to a configuration change involves executing the following: receiving data indicative of configuration changes made to software systems; clustering the configuration changes into clusters of similar configuration changes; identifying runs of test scenarios run by users belonging to different organizations; clustering the runs to clusters of similar runs; generating connections between the clusters of similar configuration changes and the clusters of similar runs; weighting the connections based on the number of different organizations associated with the connections; receiving a certain configuration change of a certain software system; selecting a certain connection, weighted above a threshold, between a cluster of similar configuration changes, to which the certain configuration change corresponds, and a certain cluster of similar runs; and selecting a test scenario template representing the certain cluster of similar runs.

Abstract: System, method, and non-transitory medium for generating a test scenario template based on a user profile, includes steps of identifying runs of test scenarios run by users belonging to different organizations on software systems of the different organizations; clustering the runs to clusters that include similar runs of test scenarios; receiving a profile of a user; selecting from the clusters a certain cluster that suits the profile; the certain cluster includes a first run of a first test scenario associated with a first organization, and a second run of a second test scenario associated with a second organization, in addition, the first run is not identical to the second run, and the first organization is not the second organization; removing from the first run proprietary data associated with the first organization; and generating a test scenario template based on the first and second runs.

Abstract: System, method, and non-transitory medium for ranking similar runs of test scenarios based on unessential test steps in the runs. Runs of test scenarios run by users on software systems that belong to different organizations are clustered to clusters of similar runs. Analysis of a certain selected cluster identifies occurrences of potentially unessential test steps in the similar runs belonging to the cluster. By counting, for each potentially unessential test step, the number of different users that ran a test scenario that includes the potentially unessential test step, it is possible to label certain test steps as verified unessential test steps. A potentially unessential test step may be labeled a verified unessential test step when its corresponding number of different users is below a predetermined threshold. A ranking module utilizes the number of occurrences of verified unessential test steps in runs in order to rank the runs.

Abstract: System, method, and non-transitory medium for rating popularity of clusters of runs of test scenarios. An interface receives runs of test scenarios, run by users belonging to different organizations, run essentially on same packages of software systems. A clustering module clusters the runs into clusters that include similar runs of test scenarios. An organization counter counts the number of different organizations associated with a cluster; an organization may be considered associated with a certain cluster if the certain cluster includes a run of a test scenario run by a user belonging to the organization. A cluster rating module computes popularity ratings of at least some of the clusters based on the number of different organizations associated with the clusters; the higher the number of different organization associated with a cluster, the higher the popularity rating of the cluster.

Abstract: System, method, and non-transitory medium for ranking runs of test scenarios belonging to a cluster. Runs by users on software systems that belong to different organizations are clustered to clusters of similar runs. The runs involve executing transactions instantiated from transaction types. A first processor receives a selection of a certain transaction type, and calculates a first number of different organizations associated with users that ran test scenarios involving execution of a transaction instantiated from the certain transaction type. A second processor receives a selection of a certain cluster from the clusters and calculates, based on runs belonging to the certain cluster, a second number of different organizations associated with users that ran certain test scenarios involving execution of a transaction instantiated from the certain transaction type. A ranking module ranks runs of test scenarios belonging to the certain cluster according to the first and the second numbers.

Abstract: Selecting a test scenario template for a certain user based on similarity of a profile of template utilization by the certain user to profiles of template utilization by other users involves executing the following: receiving runs of test scenarios, run by a certain user belonging to a certain organization; identifying test scenario templates utilized by the certain user; generating a profile of the certain user based on the test scenario templates; receiving profiles of users belonging to different organizations; comparing between the profile of the certain user and the profiles of the users and identifying at least one profile of a user, from among the profiles of the users, which is similar to the profile of the certain user; and selecting a certain template from among templates indicated as utilized in the at least one profile.

Abstract: Improving 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; generating a graph of screens referred to by the non-executable human-readable test scenario; identifying a side branch that is not mandatory for proper operation of the non-executable human-readable test scenario; and removing description of the non-mandatory side branch from the non-executable human-readable test scenario.

Abstract: Identifying non-executable human-readable test scenarios to be updated due to code changes, including: receiving an old code version and a new code version of a data-oriented large-scale software system; identifying changed code by running impact analysis on the old code version and the new code version; identifying scenarios that use the changed code; wherein a scenario defines an activity that operates at least two transactions in a specific way and therefore scenario-based identification provides more accurate results than a transaction-based identification; comparing the changed scenarios with non-executable human-readable test scenarios; and identifying the non-executable human-readable test scenarios that correspond to the changed scenarios, referred to as error-prone non-executable human-readable test scenarios.

Abstract: Identifying missing test scenarios based on a repository of organization-specific in-use scenarios, including: accessing a set of organization-specific in-use scenarios, each organization-specific in-use scenario executes least two transactions; comparing the 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; and providing at least one of the missing test scenarios to a non-programmer user for generating a test scenario repairable by a non-programmer user that covers the at least one missing test scenario.