What's New ?

Discover Our Latest algoQA Product Highlights for V4.1.2

During the past few weeks, our devoted team has been diligently working to introduce a collection of remarkable updates aimed at enhancing your experience with algoQA. We are excited to present the key highlights of our latest product release, and we are confident that these enhancements will capture your attention.

New functionalities and enhancements

Action List page update

In the algoQA Action List page, ‘Verify Not Displayed’ action is added to the Python TestComplete framework. 

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. 

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.

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.

View Logs functionality

The introduction of View Logs functionality helps in tracking the user 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.

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.

algoAF Enhancements

In the script generation process, the Settings window for a specific configuration node has been enhanced to improve the user experience. 

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. 

For more information on new functionalities and enhancements, see more.

Bug Fixes

Issue: When using the 'Follow Me' feature to record a scenario, if you skip adding a 'UI element', the recording process does not allow you to proceed or save the recorded scenario.  

A fix has been implemented to address this issue of interrupted recording flow. When using the ‘Follow Me’ feature to record a scenario, if you skip adding a 'UI element', you can still proceed with recording the scenario flow by clicking on the ‘Submit’ button and save the recorded scenario by clicking on the Analyze button.

Issue: If you have configured two nodes, but failed to add features and the corresponding UI elements to one of the configured nodes, the test case generation fails to proceed successfully.
For example, if you have configured two nodes, such as Login Process and Home Page, but features and UI elements are not added to Home Page, test case generation fails to proceed successfully.

Fix: With this fix, the test case generation process will continue without any interruption. Additionally, even in cases where only one node is fully configured with features and UI elements, you can still generate test cases effectively.

Issue: When editing an individual scenario file in the list of epic scenario files, the changes made were accidentally saved in the default scenario file instead of the corresponding individual scenario file.

Note: The epic scenario file serves as the primary file containing a collection of individual scenario files.

Fix: The bug fix ensures that modifications made to an individual scenario file are now correctly saved to the corresponding setup file, preventing unintended changes to the default setup file.