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.

Abstract: Methods for accessing impact analysis repositories and transaction-refinement index for each of the impact analysis repositories. According to the obtained transaction-refinement index, associating the combined repository with information from the most transaction refined impact analysis repository. Associating the combined repository with information from the less transaction refined impact analysis repository in the case of a request to insert or delete a table record for tables that do not contain any impacted transaction in the more transaction refined impact analysis repository. And associating the combined repository with information from the less transaction refined impact analysis repository in the case of a request to update a table record for table columns that do not contain any impacted transaction in the more transaction refined impact analysis repository.

Abstract: Executing semiautomatically a functioning test scenario to enable a non-programmer user to generate a new test scenario based on the functioning test scenario, including: recording the non-programmer user while interacting with the semiautomatic execution of the functioning test scenario; and generating the new test scenario based on the recording; wherein the semiautomatic execution enables the following features: automatically entering data inferred from the functioning test scenario into a form of a data-oriented large-scale software system; and enabling the non-programmer user to: change the automatically entered data, add a new form to the semiautomatically executed functioning test scenario, and enter data into fields inside the new form.

Abstract: One non-limiting embodiment of the invention comprises the steps of accessing at least two impact analysis repositories, calculating a combined impact analysis repository from the at least two impact analysis repositories, and utilizing the combined impact analysis repository for supplying better quality impact analysis results.

Abstract: One non-limiting embodiment of the invention comprises the steps of accessing at least two impact analysis repositories, calculating a combined impact analysis repository from the at least two impact analysis repositories, and utilizing the combined impact analysis repository for supplying better quality impact analysis results.

Abstract: A system and method for analyzing a computer program comprising a first multiplicity of elements having a second multiplicity of functional relationships defined therebetween, the first multiplicity of elements including interface elements and non-interface elements, the method comprising reading source code, finding at least selected interface elements in the source code, and identifying, and displaying to a user, only those functional relationships which are defined between the selected interface elements.

Abstract: Methods comprising the steps of receiving a code to be analyzed; running a flow analysis of the received code; running a backward and/or forward analysis, whereby the analysis returns at least one input statement; selecting at least one externally-visible statement from the returned list of statements; associating each externally-visible statement with its appropriate user-language description; and supplying a user the at least one user-language description that is associated with the externally-visible statement.