Home Support Documentation Bugs

Test Integration Adapter 2.0 Known Issues

Updated Mar 10, 2020

Overview

This document contains the Test Integration Adapter 2.0 known issues that were discovered before and since the release of Test Integration Adapter 2.0. Not every issue known to NI will appear on this list; it is intended to only show the severe and common issues.

Contacting NI

You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us.

Known Issues by Date

The following items are known issues in Test Integration Adapter 2.0 sorted by Date.

411496—Test results page in RQM cannot display TestStand XML reports
411941—Test results page in RQM has broken links when displaying an HTML report with links to files that were local to the test machine
412124—Test results page in RQM cannot dispaly HTML report that contains ActiveX function
461160—Failed connections still need to be disconnected by user
468014—Cannot install Test Integration Adapter to a non-default directory
468044—Test Integration Adapter does not work correctly on Japanese or Chinese version of Windows.



IDKnown Issue
411496

Return		Test results page in RQM cannot display TestStand XML reports
TestStand has three types of XML reports:- Default XML Report- ATML 2.02 Report- ATML 5.0 ReportThey all require a style sheet file which the server does not currently handle

Workaround: N/A

Reported Version: 1.0  Resolved Version: N/A  Added: 06/19/2013
411941

Return		Test results page in RQM has broken links when displaying an HTML report with links to files that were local to the test machine
If a TestStand HTML report is created on the test machine that contains image or file links to files that were on the test machine at the report's creation, those links will be broken when the HTML report is viewed in the test result page in RQM.

Workaround: Upload the local files as attachments and use those links in the Test Result page instead of links from the HTML report

Reported Version: 1.0  Resolved Version: N/A  Added: 06/19/2013
412124

Return		Test results page in RQM cannot dispaly HTML report that contains ActiveX function
There is one or more type of TestStand HTML reports that draws graphs within HTML report by calling ActiveX API.Web browser on a non-TestStand installation machine can not display picture in the report.

Workaround: N/A

Reported Version: 1.0  Resolved Version: N/A  Added: 06/19/2013
461160

Return		Failed connections still need to be disconnected by user
When the Test Integration Adapter fails to connect to the IBM RQM, users still need to click Disconnect before clicking Connect

Workaround: N/A

Reported Version: 2.0  Resolved Version: N/A  Added: 04/30/2014
468014

Return		Cannot install Test Integration Adapter to a non-default directory
The destination directory page isn't available within the Test Integration Adapter installer.

Workaround: N/A

Reported Version: 1.5  Resolved Version: N/A  Added: 04/30/2014
468044

Return		Test Integration Adapter does not work correctly on Japanese or Chinese version of Windows.
1. If the Adapter Name contains local characters, it does not display correctly in RQM.2. Some control names on the UI do not display correctly.3. If the relative path in the test script contains local characters, a "Bad Execution Request" report will be generated when you run a test.

Workaround: Don't use local characters when specifying the Adapter Name or in the path to the test script.

Reported Version: 2.0  Resolved Version: N/A  Added: 05/05/2014

Document last updated on 5/6/14

Back to top

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).