Version 3.2.0 (2023/02/08)

Version 3.2.0 (2023/02/08)

Summary 

Thanks to version 3.2 and its integration with JIRA, it will be easy to associate JIRA requirements at the functionality level and to open or associate a ticket at the failure level; gain and efficiency when everything can be viewed in the same interface.  Also, several improvements, including the addition of new libraries for scripting have been added to improve the experience and allow gains in performance. 

Improvements 

1. Automatic compression of output.xml and report.html files to save space. Note that compression is optional if the run is launched from the public API.  
2. Audit generation for user authentication and logout, project lock and when a user stops a run.  
3. Addition of the verdict to the Excel file of the results of a manual test  
4. Quick access to the test results in Excel format via a button to the right of the 3-dot menu (...). This file is always accessible via the said menu.  
5. Ability to specify a tenant if needed in the Swagger of the public API   
6. Addition of a checkbox "All / None" on the keyword library filter.  
7. Addition of the ALT+A shortcut on the user's page.  
8. Automatic activation of the editing mode of an added keyword while adding a combined keyword.  
9. Automatic activation of the edition mode of the added data set while adding a data set.  
10. Grey colour display of the "Comment" keyword to better distinguish comments from other active keywords.  
11. Self-selection of the level while adding a system component, so that the new component is always displayed in the list.  
12. Improved presentation of the keyword documentation displayed with F1 to better reflect its internal content.  
13. Ability to download a file residing on the Selenium hub of your GoTest instance. This download allows you to open the file and make the desired validations a second time.
    Note that it is imperative that the file has been downloaded in Selenium. Here is an example of scripting to visualize the steps to follow:
    
    
    
    
    

New Features 

Integration with Jira 

The GoTest integration with JIRA is available at 2 levels; requirements and bugs. This integration ensures traceability at these 2 levels. 

Thus, a user can now:  

• Linking JIRA requirements at the functionality and scenario level. 
• Add or link a default to a JIRA ticket for a failed scenario. 
• View the number of JIRA tickets at the test plan, feature and scenario level. 
• View the requirements in the test execution reports. 
   

Better user experience 

1. “Move” Contextual menu in the component library to move a level or a component more easily. 
2. Possibility to resize the displayed sidebars. 
3. The addition of the "copy below" and "insert below" options facilitates script maintenance.  
4. Possibility to use the "Import Variables" keyword to import a variable file in Python format during a test. 
5. Ability to record a Selenium video with the runtime scheduler and the public API. 
6. The addition of a button dedicated to the reorganization of keywords; is an asset when this reorganization is done on different pages. 
7. Display a warning message after authentication when the hard disk is 90% full or more. In addition, the software will prevent running automatic or hybrid tests to avoid completely saturating the hard disk. 
    

New libraries for scripting 

• RPA.PDF: allows you to validate the content and rendering of a PDF file (extracting text from PDFs, adding watermarks to pages and decrypting/encrypting documents). 
• RPA.Excel.Files: this allows you to read and write Excel files without having to launch the Excel application itself. 
• RPA.Tables: this allows you to import data from various sources and apply different operations to them. Common use cases are reading and writing CSV files, inspecting files in directories or performing tasks from existing Excel data. 
• RPA.Salesforce: provides access to Salesforce using a REST API. This allows you to access your Salesforce data without using the Salesforce user interface. With API access, you can perform operations and integrate Salesforce into your applications in any way you want. You can use REST API tools to create, manipulate, and search data in Salesforce by sending HTTP requests to endpoints in Salesforce. Depending on where you send the requests, you access and leverage different pieces of information, called resources. Resources include records, query results, metadata, and more. 
• RPA.Email.Exchange: allows you to send, read and delete emails. Exchange interfaces with Exchange Web Services (EWS) 
• RPA.Slack: allows you to send messages to Slack. 
• RPA.Hubspot: this mainly allows you to retrieve data from HubSpot CRM objects via the API. 
• RPA.Notifier: allows interaction with different notification providers: email, Gmail, pushover, slack, telegram and Twilio.