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: 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: 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: 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 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: The presently disclosed subject matter includes a method, a system and a delay compensation unit configured for compensating a delay in communication between a sensing unit and a control unit. A succession of two or more captured images are received from the sensing unit; information indicative of command dynamics parameters are obtained from the control unit; based on the information and a respective transfer function which models the dynamics of the sensor module, the expected reaction of the sensing module to the command is determined; and information indicative of the reaction before the command is executed in the sensing unit can be provided.

Abstract: A system kit and a method for creating a thermal imaging camera by connecting an infrared radiation capturing device to an external platform are provided herein. The kit may include a front end module which may include an image capturing device comprising a micro bolometer detector; and a universal serial bus (USB) interface connected to the image capturing device. The kit may further include a backend module, comprising data sets which are specific to said micro bolometer detector and computer readable code which is executable by a computer processor located at a physical location other than the front end module, wherein said front end module is configured to obtain raw data from the micro bolometer detector and deliver it over the USB interface to said backend module, wherein said backend module code turns the raw data into thermal imagery and temperature readings.

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 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: 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 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: Disclosed are peptide ligands for G-protein coupled receptors that are useful for treating disorders associated with G-protein coupled receptor activation.

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.