1.1 - 2024 Release Notes
This release notes documentation contains package updates and the list of new features and fixed issues for all Test Assistant releases in 2024.
For the most recent product highlights, see What’s New in Test Assistant.
For considerations and actions when upgrading to the latest version, see Upgrade Notes.
Test Assistant 2024.10.01.00
Release Date: 16 October 2024
New features
This section provides the list of new features and enhancements that have been added in this release.
| Module/s | Feature description | JIRA |
|---|
| Service | A UI file can now be tested in the Service module. | RTA-2945 |
| Service | Relative xpaths can now be generated in the Service module. | RTA-2945 |
Fixed issues
This section provides the list of issues that have been fixed in this release.
| Module/s | Fix description | JIRA |
|---|
| Service | Fixed an issue where the IsFile checkbox in the Commands is unchecked when an uploaded service file is updated. | RTA-2933 |
Service Step | Node attachment data populated in the Data Set module are now available for use in the Service and Step modules. | RTA-2933 |
Breaking changes
If you are upgrading from an earlier version, refer to the Upgrade Notes for necessary actions you should be aware of when upgrading.
Test Assistant 2024.07.02.00
Release Date: 26 July 2024
New features
This section provides the list of new features and enhancements that have been added in this release.
| Module/s | Feature description | JIRA |
|---|
| Dashboard | A Key filter has been added to the Issues Reported section to filter the list of issues using an ADO ID. | TAIT-290 |
| Step | You can now add an upload file UI steps to your testing projects. | TAIT-282 |
Fixed issues
This section provides the list of issues that have been fixed in this release.
| Module/s | Fix description | JIRA |
|---|
| Dashboard | Fixed an issue where several Name filters are displayed in the Issues Reported section filter criteria. | TAIT-289 |
| Step | Fixed an issue where an additional requestBody node is populated in the Request Body JSON. | TAIT-273 |
| Test Run | Fixed an issue where a batch execution fails with an empty Response Body payload. | TAIT-262 |
Breaking changes
If you are upgrading from an earlier version, refer to the Upgrade Notes for necessary actions you should be aware of when upgrading.
Test Assistant 2024.07.01.00
Release Date: 08 July 2024
Fixed issues
This section provides the list of issues that have been fixed in this release.
| Module/s | Fix description | JIRA |
|---|
| Run Details | Fixed an issue where a duplicate of the screenshot for a failed test scenario is displayed. | |
Steps Templates | Fixed an issue where an additional Request Body node in the Step module is populated when creating a template. | |
| Test Run | Fixed an issue where a failed test report cannot be downloaded. | RTA-2300 |
Test Assistant 2024.06.01.00
Release Date: 04 June 2024
New features
This section provides the list of new features and enhancements that have been added in this release.
| Module/s | Feature description | JIRA |
|---|
| Azure | Attachments can now be added to the test results for single or multiple scenarios. | RTA-2257 |
| Azure | New issue tickets can now be linked to the parent ticket configured for a test execution. | RTA-2223 |
| Azure | All Azure or JIRA tickets associated with your testing project are now visible when creating a template. | RTA-2222 |
| Dashboard | Filter options are now available on the Issues Reported list. | RTA-2224 |
| Test Run | An issue ticket can now be created in Azure or JIRA without a parent ticket. | RTA-2297 |
| Run Details | Link to the created issue tickets for a test run is now displayed on the Run Details screen, and clicking on the link will open a new tab. | RTA-2225 |
Fixed issues
This section provides the list of issues that have been fixed in this release.
| Module/s | Fix description | JIRA |
|---|
| Dashboard | Fixed an issue where an issue ticket was linked to another step after accessing the Run ID from the dashboard. | RTA-2300 |
| Dashboard | Fixed an issue where the linking issue icon was disabled for another step after accessing the Run ID from the dashboard. | RTA-2300 |
Scenario Validation Services | Fixed an issue where the Input Fields value was not updated in the Velocity Script Details after updating the Input Fields value in the Validation Service module. | RTA-2285 |
| Test Run | Fixed an issue where a test would return a passed result even if the query returned no rows. | RTA-2221 |
| Test Run | Fixed an issue where an alert pop-up message is displayed on the Details tab after executing a UI scenario. | RTA-2036 |
| Validation Services | Fixed an issue where an Expected Field added to a validation service was not automatically added to the Velocity Script Details. | RTA-2170 |
Breaking changes
If you are upgrading from an earlier version, refer to the Upgrade Notes for necessary actions you should be aware of when upgrading.
Test Assistant 2024.05.02.00
Release Date: 21 May 2024
New features
This section provides the list of new features and enhancements that have been added in this release.
| Module/s | Feature description | JIRA |
|---|
| Environment | A schema can now be defined in the Environment module to allow the fetching of data from different schemas instead of setting the schema in SQLs. | RTA-2039 |
Service Test Run | Test Assistant now supports if-else and loop conditions to allow generalized UI testing combinations. | RTA-2120 |
Fixed issues
This section provides the list of issues that have been fixed in this release.
| Module/s | Fix description | JIRA |
|---|
| Data Set | The value of the next or subsequent steps in the Data Set module is now displayed in the Request Body. | RTA-2160 |
| Data Set | The + is now displayed on the Path Parameters tab. | RTA-2146 |
| Data Set | The + is now properly working on the Query Parameters tab. | RTA-2146 |
| Data Set | Fixed an issue where the rows in the Header tab are deleted when an empty additional row is deleted. | RTA-2146 |
| Environment | The API Base URL field now accepts URLs with no . (dot). | RTA-2194 |
| Validation Services | Fixed an issue where the Update button is only enabled after clicking Extract Filters. | RTA-2209 |
| Validation Services | Fixed an issue where the captured data from the validation service did not match the data being executed, causing the test execution to fail. | RTA-2197 |
Template Test Run | The Generate Dataset from Query checkbox now resets when navigating back to the Test Run or Template screen from the Data Set module. | RTA-2152 |
| Test Run | Fixed an issue where the test execution passed even if the actual and expected values do not match. | RTA-2196 |
| Test Run | Fixed an issue where the execution gets stuck even if the element is already present on the screen. | RTA-2165 |
| Test Run | The Database field in the Filter Details window now loads the default database. | RTA-2152 |
Breaking changes
If you are upgrading from an earlier version, refer to the Upgrade Notes for necessary actions you should be aware of when upgrading.
Test Assistant 2024.05.01.00
Release Date: 03 May 2024
New features
This section provides the list of new features and enhancements that have been added in this release.
| Module/s | Feature description | JIRA |
|---|
| Service | The command waitForSecond has been replaced with Pause, and the unit has been changed from seconds to milliseconds. | RTA-2138 RTA-2174 |
Fixed issues
This section provides the list of issues that have been fixed in this release.
| Module/s | Fix description | JIRA |
|---|
| Data Set | Scenario names with special symbols can now be selected when creating a new data set. | RTA-2153 |
| Data Set | The Select checkbox can now be checked or unchecked when creating or updating a data set. | RTA-2145 |
Data Set Service | Service parameters with null value becomes empty when the service is loaded on the Data Set page. | RTA-2157 |
Data Set Service Step | Data sets can now be saved or updated for services and steps for API UI testing. | RTA-2149 |
| Environment | Fixed an issue where the Test Connection button is triggered when clicking on the white space near the button. | RTA-2166 |
| Environment | Fixed an issue where database updates are still saved when clicking the Cancel button. | RTA-2121 |
| Run Details | Fixed an issue where test reports are downloaded in an insecure mode. | RTA-2161 |
| Run Details | Fixed an issue where an error message is displayed when a data set is automatically created using mining querying for Date fields. | RTA-2148 |
| Run Details | The sequence number of scenarios is now correctly displayed in the summary report. | RTA-2142 |
Run Details Scenario | Fixed an issue where an incorrect scenario page was displayed when clicking on a scenario on the Run Details page. | RTA-2140 |
| Scenario | The overlapping tooltip texts have been fixed. | RTA-2130 |
| Services | You cannot create an API or Batch service without entering valid information in the Service Type field. | RTA-2175 |
Services Test Run | Fixed an issue where UI recording failed when running a UI test on a page with a size of 1552x855. | RTA-2119 |
| Step | Fixed an issue where a Validation Service could not be updated when the Step Type or Service was changed when creating a new step. | RTA-2171 |
| Templates | The Sequence column on the Filter Details window now displays the correct sequence number. | RTA-2151 |
| Templates | Fixed an issue where the Save or Update button needed to be clicked twice to save or update a template. | RTA-2151 |
| Validation Service | Fixed an issue where an invalid request or response is accepted when creating or updating a validation service. | RTA-2129 |
Breaking changes
If you are upgrading from an earlier version, refer to the Upgrade Notes for necessary actions you should be aware of when upgrading.
Test Assistant 2024.04.02.00
Release Date: 16 April 2024
New features
This section provides the list of new features and enhancements that have been added in this release.
| Module/s | Feature description | JIRA |
|---|
Data Set Scenario | You can now add descriptions to filter labels in the Scenario module. The filter label description will be shown as a tooltip in the Data Set module to identify the necessary format or value required to enter for the filter label. | RTA-2117 |
Data Set Validation Service | Additional operational values are now available to use in validation service queries in the Data Set module. | RTA-2114 |
| Environment | The SFTP authentication now supports PEM files. | RTA-2128 RTA-2133 |
| Services | Components related to SQL microservices now support :parameterName format. | RTA-1907 |
Fixed issues
This section provides the list of issues that have been fixed in this release.
| Module/s | Fix description | JIRA |
|---|
| Data Set | Fixed an issue where an SFTP data set cannot be updated. | RTA-2134 |
Data Set Step | Fixed an issue where the Replace File checkbox is not ticked when creating a Data Set using a step with "isReplace": true. | RTA-2048 |
| Project | Fixed an issue where a project cannot be deleted and a login error message is displayed when an entered Tracking project is deleted during creation of a new project. | RTA-2144 |
| Scenario | Fixed an issue where the filter labels are not displayed correctly when checking query in the Scenaior module. | RTA-2143 |
| Scenario | The Response Body in the velocity mapping screen is now available for the main service when setting input values for a validation service. | RTA-2116 |
Templates Test Run | Check Query button is now displayed when generating a data set from a query during the creation of a test template and a test run. | RTA-2126 |
| Validation Service | Fixed the UI issues in the Check Query window. | RTA-2109 |
| Validation Service | Fixed an issue where updated values for a Validation Service do not reflect during test execution. | RTA-2059 |
Test Assistant 2024.04.01.00
Release Date: 02 April 2024
New features
This section provides the list of new features and enhancements that have been added in this release.
| Module/s | Feature description | JIRA ticket |
|---|
| Data Set | Values of the key-value pairs in a data set can now be updated using the EXCEL view. | RTA-1970 |
| Services | A proper error message is now displayed when deleting a service used in a step. | RTA-2107 |
Service Validation Service | All special characters, except _, need to be removed from the query before clicking Process Query to avoid SQL run issues. | RTA-2103 |
Fixed issues
This section provides the list of issues that have been fixed in this release.
| Module/s | Fix description | JIRA ticket |
|---|
| Dashboard | The Recent Activities section now displays correct log entries. | RTA-2106 |
| Data Set | The downloaded CSV data set file now displays the correct sequence of steps and excludes fields that are not present in the data set. | RTA-2110 |
| Environment | Non-default databases can now be deleted from the Database Details table in the Environment module. | RTA-2105 |
| Environment | A confirmation message is now displayed after successfully updating an environment. | RTA-2091 |
| Environment | The has been removed from all the Password fields in the Environment module. | RTA-2054 |
| Environment | Fixed an issue where test execution does not start and no error message is displayed when the added password in the environment is incorrect. | RTA-1931 |
| External System | The Add New Environment button remains disabled until the external system details are saved when creating a new external system. | RTA-2104 |
| External System | Fixed an isse where no external system details are displayed when navigating back to the External System module using breeadcrumbs. | RTA-2089 |
| External System | The external systems logos are now displayed properly in card and list views. | RTA-2022 |
| External System | Fixed an issue where an error message is displayed when creating or updating an external system with a logo. | RTA-2123 |
| Project | Fixed an issue where an error message is displayed when updating a project. | RTA-2092 |
| Scenario | Fixed an issue where the Scenario Details fields shrunk after closing the Check Query window when creating a new scenario. | RTA-2111 |
| Scenario | The correct Step Type is now displayed on the Scenario card and list views. | RTA-2101 |
| Scenario | Data mining scenarios are now loading correctly, and all the expected operations are now accessible. | RTA-2100 |
| Scenario | Scenario breadcrumb is now clickable and directs you to the Scenario module when clicked. | RTA-2094 |
| Scenario | Fixed an issue where the Velocity Script details are not displayed after configuring filters and updating a scenario. | RTA-2070 |
| Service | SFTP services with no configured steps can now be deleted. | RTA-2099 |
| Service | Fixed an issue where the configured target and targets are not captured during test execution. | RTA-2098 |
| Service | Fixed an issue where the Request Body is not updated when Select All Commands is ticked after selecting a particular command from the Selected Commands tab. | RTA-2080 |
| Sign Up | Login page is now displayed after a successful signup. | RTA-2085 |
| Sign Up | The in the Password and Re-Enter Password fields now work properly. | RTA-2085 |
| Sign Up | The expected error message, when the Password and Re-Enter Password field values do not match, is now displayed. | RTA-2085 |
| Sign Up | The image on the Sign Up page is displayed properly. | RTA-2085 |
| Test Run | The Generate Dataset From Query feature in the Test Run window now works as expected. | RTA-2102 |
| Validation Service | Fixed an issue where the Payload Details > Request Body is automatically populated with data upon selecting an External System when creating a new validation service. | RTA-2115 |
| Validation Service | Fixed an issue where an exception error message is displayed when deleting a validation service. | RTA-2053 |
Breaking changes
If you are upgrading from an earlier version, refer to the Upgrade Notes for necessary actions you should be aware of when upgrading.
Test Assistant 2024.03.02.00
Release Date: 18 March 2024
New features
This section provides the list of new features and enhancements that have been added in this release.
| Module/s | Feature description | JIRA |
|---|
| Database/SFTP connections | You can now test your connections when configuring the database and SFTP details. | RTA-1988 |
| Data Set | The SFTP type of datasets can now be generated using data mining. | RTA-1905 |
| Data Set | Dataset names are now suffixed with the data from the first column retrieved from the SQL query used to generate the dataset. | RTA-2027 |
Environment Validation services | Database used in a validation service can no longer be deleted in the Environment module. | RTA-1892 |
| Issue Tracking | Azure is now configured to retrieve the 50 latest issues to avoid error messages when retrieving many issues. | RTA-2029 |
| Test Run | You can now upload a file during UI test execution. | RTA-2052 |
Fixed issues
This section provides the list of issues that have been fixed in this release.
| Module/s | Fix description | JIRA |
|---|
Dashboard Run Results | All filters on the Dashboard and Run Results pages are now working properly. | RTA-1898 |
| Dataset | Fixed an issue where the Data Sets module throws an exception message when loading, saving, and executing SFTP Upload datasets. | RTA-2041 |
| Data Set | You must now provide a File Name or a JSON Path when adding a File Download. | RTA-2014 |
| Data Set | The Save All button is now only enabled when all mandatory fields have valid values. | RTA-1906 |
| Data Set | The Expected Value feature is now properly working and showing correct validations. | RTA-1906 |
| Data Set | Fixed an issue where the view details functionality for an added data setup in a test run is not working. | RTA-1906 |
| Environment | Fixed an issue where an error message is displayed when saving an environment with unchecked Default setting. | RTA-2026 |
| Issue Tracking | Fixed an issue where the API fails when the key does not match the description. | RTA-2029 |
| Scenarios | Tooltips in sequencing are now displayed for long scenario names. | RTA-1924 |
Scenarios Services | Query Type services in the Services module and scenario datasets in the Scenarios module can now use the Check Query functionality. | RTA-1945 |
| Services | Query service types have been assigned a new color and added to the service type legends. | RTA-2031 |
Test Run Services | Fixed an issue where a test execution continues running even if an invalid dataset was selected. | RTA-2044 |
| Test Run | Steps are now marked as Failed with the correct error message when SFTP details are improperly configured. | RTA-2032 |
Test Run Validation Services | API validation services are now successfully executing. | RTA-2002 |
Breaking changes
If you are upgrading from an earlier version, refer to the Upgrade Notes for necessary actions you should be aware of when upgrading.
Test Assistant 2024.03.01.01
Release Date: 11 March 2024
New features
This section provides the list of new features and enhancements that have been added in this release.
| Module/s | Feature description | JIRA |
|---|
| Environment | A Test Connection button is now available to verify the SFTP configuration. | RTA-1919 |
Fixed issues
This section provides the list of issues that have been fixed in this release.
| Module/s | Fix description | JIRA |
|---|
| Dashboard | Fixed an issue where the page number do not update after applying a filter on the Recent Activities section. | RTA-1937 |
| Dashboard | Fixed an issue with the validation of StartAt and EndAt date filters. Now, the StartAt date must be earlier than the EndAt date, and the EndAt date must come after the StartAt date. | RTA-1937 |
| Dataset | Fixed an issue where Data Sets inputs are not accepted, causing UI test scripts to fail during login. | RTA-2040 |
Environment Test Run | Fixed an issue where SFTP test execution fail to start due to an incorrect password set in the Environment module, with no error messages provided. Clear error messages about invalid SFTP connection details are now displayed in the Test Results.
| RTA-1917 |
Breaking changes
If you are upgrading from an earlier version, refer to the Upgrade Notes for necessary actions you should be aware of when upgrading.
Test Assistant 2024.03.01.00
Release Date: 4 March 2024
New features
This section provides the list of new features and enhancements that have been added in this release.
| Module/s | Feature description | JIRA |
|---|
| All modules | The Test Assistant now has an improved search component that allows for faster searching of items and switching to another module. | RTA-1868 |
| Dashboard | You should click twice on the graph in the Run Summary to apply the filter on the Run Results. | RTA-1889 |
| Run Results | The test reports now display the steps that have been set to be ignored during the testing process. | RTA-1897 |
| Service | The Form Data option for Payload details is now available when creating a new service. | RTA-1873 |
| Test Run | The verifyElementPresent command has been added to check the presence of a particular element or value. If the specified element or value is not present, the test run remains in progress. | RTA-1889 |
Fixed issues
This section provides the list of issues that have been fixed in this release.
| Module/s | Fix description | JIRA |
|---|
| All modules | The count on the module icons in card and list views are now consistent with the correct number of items in the module. | RTA-1962 |
| Breadcrumbs | Fixed an issue where parts of breadcrumbs disappeared after refreshing the page. | RTA-2023 |
| Dashboard | Fixed an issue where the Test Assistant crashes if the user duplicates the browser tab of the in-progress live test execution. | RTA-1890 |
| Dashboard | Fixed the UI misalignments on the dashboard. | RTA-2007 |
| Dashboard | Fixed an issue on the Azure DevOps Services API where the access token, issue tracking project, and the created tickets are not loading properly. | RTA-2011 |
Dashboard Login screen | The year on the footer and the login screen have been changed from 2023 to 2024. | RTA-1911 |
| Dataset | The Clear Data option is now visible on the Dataset page when a path, query, or header is specified. | RTA-1859 |
| Dataset | Fixed an issue where the other fields retain their values when updating the Scenario of a dataset. | RTA-2013 |
| Dataset | A dataset can now be created. | RTA-2019 |
Dataset Run Results Service Validation service | The Beautify is now working on the specified modules. | RTA-1865 |
| External System | Fixed an issue where the links on the list and card views are not working. | RTA-1891 |
| External System | The icons on the footer of a card are now directing the users to the correct page. | RTA-1921 |
Features Templates | Fixed an issue where an error message is displayed when the Features or Templates module is accessed. | RTA-1909 |
| Run Results | The empty column on the non-query validation service popup window has been removed. | RTA-1854 |
| Run Results | The correct steps sequence is now displayed during live execution for tests with multiple datasets. | RTA-1895 |
| Run Results | The screenshot name is now displayed on the image header regardless of command count. | RTA-1959 |
| Scenario | Fixed an issue where the link icon on the Scenarios page does not direct the users to the scenario linking screen. | RTA-1064 |
| Scenario | The name and path now display values when a JSON path is added to the Velocity Script Details of a scenario. | RTA-1908 |
| Scenario | Fixed an issue where the Replace File in the Dataset page is unchecked even if it was set to true in the Velocity Script Details. | RTA-1908 |
| Scenario | Fixed an issue where the multiple file paths added to a scenario are not being saved. | RTA-1908 |
| Scenario | The feature names are now displayed in the Feature Name filter. | RTA-1910 |
| Scenario | Fixed an issue where an error message is displayed when a filter is selected during dataset generation. | RTA-1935 |
| Scenario | Fixed an issue where an error message is displayed when updating a dataset. | RTA-1938 |
| Service | Fixed an issue where some of the fields are not displaying when creating a new API service. | RTA-1876 |
| Service | A Query or SFTP service can now be updated. The unnecessary fields for the Query service have been removed. | RTA-1913 |
| Service | The combined URLs in the Service URL field are now displayed properly. | RTA-1957 |
| Step | Fixed an issue where the service modifications are not reflected in the Steps page associated with it. | RTA-1863 |
| Step | The Step page now displays all expected details. | RTA-1964 |
| Templates | The error message related to the JDBC connection that was appearing while accessing the Templates page has been fixed. | RTA-1914 |
| Test Run | Fixed an issue where other environment options cannot be selected. | RTA-1922 |
| Test Run | An error message is now displayed when a step has been removed from a scenario and the associated data set has not been updated. | RTA-1948 |
| Test Run | The validation service associated with a step is now displayed during execution. | RTA-2004 |
| Test Run | Fixed an issue where the Element not found error message is displayed for UI elements present in the test environment. | RTA-2015 |
| Validation Service | The SQL ASSERSION is now working with the API. | RTA-1999 |
Breaking changes
If you are upgrading from an earlier version, refer to the Upgrade Notes for necessary actions you should be aware of when upgrading.
Test Assistant 2024.01.01.00
Release Date: 5 January 2024
New features
This section provides the list of new features and enhancements that have been added in this release.
| Module | Feature description |
|---|
Configurations Projects | JIRA and Azure DevOps integrations |
Dashboard Run Results | The Run Results graph now displays Project Name instead of Run ID when hovering on the bars. |
| Filters | Advanced filter options allowing multiple filter criteria have been added to all the pages. |
| Scenarios | Scenarios can now be sorted by Step Type. |
| Services | A click command can now be added to the service Request Body template. |
| Test Results | Bulk execution result reports can now be exported to your specified local or cloud storage. |
Test Run Validation Services | Databases can now be specified in the Test Run and Validation Services modules. |
Fixed issues
This section provides the list of issues that have been fixed in this release.
| Module | Fix description |
|---|
| Data Sets | Fixed an issue where an additional node in the Request Body was displayed when viewing a data set. |
| Data Sets | Fixed an issue where parameter values are interchanged when updating a data set. |
Dashboard Run Results | Filter by Run Id in the Dashboard and the Run Results module now works properly. |
Dashboard Run Results | Filter by execution date in the Run Results module now works properly. |
| Projects | Project names can no longer contain special characters. |
| Projects | The Select Issue Tracking Project field no longer becomes empty when editing a project. |
| Scenarios | Fixed an issue where partially matching database names were not displayed when typing a name on the Select Database field while creating a new scenario. |
Scenarios Steps | Fixed an issue where an incorrect Response Body template was displayed when linking steps or scenarios. |
| Templates | Templates can no longer be created without a unique Template Code. |
| Templates | The sequence number for scenarios is now displayed when updating a template. |
| Test Run | Fixed an issue where the Execute Test Suite button remained disabled after filling out all mandatory fields when configuring a new test run. |
| Test Run | The Payloads section now displays the configured template in the Request Body during live runs. |
| Test Run | Mandatory fields are now enabled for query executions. |
| Test Run | Fixed an issue where clicking the back button triggered a new execution. |
| Validation Services | Fixed an issue where default values were set for URL and HTTP method fields in Query type validation services. |
| Validation Services | Fixed an issue where configured Field Labels are not captured in the Validation Services module. |
| Validation Services | Fixed an issue where the Extract Filters button is not working when there are no dynamic input parameters in the Query. |
2.1 - Upgrade Notes
This document provides information about necessary actions or considerations when upgrading to a newer version of Test Assistant.
For the latest updates and information on Test Assistant releases, please refer to the Release Notes.
For the most recent product highlights, see What’s New in Test Assistant.
Upgrade to Test Assistant 2024.10.01.00
Test Assistant has been upgraded to version 2024.10.01.00. The commons version has also been upgraded. To prevent any issues, run the following commands:
alter table tbl_project add column all_scenarios bool null;
alter table tbl_project add column auto_ticket_creation bool null;
alter table tbl_test_suite_execution add column all_scenarios_template bool null;
alter table tbl_test_suite_execution add column auto_ticket_creation_template bool null;
CREATE OR REPLACE VIEW vw_project
AS SELECT tp.project_id,
tp.project_code,
tp.project_desc,
tp.project_name,
tp.logo,
tp.metadata,
tp.created_by,
tp.created_dttm,
tp.last_modified_by,
tp.last_modified_dttm,
tp.jira_project_name,
( SELECT count(1) AS count
FROM tbl_feature tf
WHERE tf.project_id = tp.project_id) AS feature_count,
( SELECT count(1) AS count
FROM tbl_scenario ts
WHERE ts.project_id::bpchar = tp.project_id) AS scenario_count,
ARRAY( SELECT tpesm.system_id
FROM tbl_project_external_system_map tpesm
WHERE tpesm.project_id = tp.project_id) AS system_ids,
( SELECT count(1) AS count
FROM tbl_test_suite_template_dummy ttstd
WHERE ttstd.project_id::bpchar = tp.project_id) AS template_count,
array_length(ARRAY( SELECT tpesm.system_id
FROM tbl_project_external_system_map tpesm
WHERE tpesm.project_id = tp.project_id), 1) AS system_count,
tp.auto_ticket_creation,
tp.all_scenarios
FROM tbl_project tp;
-- public.vw_external_system source
CREATE OR REPLACE VIEW vw_external_system
AS SELECT tes.system_name,
tes.system_code,
tes.system_id,
tes.system_desc AS description,
tes.logo,
tes.created_by,
tes.created_dttm,
tes.last_modified_by,
tes.last_modified_dttm,
( SELECT count(env.env_id) AS count
FROM tbl_environment env
WHERE env.system_id = tes.system_id
GROUP BY env.system_id) AS environments_count,
( SELECT count(ts.svc_id) AS count
FROM tbl_service ts
WHERE ts.system_id = tes.system_id
GROUP BY ts.system_id) AS services_count,
( SELECT count(tvs.vld_svc_id) AS count
FROM tbl_validation_service tvs
WHERE tvs.system_id = tes.system_id
GROUP BY tvs.system_id) AS valid_services_count,
NULLIF(( SELECT count(*) AS count
FROM vw_project vp
WHERE tes.system_id = ANY (vp.system_ids)), 0) AS projects_count,
( SELECT count(stp.step_id) AS count
FROM tbl_step stp
WHERE stp.system_id = tes.system_id
GROUP BY stp.system_id) AS steps_count,
( SELECT te.base_url
FROM tbl_environment te
WHERE te.system_id = tes.system_id AND te.active = true) AS base_url
FROM tbl_external_system tes;
update
tbl_filter_configuration
set
column_display_name
= 'ID/Key',
column_name
='ID/Key'
where
column_display_name
='ADO ID'
;
Upgrade to Test Assistant 2024.06.01.00
Test Assistant has been upgraded to version 2024.06.01.00 to improve JIRA and Azure integrations. To apply these improvements to your Test Assistant, run the following commands:
UPDATE tbl_issue_tracking_endpoint
SET metadata =
'{
"input-template": "[\n {\n \"op\": \"add\",\n \"path\": \"/fields/System.ChangedDate\",\n \"from\": null,\n \"value\": \"\"\n }\n #if ($StringUtil.hasLength($root.title))\n ,{\n \"op\": \"add\",\n \"path\": \"/fields/System.Title\",\n \"from\": null,\n \"value\": $root.title\n }\n #end\n #if ($StringUtil.hasLength($root.description))\n ,{\n \"op\": \"add\",\n \"path\": \"/fields/System.Description\",\n \"from\": null,\n \"value\": $root.description\n }\n #end\n #if($Objects.nonNull($root.labels))\n , {\n \"op\": \"replace\",\n \"path\": \"/fields/System.Tags\",\n \"from\": null,\n \"value\": \"#foreach($label in $root.labels)$label.asText()#if($foreach.hasNext); #end#end\"\n }\n #end\n #if ($StringUtil.hasLength($root.attachmentUrl))\n , {\n \"op\": \"add\",\n \"path\": \"/relations/-\",\n \"value\": {\n \"rel\": \"AttachedFile\",\n \"url\": $root.attachmentUrl,\n \"attributes\": {\n \"comment\": \"TA Attachment Added\"\n }\n }\n }\n #end\n #if ($StringUtil.hasLength($root.fields.linkUrl))\n , {\n \"op\": \"add\",\n \"path\": \"/relations/-\",\n \"value\": {\n \"rel\": $root.fields.linkType,\n \"url\": $root.fields.linkUrl,\n \"attributes\": {\n \"comment\": \"Making a new link for the dependency\"\n }\n }\n }\n #end\n]",
"output-template": "#macro(getDescription $fields)\n#if($StringUtil.hasLength($fields[\"Microsoft.VSTS.TCM.SystemInfo\"]))\n$fields[\"Microsoft.VSTS.TCM.SystemInfo\"]##\n#else\n#if($StringUtil.hasLength($fields[\"System.Description\"]))\n$fields[\"System.Description\"]##\n#else\"\"##\n#end\n#end\n#end\n#macro(getLabels $labels)\n#if($StringUtil.hasLength($root.fields[\"System.Tags\"]))\n#foreach($label in $labels.asText().split(\";\"))\"$StringUtil.trimWhitespace($label)\"#if($foreach.hasNext), #end#end\n#end\n#end\n{\n \"key\": $root.id,\n \"project\": $root.fields[\"System.TeamProject\"],\n \"issueType\": $root.fields[\"System.WorkItemType\"],\n \"title\": $root.fields[\"System.Title\"],\n \"fields\":{\n \"priority\": $root.fields[\"Microsoft.VSTS.Common.Priority\"],\n \"severity\": $root.fields[\"Microsoft.VSTS.Common.Severity\"]\n },\n \"description\": #getDescription($root.fields),\n \"labels\": [#getLabels($root.fields[\"System.Tags\"])],\n \"status\": $root.fields[\"System.State\"],\n \"createdBy\": $root.fields[\"System.CreatedBy\"].displayName,\n \"createdDate\": $root.fields[\"System.CreatedDate\"],\n \"avatar\": null\n #if($Objects.nonNull($root.fields[\"System.AssignedTo\"]))\n , \"assignee\": $root.fields[\"System.AssignedTo\"].displayName\n #end\n #if($baseUrl)\n , \"selfUrl\": \"$baseUrl/$root.fields[\"System.TeamProject\"].asText()/_workitems/edit/$root.id.asText()/\"\n #end\n}",
"default-params": [
{
"type": "query",
"name": "api-version",
"alias": "api-version",
"value": "7.0"
}
],
"input-params": [
{
"type": "path",
"name": "id",
"alias": "id",
"required": "Y"
}
]
}'
WHERE provider = 1 AND tran_type = 'update-issue';
INSERT INTO public.tbl_issue_tracking_endpoint (issue_tracking_endpoint_id,http_method,metadata,provider,tran_type,url) VALUES
('35daead53bfc4a108f9f30961a86d394','GET','{
"input-template": "",
"output-template": "{\n \"fields\" : [\n #foreach($type in $root.value)\n {\n \"name\": $type.name,\n \"referenceName\": $type.referenceName, \n \"attributes\": $type.attributes,\n \"url\": $type.url\n }#if($foreach.hasNext),#end\n #end\n ]\n}",
"default-params": [
{
"type": "query",
"name": "api-version",
"alias": "api-version",
"value": "7.0"
}
],
"input-params": [ ]
}',1,'get-relation-types','/_apis/wit/workitemrelationtypes');
UPDATE tbl_issue_tracking_endpoint
SET metadata =
'{
"input-template": "#set($filterAdded = false)\n#macro(setWithFilter)#set($filterAdded = true)#end\n{\n \"query\": \"Select [System.Id] From WorkItems Where#if($Objects.nonNull($root.project) && !$root.project.isEmpty)#setWithFilter() [System.TeamProject] IN (#foreach($project in $root.project)''$project.asText()''#if($foreach.hasNext), #end#end) #end#if($Objects.nonNull($root.issueType) && !$root.issueType.isEmpty)#if($filterAdded) AND #end#setWithFilter() [System.WorkItemType] IN (#foreach($issueType in $root.issueType)''$issueType.asText()''#if($foreach.hasNext), #end#end) #end#if($Objects.nonNull($root.title))#if($filterAdded) AND #end#setWithFilter() [System.Title] Contains ''$root.title.asText()'' #end#if($Objects.nonNull($root.id) && !$root.id.isEmpty)#if($filterAdded) AND #end#setWithFilter() [System.Id] IN (#foreach($id in $root.id)''$id.asText()''#if($foreach.hasNext), #end#end) #end#if($Objects.nonNull($root.status) && !$root.status.isEmpty)#if($filterAdded) AND #end#setWithFilter() [System.State] IN (#foreach($status in $root.status)''$status.asText()''#if($foreach.hasNext), #end#end) #end#if($Objects.nonNull($root.assigneeNameOrEmail) && !$root.assigneeNameOrEmail.isEmpty)#if($filterAdded) AND #end#setWithFilter() [System.AssignedTo] IN (#foreach($assignee in $root.assigneeNameOrEmail)''$assignee.asText()''#if($foreach.hasNext), #end#end) #end#if($Objects.nonNull($root.label) && !$root.label.isEmpty)#if($filterAdded) AND #end#setWithFilter() (#foreach($label in $root.label) [System.Tags] Contains ''$label.asText()''#if($foreach.hasNext) OR#end#end)#end Order By [System.Id] DESC\"\n}",
"output-template": "{\n \"ids\": \"#foreach($item in $root.workItems)$item.id#if($foreach.hasNext),#end#end\"\n}",
"default-params": [
{
"type": "query",
"name": "api-version",
"alias": "api-version",
"value": "7.0"
},
{
"type": "query",
"name": "$top",
"alias": "$top",
"value": "50"
}
],
"input-params": []
}'
WHERE provider = 1 AND tran_type = 'azure-wiql-search';
ALTER TABLE tbl_test_suite_execution ADD COLUMN parent_issue VARCHAR null;
ALTER TABLE tbl_ts_step_execution ADD COLUMN link_ticket VARCHAR null;
INSERT INTO public.tbl_filter_configuration (filter_id,data_type,field_name,field_desc,field_type,"operator",entity_id,column_display_name,column_name,value,selected) VALUES
('40289de38f9ad1ae018f9afebf5b0003','AUTOCOMPLETE',NULL,NULL,NULL,5,'40289de38f9ad1ae018f9aee7ad00000','Issue Type','Issue Type',NULL,NULL),
('40289de38f9ad1ae018f9afebf5b0004','AUTOCOMPLETE',NULL,NULL,NULL,5,'40289de38f9ad1ae018f9aee7ad00000','Title','Title',NULL,NULL),
('40289de38f9ad1ae018f9afebf5b0006','AUTOCOMPLETE',NULL,NULL,NULL,5,'40289de38f9ad1ae018f9aee7ad00000','Label','Labels',NULL,NULL);
INSERT INTO public.tbl_filter_configuration (filter_id,data_type,field_name,field_desc,field_type,"operator",entity_id,column_display_name,column_name,value,selected) VALUES
('40289de38f9ad1ae018f9afebf5a0002','AUTOCOMPLETE',NULL,NULL,NULL,5,'40289de38f9ad1ae018f9aee7ad00000','Keys','Keys',NULL,NULL);
INSERT INTO public.tbl_filter_configuration (filter_id,data_type,field_name,field_desc,field_type,"operator",entity_id,column_display_name,column_name,value,selected) VALUES
('40289de38f9ee704018fa9688c770007','AUTOCOMPLETE',NULL,NULL,NULL,5,'40289de38f9ad1ae018f9aee7ad00000','Status','Status',NULL,NULL);
INSERT INTO public.tbl_entity (entity_id,entity_desc,entity_fields,entity_name) VALUES
('40289de38f9ad1ae018f9aee7ad00000',NULL,NULL,'Issues Reported');
Upgrade to Test Assistant 2024.05.02.00
Test Assistant has been upgraded to version 2024.05.02.00 to define a schema in the Environment module. This new feature will allow the fetching of data from different schemas instead of setting the schema in SQLs. Run the following command in your Test Assistant database:
ALTER TABLE tbl_database_details ADD COLUMN "schemas" _text null;
Upgrade to Test Assistant 2024.05.01.00
Test Assistant has been upgraded to version 2024.05.01.00 to improve the integration of Test Assistant with Azure DevOps. Run the following commands in your Test Assistant database:
{% code lineNumbers=“true” fullWidth=“false” %}
UPDATE tbl_issue_tracking_endpoint
SET metadata =
'{[\n {\n \"op\": \"add\",\n \"path\": \"/fields/System.Title\",\n \"from\": null,\n \"value\": $root.title\n },\n {\n \"op\": \"add\",\n \"path\": #if($root.issueType.asText().equals(\"Bug\"))\"/fields/Microsoft.VSTS.TCM.ReproSteps\"#else\"/fields/System.Description\"#end,\n \"from\": null,\n \"value\": $root.description\n },\n {\n \"op\": \"add\",\n \"path\": \"/fields/Microsoft.VSTS.Common.ValueArea\",\n \"from\": null,\n \"value\": \"Business\"\n },\n {\n \"op\": \"add\",\n \"path\": \"/fields/System.AreaPath\",\n \"from\": null,\n \"value\": \"$root.project.asText()\\\\FAAD\\\\Fee Operations and Billing\"\n },\n {\n \"op\": \"add\",\n \"path\": \"/fields/NT.Test.DefectType\",\n \"from\": null,\n \"value\": \"Functional\"\n },\n {\n \"op\": \"add\",\n \"path\": \"/fields/NT.Release.DetectedInRelease\",\n \"from\": null,\n \"value\": \"2024-02-13T06:00:00Z\"\n },\n {\n \"op\": \"add\",\n \"path\": \"/fields/NT.App.PrimaryTLA\",\n \"from\": null,\n \"value\": \"GFB*Global Fee Billing*APM0002620\"\n },\n {\n \"op\": \"add\",\n \"path\": \"/fields/NT.App.HotFix\",\n \"from\": null,\n \"value\": false\n },\n {\n \"op\": \"add\",\n \"path\": \"/fields/NT.App.Releasable\",\n \"from\": null,\n \"value\": true\n }\n #if($Objects.nonNull($root.labels) && !$root.labels.isEmpty())\n , {\n \"op\": \"add\",\n \"path\": \"/fields/System.Tags\",\n \"from\": null,\n \"value\": \"#foreach($label in $root.labels)$label.asText()#if($foreach.hasNext); #end#end\"\n }\n #end\n ,\n {\n \"op\": \"add\",\n \"path\": \"/fields/Microsoft.VSTS.Common.Priority\",\n \"from\": null,\n \"value\": $root.fields.priority\n },\n {\n \"op\": \"add\",\n \"path\": \"/fields/Microsoft.VSTS.Common.Severity\",\n \"from\": null,\n \"value\": $root.fields.severity\n }\n ]",
"output-template": "#macro(getDescription $fields)\n#if($StringUtil.hasLength($fields[\"Microsoft.VSTS.TCM.SystemInfo\"]))\n$fields[\"Microsoft.VSTS.TCM.SystemInfo\"]##\n#else\n#if($StringUtil.hasLength($fields[\"System.Description\"]))\n$fields[\"System.Description\"]##\n#else\"\"##\n#end\n#end\n#end\n#macro(getLabels $labels)\n#if($StringUtil.hasLength($root.fields[\"System.Tags\"]))\n#foreach($label in $labels.asText().split(\";\"))\"$StringUtil.trimWhitespace($label)\"#if($foreach.hasNext), #end#end\n#end\n#end\n{\n \"key\": $root.id,\n \"project\": $root.fields[\"System.TeamProject\"],\n \"issueType\": $root.fields[\"System.WorkItemType\"],\n \"title\": $root.fields[\"System.Title\"],\n \"fields\":{\n \"priority\": $root.fields[\"Microsoft.VSTS.Common.Priority\"],\n \"severity\": $root.fields[\"Microsoft.VSTS.Common.Severity\"]\n },\n \"description\": #getDescription($root.fields),\n \"labels\": [#getLabels($root.fields[\"System.Tags\"])],\n \"status\": $root.fields[\"System.State\"],\n \"createdBy\": $root.fields[\"System.CreatedBy\"].displayName,\n \"createdDate\": $root.fields[\"System.CreatedDate\"],\n \"avatar\": null\n #if($Objects.nonNull($root.fields[\"System.AssignedTo\"]))\n , \"assignee\": $root.fields[\"System.AssignedTo\"].displayName\n #end\n #if($baseUrl)\n , \"selfUrl\": \"$baseUrl/$root.fields[\"System.TeamProject\"].asText()/_workitems/edit/$root.id.asText()/\"\n #end\n}",
"default-params": [
{
"type": "query",
"name": "api-version",
"alias": "api-version",
"value": "7.0"
}
],
"input-params": [
{
"type": "path",
"name": "project",
"alias": "project",
"required": "Y"
},
{
"type": "path",
"name": "type",
"alias": "type",
"required": "Y"
}
]
}'
WHERE provider = 1 AND tran_type = 'create-issue';
INSERT INTO public.tbl_issue_tracking_endpoint (issue_tracking_endpoint_id,http_method,metadata,provider,tran_type,url) VALUES
('5f44fc32e4ea11edb5ea0242ac120003','GET','{
"input-template": "",
"output-template": "{\n \"fields\" : [\n #foreach($type in $root.value)\n {\n \"name\": $type.name,\n \"referenceName\": $type.referenceName, \n \"alwaysRequired\": $type.alwaysRequired,\n \"defaultValue\": $type.defaultValue,\n \"allowedValues\": $type.allowedValues,\n \"dependentFields\": $type.dependentFields,\n \"url\": $type.url\n }#if($foreach.hasNext),#end\n #end\n ]\n}",
"default-params": [
{
"type": "query",
"name": "$expand",
"alias": "$expand",
"value": "All"
},
{
"type": "query",
"name": "api-version",
"alias": "api-version",
"value": "7.0"
}
],
"input-params": [
{
"type": "path",
"name": "project",
"alias": "project",
"required": "Y"
},
{
"type": "path",
"name": "type",
"alias": "type",
"required": "Y"
}
]
}',1,'get-work-item-fields','/{project}/_apis/wit/workitemtypes/{type}/fields');
Upgrade to Test Assistant 2024.04.01.00
Test Assistant has been upgraded to version 2024.04.01.00 to fix the following issues:
- where the downloaded CSV data set file does not display the correct sequence of steps and includes fields that are not present in the data set.
ALTER TABLE tbl_document add data_bkup oid ;
ALTER TABLE tbl_document ADD COLUMN data_new BYTEA;
UPDATE tbl_document SET data_new = lo_get(data);
ALTER TABLE tbl_document DROP COLUMN data;
ALTER TABLE tbl_document RENAME COLUMN data_new TO data;
- where error message is displayed when creating or updating an external system with logo.
{% code overflow=“wrap” lineNumbers=“true” %}
UPDATE tbl_step SET step_template = jsonb_set( step_template::jsonb, '{params}','{}'::jsonb,false) where step_type = 'UI' and step_template not like '%"params":{}%'and step_template not like '%"params": {"headers": null, "pathParams": null, "queryParams": null}%';
Upgrade to Test Assistant 2024.03.02.00
Test Assistant has been upgraded to version 2024.03.02.00 to fix the issue where an error message is displayed when accessing a Run ID associated with an SFTP scenario. You need to run the following queries in your database SQL editor:
ALTER TABLE tbl_downloaded_files ADD COLUMN byte_download_data bytea;
UPDATE tbl_downloaded_files SET byte_download_data = lo_get(download_data)::bytea;
ALTER TABLE tbl_downloaded_files RENAME COLUMN download_data TO download_data_bkup;
ALTER TABLE tbl_downloaded_files RENAME COLUMN byte_download_data TO download_data;
ALTER TABLE tbl_document ADD COLUMN byte_data bytea;
UPDATE tbl_document SET byte_data = lo_get("data")::bytea;
ALTER TABLE tbl_document RENAME COLUMN "data" TO data_bkup;
ALTER TABLE tbl_document RENAME COLUMN byte_data TO "data";
Upgrade to Test Assistant 2024.03.01.01
Test Assistant has been upgraded to version 2024.03.01.01 to fix the following issues:
- where the Data Sets module throws an exception message when loading, saving, and executing SFTP Upload datasets. You need to run the following queries in your database SQL editor:
ALTER TABLE tbl_files_dto ADD COLUMN byte_upload_data bytea;
UPDATE tbl_files_dto SET byte_upload_data = lo_get(upload_data)::bytea;
ALTER TABLE tbl_files_dto RENAME COLUMN upload_data TO upload_data_bkup;
ALTER TABLE tbl_files_dto RENAME COLUMN byte_upload_data TO upload_data;
- issue where the Dashboard page does not properly display statistics and graphs. You need to run the following queries in your database SQL editor:
CREATE OR REPLACE FUNCTION refresh_vw_grouped_scenario()
RETURNS TRIGGER LANGUAGE plpgsql
AS $$
BEGIN
REFRESH MATERIALIZED VIEW vw_grouped_scenario;
RETURN NULL;
END $$;
CREATE TRIGGER refresh_vw_grouped_scenario
AFTER INSERT OR UPDATE OR DELETE OR TRUNCATE
ON tbl_ts_scenario_execution
FOR EACH STATEMENT
EXECUTE PROCEDURE refresh_vw_grouped_scenario();
Upgrade to Test Assistant 2024.03.01.00
Before running the Test Assistant, ensure that you have added the following to the specified YAML files:
config/executor/application-{env}.yml
uidriver:
autodownload: false
config/api-gateway/application-{env}.yml
Upgrade to Test Assistant 2023.09.01.00
There are no new microservices for this release. This means that no new service needs to be deployed. Ensure all your property files are moved to the 2023.09.01 folder, and your test script runs are using version 2023.09.01.
Upgrade to Test Assistant 2.8.0
Uninstall the previous version
Before installing Test Assistant 2.8.0, ensure that you have uninstalled the previous version.
To uninstall microservices, kill the following java processes:
Core.jar
Executor.jar
Gateway.jar
To uninstall older versions for the front end, do the following:
- Navigate to the
html folder of Nginx.
- Delete all contents of the folder.
Installation prerequisite
A TA-2.8.0.zip is provided for all clients seeking to upgrade Test Assistant. To prepare the requirements before deployment, do the following:
- Extract the contents to
2.8.0 folder in /usr/appl/gfb/riata.
- Copy the
application-uat.yml file from the older version of the core and executor folders to the newer version.
For example, copy the application-uat.yml file from the /usr/appl/gfb/riata/2.7.0/core folder to /usr/appl/gfb/riata/2.8.0/core folder.
- Copy the contents of the
insert-properties file to the end of the application-uat.yml file in the core and executor folders.
Deploy the application
To run the new microservices, run the following:
nohup java -jar /usr/appl/gfb/riata/2.8.0/sql-api.jar -Dspring.profiles.active=uat -Dspring.config.location/usr/appl/gfb/riata/2.8.0/application-uat.yml > /usr/appl/gfb/riata/2.8.0/logs/sql-api.log 2>&1 &
To update the front end, do the following steps.
Ensure that you have already extracted the contents of the provided TA-2.8.0.zip.
- Copy all the contents in the
UI folder to the html folder of Nginx.
- Restart your Nginx server.