Abstract: A system that includes a failed test detector and a task updater can automatically update tasks associated with consistent failures of software tests in a software development management platform. The failed test detector can use a set of evidence of test (EOT) files that indicate software testing results over a period of time to identify tests that are consistently failing when executed against versions of a software application. The task updater can automatically create tasks associated with such consistently-failing tests in the software development management platform. The task updater can also automatically close existing tasks associated with tests, in the software development management system, if the failed test detector determines that those tests are no longer failing consistently.

Abstract: A computing system for collaborative interactions between virtual and real-world environments using an extended reality collaboration environment is provided.

Abstract: A computer system is described for conducting interactions of a simulated event for users in a virtual environment. The computer system includes a processor programmed to: (i) present the virtual environment including an item of a first user associated with a first user device; (ii) receive sensor data from one or more sensors associated with the first user device, the sensor data including data related to the item; (iii) select a simulated event involving the item; (iv) generate the simulated event involving the item and using the received sensor data for display within the virtual environment; and (v) cause the simulated event involving the item to be displayed within the virtual environment to the first user device and a second user device, wherein the first user and the second user visually experience the simulated event involving the item.

Abstract: A computing system is provided.

Abstract: A timeline generation and solving tool is provided to parameterize a project at an application lifecycle management (“ALM”) tool, and generate and solve a timeline of features according to the parameterized project. The Scrum master may re-parameterize the project, causing a new timeline to be generated, solved, and visualized. In this fashion, the Scrum master may rapidly prototype many project parameterizations, resulting in many possible timelines. Without the use of a timeline generation and solving tool which interfaces with an ALM tool, retrieves project features, and converts project features to a common format suitable for computations based on working speeds, a Scrum master would need to generate and check a timeline by hand, and work indirectly by manually copying data out of the ALM tool, leading to a slow and potentially error-prone project roadmapping process which does not permit rapid prototyping of possible timelines.

Abstract: A timeline generation and solving tool is provided to parameterize a project at an application lifecycle management (“ALM”) tool, and generate and solve a timeline of features according to the parameterized project. The Scrum master may re-parameterize the project, causing a new timeline to be generated, solved, and visualized. In this fashion, the Scrum master may rapidly prototype many project parameterizations, resulting in many possible timelines.

Abstract: A system that includes a failed test detector and a task updater can automatically update tasks associated with consistent failures of software tests in a software development management platform. The failed test detector can use a set of evidence of test (EOT) files that indicate software testing results over a period of time to identify tests that are consistently failing when executed against versions of a software application. The task updater can automatically create tasks associated with such consistently-failing tests in the software development management platform. The task updater can also automatically close existing tasks associated with tests, in the software development management system, if the failed test detector determines that those tests are no longer failing consistently.

Abstract: A system that includes a failed test detector and a task updater can automatically update tasks associated with consistent failures of software tests in a software development management platform. The failed test detector can use a set of evidence of test (EOT) files that indicate software testing results over a period of time to identify tests that are consistently failing when executed against versions of a software application. The task updater can automatically create tasks associated with such consistently-failing tests in the software development management platform. The task updater can also automatically close existing tasks associated with tests, in the software development management system, if the failed test detector determines that those tests are no longer failing consistently.

Abstract: A system that includes a failed test detector and a task updater can automatically update tasks associated with consistent failures of software tests in a software development management platform. The failed test detector can use a set of evidence of test (EOT) files that indicate software testing results over a period of time to identify tests that are consistently failing when executed against versions of a software application. The task updater can automatically create tasks associated with such consistently-failing tests in the software development management platform. The task updater can also automatically close existing tasks associated with tests, in the software development management system, if the failed test detector determines that those tests are no longer failing consistently.

Abstract: A timeline generation and solving tool is provided to parameterize a project at an application lifecycle management (“ALM”) tool, and generate and solve a timeline of features according to the parameterized project. The Scrum master may re-parameterize the project, causing a new timeline to be generated, solved, and visualized. In this fashion, the Scrum master may rapidly prototype many project parameterizations, resulting in many possible timelines. Without the use of a timeline generation and solving tool which interfaces with an ALM tool, retrieves project features, and converts project features to a common format suitable for computations based on working speeds, a Scrum master would need to generate and check a timeline by hand, and work indirectly by manually copying data out of the ALM tool, leading to a slow and potentially error-prone project roadmapping process which does not permit rapid prototyping of possible timelines.