|
|
|
|
Release Notes |
Home Company Profile Products Support Partners Release Notes Application Notes Papers and Info Problem Report FAQ |
Release Notes 1. Overview This is a maintenance release. 2. Detailed Description 2.1 Critical items 2.1.1 File Download dialog If TestBase IDE is running on Windows XP SP2 with Visio 2000 or Visio 2002, the “File Download” dialog pops up when the user opens a Control Flow Diagram (for a DP) or the Stencil. To prevent the appearance of this dialog in subsequent opening operations the user must uncheck the checkbox “Always ask before opening this type of file.” and press Open button in this dialog to allow the completion of the opening operation. 2.1.2 Permissions for installation & security administration The user performing the installation must have Administrator permissions for the Windows operating system. After installing TestBase, this user must start the IDE once, to perform a Registry initialization. After that, users with more restricted permissions can use the TestBase modules. 2.1.3 Configuration of environment variables (general) The TestBase environment variables are reset to their default values during the installation of a new version. They must be manually set to the values used by the previous version of TestBase. 2.1.4 Configuration of environment variables when using the LabVIEW Adapter The LabVIEW Adapter loads the LabVIEW engine when it is loaded by TestBase, and unloads the engine when it is unloaded. It appears that the repeated unloading and reloading of the LabVIEW engine causes unreliable operation. Thus, for a reliable operation of the LabVIEW test procedures it is recommended to set the value of the environment variable TB_TCA_UNLOAD to 0 (zero). 2.1.5 Security setting for third-party applications Recent versions of Microsoft Excel and Visio support a more flexible configuration of their security features, which includes the ability to execute macros. TestBase uses such macros to implement integration with Excel and Visio. Consequently, these products have to be configured properly, to accept the execution of macros. Detailed instructions are provided in the TestBase Installation Guide. 2.1.6 Configuration of Functional Test Controller (FTC) execution reports When generating FTC Execution Reports that include Test Information and Parameter Values, it is strongly recommended to use separate files, instead of appending information to the same file. If information is appended to the same file, this file will eventually become very large and this will increase the execution time. Use the FTC menu Tools | Options | UI_FT Specific to configure the generation of execution reports. 2.1.7 Configuring Visio 2000 for generation of Diagnostic Procedure Reports When generating a report for a Diagnostic Procedure, you may get the error message “Unable to export CFD”. The report files containing the Visio diagram are not generated. The report file containing the text description of the diagnostic strategy is generated, but its hyperlinks will not operate. This problem occurs if Visio Professional was installed on the system but its HTML export feature was never used. To fix the problem, the feature must be exercised once as follows: open an existing flowchart in Visio or create a new one (menu File | New) export the flowchart as HTML (menu File | Save As, select file type “HTML Files”, select a temporary folder and press OK). 2.1.8 Limitations of Evaluation License The evaluation license is valid for 30 days from the date you install TestBase and provides you with full functionality with the following exceptions: 2.1.9 Shortcut keys (functionality change) The shortcut keys (accelerators) that did not operate properly in some contexts were removed from the menu. The shortcut keys that are currently shown in the menu do operate properly. You should avoid using any shortcut keys that are not in the menu. 2.1.10 Case sensitivity of Outcome comparisons (functionality change) When a Test block is followed by decision blocks, the compiler compares the outcome values tested by the decision blocks against the set of possible outcomes returned by the called Test procedure. In some of the previous releases, the above comparison was case insensitive. For consistency with other comparisons in TestBase, the comparison algorithm was changed to case sensitive, starting with release 2.4.0. This change does not affect the operation of existing projects and does not require their recompilation. 2.1.11 Running ATLAS Test Procedure from sample database used in the Developer's Manual To run the ATLAS Test Procedure from Developer’s Manual sample database you must disable the run-time Test Diagram Viewer from PAWS Run Time System. 2.1.12 Operating system compatibility The product works properly with Windows NT 4.0 SP 6, Windows 2000 SP 2 and Windows XP SP 2. 2.1.13 Internet Explorer compatibility The product works properly with Microsoft Internet Explorer 5.5 and 6.0. It does not work with Internet Explorer 5.0. 2.1.14 Microsoft Office compatibility The display of Excel reports works properly with Microsoft Office 2000 Service Release 1, Microsoft Office XP and Microsoft Office 2003. 2.1.14 Microsoft Visio compatibility The product works properly with Microsoft Visio 2000, Visio 2002 and Visio 2003. 2.1.16 Oracle compatibility The MTI Controller distributed with the current version of the product was tested with the following combinations of versions for server and client:
A compatibility problem exists between the Oracle software and the Microsoft libraries used internally by TestBase. This problem may be corrected, for Oracle 8 versions, by configuring the system registry as described in the document Connectivity Issue with MDAC and Oracle8i.pdf. For Oracle 9, use the information provided for version 8.1 in the above document, performing the following replacements in the strings to be entered in the registry:
2.1.17 LabWindows/CVI compatibility The Adapter for LabWindows/CVI works properly with the following versions: 5.0, 5.5 and 6.0. Minor changes to the sample test code must be performed in order to compile it under version 5.0. The TestBase installation package redistributes version 6.0 of the LabWindows/CVI Run Time Engine. You may obtain other versions of the Run Time Engine from National Instruments. 2.2 Known Limitations 2.2.1 TestBase IDE The “Undo” command used during flowchart editing operates with some limitations (see examples below). After performing an Undo, it is recommended to verify its effect on the flowchart and the parametric data displayed in the grid. The “Undo” command for the addition of an Off-Page Reference block does not delete the “pair” block that was automatically appended. Workaround: delete manually the “pair” block. The “Undo” command for the deletion of a block does not recover the parametric data originally assigned to that block. All parameter values are reset to their defaults. 2.2.2 LabWindows/CVI Adapter A limited subset of scalar data types is currently supported in the TestBase Support Library for LabWindows/CVI. Use direct access to VARIANT fields for other data types. 2.2.3 PAWS Adapter Array parameters are not supported. 2.2.4 LabVIEW Adapter The documentation for developing test procedures with LabVIEW does not cover the use of Custom Data Type Editors as ActiveX controls on LabVIEW panels. 2.2.5 VEE Adapter The documentation for developing test procedures with VEE does not cover the use of Custom Data Type Editors. 2.2.6 Custom Data Types (CDTs) a. The use of CDT Editors is currently not supported in test procedures developed with PAWS ATLAS, SMART ATLAS, VISUAL-ATEC and Agilent VEE.
c. The values of Global Parameters with Custom Data Types are not stored in Oracle and Access MTI databases. You may retrieve these values from the Input Parameters to whom the Global Parameters are assigned. 2.2.7 Diagnostic Procedure reports The internal links of text-based reports will not operate if the set of files generated for a report is moved to a different location in the file system or on a web server. 2.3 Problem Reports and Other Fixes PR07067 – Errors during Export operation for some Test Strategies that contain “corrupted” Diagnostic Procedures The “corrupted” Diagnostic Procedures were probably generated during some operations that caused IDE to terminate abnormally. IDE – Build operation of a Test Strategy is time consuming for the Test Strategy containing numerous DP call blocks Speed has been improved for Build operation. IDE – Errors in drawing the CFDs for imported Test Strategies Problem has been corrected. 2.4 Enhancements
|
