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.
You can contact us by phone, email, or the discussion
forums. Visit the NI
Website to contact us.
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
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
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.
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.