Version 5.4.381
We have added a new functionality that allows user-created components, i.e. Scanned, Scripted, and Composite, to be duplicated within a project. To read more about duplication of user components, click here.
Additionally, the user interface for opening and deleting components has been improved by incorporating these actions into a right-click context menu.
To explore the updated UI for component operations, see the links below:
The features implemented are displayed in this video demonstration:
We’ve implemented a new feature enabling the cloning of user-created components: Scanned, Scripted, and Composite across various projects.
To learn how to clone these components, see the links below:
Please note that this feature is exclusively accessible to account administrators via the useMango™ app website.
Here is a video demonstration that walks you through the process of cloning components from one project to another.
We’ve implemented a new feature that empowers users to organize their tests within folders. This feature allows grouping related tests which simplifies navigation.
For more detailed information on using Folders in useMango™, please refer to Working with Folders.
Issue: Last modified date wasn’t updating after editing the description of User Components in the Components Tab.
Fix: Last modified date now updates when the description is edited.
Issue: Usage count of composite component does not update after exploding a composite component.
Fix: Usage count is now updated correctly upon exploding a composite component.
Issue: Incompatibility with Google Chrome versions > 95 when running web tests.
Fix: Fixed behaviour of interacting with Google Chrome for newer versions.
Issue: Default dataset is not run when other datasets are present for V1 engine in Jenkins.
Fix: Default dataset now runs along with other datasets present for V1 engine in Jenkins.
Issue: Parameter is not sustained after exploding a composite component if no value is provided to the parameter from test
Fix: Parameter is now sustained as a test variable after exploding a composite component if no value is provided to the parameter from test