A method for testing an updated version of an existing software application is provided. The method may comprise analyzing a user interface screen of the updated version of the existing software application to identify previously existing controls and updated controls and then associating a plurality of testing actions with the previously existing controls and thee updated controls, thereby generating a plurality of test steps. The method may further comprise generating an updated test component comprised of the plurality of test steps, identifying one or more previously existing test components that should be replaced by the updated test component in a test asset repository, and automatically updating each of the one or more previously existing test components with the updated test component at the same time.

According to a computer-implemented method, a determination is made of content of an inbound request that is received at a composite software application from a client. The composite software application utilizes features from an application component that is deployed independently from the composite software application. A determination is made of content of an outbound request that is transmitted from the composite software application to the application component, with the outbound request being triggered by the inbound request. A determination is also made of content of a response to the inbound request that is transmitted from the composite software application to the client. The content of each of the inbound request, the response to the inbound request, and the outbound request are recorded in a repository as a baseline test case for regression testing of the composite software application.

A test environment as described herein allows for testing webpages prior to deployment to a website. More particularly, a virtual test environment allows a developer to virtually test webpages instantiated from representations of webpages stored in a repository. In an example of testing, upon a change to a webpage of a website, one or more virtual test environments may be instantiated to test the webpage and associated webpages. In an example of test environment functionality, the test environment may generate templates representing webpages from a base template representing a set of features common to the webpages. Furthermore, a centralized computer may be used to coordinate templates representing webpages by, for example, managing naming. The centralized computer may further track virtual test environments. In a further example of test environment functionality, templates representing webpages may be generated from webpage source code of the webpages.

A test environment as described herein allows for testing webpages prior to deployment to a website. More particularly, a virtual test environment allows a developer to virtually test webpages instantiated from representations of webpages stored in a repository. The webpage representations may be dynamically updated in the repository with changes to the webpages made in the virtual test environment to maintain updated webpage representations in the repository to allow webpages to be tested against updated webpages.

Embodiments presented herein provide techniques for evaluating for dynamically testing an application or “app” on multiple computing devices at the same time. Each device participating in a testing session runs a device agent which monitors and records user input directed to the app on that device. When a user input event occurs is directed to the app on one of the devices, the corresponding device agent translates the user input into replication events that can be broadcast to, and then replayed by, the app on the other computing devices participating in the testing session.

A system and method for managing the migration of software components among test servers that form a distributed software test environment to ensure that the software components in each of the test servers represent a production environment except for software components being tested. The system further ensures that component changes rolled out into production are not overridden when multiple update requests are made for the same component.

Embodiments of the invention are directed to a system, method, or computer program product for providing an entity wide software tracking and maintenance tool for monitoring maintenance and software updates across an entity. As such, the invention provides a uniform and stable method of monitoring software updates and software installation across an entity's information technology infrastructure. The invention receives software updates or new programs for installation across the entity. The invention then creates a tracking module to link to the maintenance update. The tracking module is a self-contained, self-describing module that contains static information related to the maintenance. Subsequently, the tracking module allows users to monitor the progress of maintenance levels. In some embodiments, the user may query the system to determine the progress of a specific maintenance. In some embodiments, the system may automatically notify a user of the success or failure of maintenance at one or more stages.

In an approach to determining an importance value of an artifact in a collaborative software development environment, a computer determines a snapshot of a collaborative software development environment, wherein the snapshot includes an artifact and at least one relationship between the artifact and one or more nodes in one or more hierarchical levels. The computer then determines, based, at least in part, on the snapshot, a plurality of parameters for the artifact in the collaborative software development environment. The computer calculates, based, at least in part, on the plurality of parameters, an importance value of the artifact.

A method for generating an automated test configured to test a system under test. The system under test has a plurality of operational states, at least one operational state having one or more executable actions associated therewith operable to execute predetermined operations and/or transition the system under test between operational states. The method includes the steps of: defining a model of the system under test comprising a plurality of model states; defining one or more selectable model actions; associating one or more test description sections with one or more model actions; selecting a sequence of model actions; and utilising the test description sections associated with the selected sequence of model actions to define a sequence of operation commands for execution on the system under test as an automated test.

A system for equivalence class analysis-based automated requirements-based test case generation includes a control processor, a data store containing textual design requirements, a textual converter unit structured to convert the textual design requirements to a machine-readable version of design requirements, a requirement partition unit configured to partition the machine-readable design requirements into one or more sets of related design requirements, an equivalence class partition unit configured to process the machine-readable design requirements and input/output variables into a set of equivalence classes, an equivalence class analyzer unit structured to analyze the set of equivalence classes to generate equivalence class tests and identify uncovered input space, and a boundary class analyzer unit structured to identify boundaries of the equivalence classes and generate boundary value tests and robustness tests. A method for equivalence class analysis-based automated requirements-based test case generation implementable on the system, and a non-transitory computer readable medium are also disclosed.