See more on new functionalities and enhancements

Action List page updates

In the algoQA Action List page, the ‘Verify Not Displayed’ action is added to the Python TestComplete framework. This action supports the following UI elements:

 Textboxes, Radio buttons, checkboxes, links, dropdown lists, Images, Text areas, File uploads and labels.

Parameterized custom actions

Previously, you could specify conditions only to Text box UI elements to verify the object locator in the Open Control List Panel window. To access this window, navigate to node configuration> edit icon.

You can now set up business rules to specify conditions for windows, text boxes, dropdown lists and text areas to verify the object locator in the Open Control List Panel window. 

Custom actions are often used to define specific behaviors or tasks that must be performed when interacting with user interface elements (for example, buttons, text boxes and dropdown lists). These custom actions can be configured to take inputs or parameters, and earlier, you were restricted to provide specific data types while setting up the inputs or parameters.

 You will notice that custom actions are highlighted in a distinct color for easy identification.

 This enhancement is applicable when you train a scenario using Follow Me feature and with this enhancement, you can now provide various data types as inputs or parameters when configuring custom actions for the UI elements in the Edit Control window.

To access the Edit Control window, navigate to Follow Me > Create profile sequences > select the feature and appropriate UI element > edit icon.

 Similarly, this enhancement is applicable for editing a recorded scenario using Edit Scenario feature and with this enhancement, you can now provide various data types as inputs or parameters when configuring custom actions for the UI elements in Edit Control Form window.

To access Edit Control Form window, navigate to Edit scenarios > in the Edit Scenario Form > Scenario Sequence section > select the appropriate feature and UI element > edit icon to expand edit control details.

Reuse of the existing scenario

The Edit Scenario Form has been enhanced to allow you to easily reuse an existing scenario and modify it according to your current requirements. Previously, there was an issue saving the modified scenario.

To access Edit Scenario Form, navigate to Main canvas > More Action menu > Edit scenarios > Edit Scenario Form.

 With the latest enhancement, you will find a new Save As button when you edit the scenario name. This button enables you to save the modified scenario with your desired changes while preserving the original scenario intact.

Enhanced scenario management

In the Edit Scenario form page, Scenario Name checkbox is introduced in the title bar. This checkbox enables you to select all scenarios within the current view. 

Note that the current view is restricted to a maximum of 100 scenarios.

To view the next set of 100 scenarios, click the pagination arrow located in the bottom-right corner.

 In the Edit Scenario form page,  button is introduced in the title bar. This export csv button enables you to download the selected scenarios in the csv format. By exporting the scenarios into a structured csv format, you can access information, such as serial numbers, requirement IDs, feature names, tags, scenario names, and outlines.

The csv document acts as a visual representation of the connections between requirements and scenarios. This makes it easier to verify that all requirements are tested and there are no gaps. Once the information is in spreadsheet format, you can perform various types of analysis, such as filtering and sorting.

To access the Edit Scenario form, go to 'More Actions' on the Main Canvas and choose 'Edit Scenarios'.

View Logs functionality

 The introduction of View Logs functionality helps in tracking the user actions.

This functionality displays user actions with corresponding date, time and name of the user who has performed this action.

To access View Logs, go to https://algoshack.net > Profiler > Project Explorer > Feature file > Configuration file > More Actions.

Auto Backup check box

In the Project Settings page, Auto BackUp check box is introduced to take backups of all the feature files regularly without any manual intervention. This ensures that all your feature files will be secured through automated backups, and your data remains safe.

Back Up and Restore functionalities

The introduction of the Back Up functionality allows you to create copies of your files, including configured nodes, feature files associated with UI elements, test cases, and recorded scenarios for a defined duration.

Back Up functionality ensures that in case of accidental deletion, you have a recent copy of your backed up files that can be restored.
To access the Backup feature, go to https://algoshack.net > Profiler > Project Explorer > Feature file > Configuration file > More Actions.

Restore functionality is introduced to restore the backed-up test cases, configured nodes, feature files associated with UI elements and recorded scenarios in case of accidental deletion.

The Restore functionality provides the ability to retrieve the previously backed-up test cases, configured nodes, feature files associated UI elements and recorded scenarios.

To access the Restore feature, go to https://algoshack.net > Profiler > Project Explorer > Feature file > Configuration file > More Actions.

algoAF Enhancements

In the script generation process, the Settings window for a specific configuration node has been enhanced to improve the user experience. In this window, you can now easily view all the relevant languages, frameworks, and report types, with the non-relevant options appearing dimmed.

To access the Settings window, go to algoQA>algoAF > node configuration> Settings.

 In the script generation process, while creating custom actions in the Custom Setting Editor, you have the flexibility to use code snippets from the right pane of the screen. You can easily create your own custom actions by copying and pasting the specific code snippets you need.