1. Overview

This release includes the following main items:

• TestBase installation package, including a complete set of sample files, documentation and tutorial slides
• TYX License Manager 2.0.0
• Installation instructions

2. Detailed Description

2.1 Critical items

2.1.1. Operating system compatibility

The product works properly with Windows NT 4.0 SP 6 and Windows 2000 SP 2 and Windows XP.

2.1.2. 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.3. Microsoft Office compatibility

The display of Excel reports works properly with Microsoft Office 2000 Service Release 1 and Microsoft Office XP.

2.1.4. Microsoft Visio compatibility

The product works properly with Microsoft Visio 2000. The current version of the product is not compatible with Visio 2002.

2.1.5. Oracle compatibility

The source of the compatibility problem that occurred for previous versions was identified as being caused by an inconsistency between the Oracle software and the Microsoft libraries used internally by TestBase. This problem may be fixed by configuring the system registry as described in the document Connectivity Issue with MDAC and Oracle8i.pdf.

The MTI Controller distributed with the current version of the product was tested with Oracle 8.1.5 and 8.1.7, under Windows NT 4.0 and Windows 2000.

2.2.1. TestBase IDE

"Undo" and "Paste" commands used during flowchart editing do not operate properly in some situations. It is recommended to avoid using them.

Uppercase and lowercase are not used consistently during design and execution. Workaround: do not define Global Parameters that have identical names but different uppercase/lowercase letters (e.g. "Temperature" and "temperature").

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.

When running a test strategy in debug mode, with execution stopped between steps, if the user clicks on a different Control Flow Diagram then clicks the Run, Step, SimulatedStep or SimulatedStepWithUI buttons, an error message may be displayed: "Automation Error. Illegal to call out while inside message filter". Press OK, click on the Control Flow Diagram that is currently debugged and continue using the IDE. The error indicated before has no impact on subsequent operation.

In some situations accelerator keys (Ctrl-O for File | Open, F5 for Debug | Go, etc.) do not work. Use menus or toolbar buttons instead.

A General Protection Fault occurs when closing IDE or DC GUI after an Abort operation. Because it occurs only when the application is terminated, this behavior does not have harmful effects.

2.2.2. LabWindows support library

A limited subset of scalar data types is currently supported in the library. Workaround: use direct access to VARIANT fields for other data types.

2.3 Enhancements

2.3.1. Installation

The installation procedure was simplified, by eliminating the manual configuration steps required in previous versions. The Installation Manual was also enhanced.

2.3.2. New Adapters

Adapters are available for new languages and formats, as follows.

The product number for this feature is 4951.

The development of ATLAS test procedures requires the PAWS Developer’s Studio version 1.16.0 or higher. The execution of ATLAS test procedures requires the PAWS Run Time System (same version as the one used for development).

This feature is at Beta level in the current release. The functionality is fully implemented and tested. Samples are operational. The development of test procedures is not documented. See the tutorial file Development of ATLAS Test Procedures.pdf under <TestBase installation directory>\Doc\Tutorials for preliminary information.

The product number for this feature is 4952.

The development of COM test procedures requires Microsoft Visual C++ 6.0 or higher, or Microsoft Visual Basic 6.0 or higher. The execution of COM test procedures does not requires special software, besides the services provided by the Operating System.

The development of COM test procedures requires Microsoft Visual C++ 6.0 or higher, or Microsoft Visual Basic 6.0 or higher.

This feature is at Beta level in the current release. The functionality is fully implemented and tested. Samples are operational. The development of test procedures is documented only for Microsoft Visual Basic.

The product number for this feature is 4960.

The development of HTML documents and DHTML reports may be performed with a variety of tools, such as Microsoft FrontPage, Microsoft Visual J++ or Microsoft Word. The display of HTML documents and DHTML reports Microsoft Internet Explores 5.5 or higher (also required by the TestBase IDE).

Other document formats that may be displayed include:

1. Adobe PDF - development requires Adobe Acrobat; display requires only the Adobe Acrobat Reader (freely available)
2. Microsoft Word - development and display requires Microsoft Word (compatible versions to be used for development and display)
3. Microsoft Visio - development and display requires Microsoft Visio (compatible versions to be used for development and display)
4. Any document formats for which an Active Document Server is available on the system

This feature is at Beta level in the current release. The functionality is fully implemented and tested. Samples are operational. The development of DHTML reports is not documented.

2.3.3. Intusoft Importer

This version includes an importer from the TDF file format generated by the Intusoft Test Designer. Run <TestBase installation directory>\Importers\Intusoft\IntuImp.exe and follow the instructions. A TestBase Diagnostic Database (.tdd) will be generated.

The operation of the importer was tested with Intusoft Test Designer version 8.9.8.

This feature is at Beta level in the current release. The functionality is fully implemented and tested. Samples are operational. The design-to-test development flow is not documented.

2.3.4. Loading of Adapters

In previous versions Test Controller Adapters were loaded for each Test execution and unloaded immediately afterwards. This version offers the option of keeping Test Controller Adapters loaded during the execution of a test strategy. This requires the manual editing of an environment variable, as described in Section 4.0 of the Installation Manual. Keeping Test Controller Adapters loaded improves execution performance. If used in conjunction with a similar feature available for LabWindows/CVI DLLs (see Section Error! Reference source not found.), this feature allows the transmission of data between test procedures implemented in the same DLL via static variables.

In previous versions, TED Controller Adapters were kept loaded for the entire TestBase session. In this version, TED Controller Adapters are kept loaded during the execution of a test strategy, being unloaded when the test strategy is finished. This change in behavior does not require the modification of previously developed documents or reports. There is one minor change in the behavior perceived by users: while for previous TestBase versions the Excel reports generated during distinct test strategy executions were created in the same Excel MDI window, now they are created in distinct windows. Reports generated in the same test strategy execution are still created in the same Excel MDI window.

2.3.5. Loading of LabWindows/CVI DLLs

In previous versions LabWindows/CVI DLLs were loaded for each Test execution and unloaded immediately afterwards. This version offers the option of keeping LabWindows/CVI DLLs loaded during the execution of a test strategy. This requires the manual editing of an environment variable, as described in Section 4.0 of the Installation Manual. LabWindows/CVI DLLs loaded improves execution performance. If used in conjunction with a similar feature available for Test Controller Adapters (see Section Error! Reference source not found.), this feature allows the transmission of data between test procedures implemented in the same DLL via static variables.

2.3.6. Specifying paths for test procedure and document/report files

The paths where test procedure files and document/report files are stored in the file system may be specified in specialized environment variables (see Section 4.0 of the Installation Manual). In this case, the file names should be specified without a path in the Test/TED Databases.

This enhancement provides full portability of test procedures and documents/reports from a system to another, without requiring changes in databases. It also simplifies the installation procedure for samples, eliminating the manual configuration of the PATH environment variable and of Excel options.

2.3.7. Persistent storage of paths for "file open" commands

Paths used in "file open" commands are persistently stored between sessions, for both the IDE and production user interfaces. This eliminates the need for directory navigation each time a file is opened.

2.3.8. Persistent storage of child window state in IDE

The maximization state of child windows in the IDE is persistently stored between sessions. The default zoom factor of Control Flow Diagrams was changed from "full page" to 100%.

This eliminates the need for maximizing the window and changing the zoom factor each time a file is opened.

2.3.9. Handling of test procedure errors

The handling of TestBase errors caused by faulty test procedure code was improved. Names and data types of output parameters returned from the test procedure code are compared against the parameter’s definition in the Test Database. If there are differences, an error message is issued and the execution of the test strategy is stopped. The changes have no effect on test procedures and test strategies developed with previous 2.0.x and 2.1.x versions.

The handling of errors in the LabWindows/CVI sample was also improved.

2.3.10. Verification of third-party software

The existence of an operational Microsoft Visio installation is checked by the IDE at startup and a specific error message is displayed. This eliminates the counter-intuitive error message displayed by previous versions.

The existence of a proper version of Microsoft Internet Explorer is checked by the IDE at startup and a specific error message is displayed. This eliminates the counter-intuitive error message displayed by previous versions.

2.3.11. Internationalization

A problem that prevented the use of non-US versions of Visio was fixed. The problem was caused by language-specific property names in the Visio Automation interface.

A problem occurring on non-US Windows NT/2000 versions was fixed. The problem was caused by a different name for the "Program Files" directory.

2.3.12. Samples

Additional samples are provided for the new test environments and document/report formats (see Section 2.3.2).

Samples were renamed and re-organized. Test procedures are installed in environment-specific directories under <TestBase installation directory>\Samples\TPs. Documents and reports are installed in environment-specific directories under <TestBase installation directory>\Samples\Reports. Test strategies using these test procedures and documents/reports are defined in <TestBase installation directory>\Samples\Projects\Sample.tdd.

A set of samples using instruments was added. LabWindows/CVI test procedures are available in <TestBase installation directory>\Samples\TPs\CVI\Demo_CVI. Test strategies using these test procedures are defined in <TestBase installation directory>\Samples\Projects\Demo.tdd.

2.3.13. Documentation

Slides providing a general presentation of the product are available in <TestBase installation directory>\Doc\Presentation.

Tutorial slides on several topics are available in <TestBase installation directory>\Doc\Tutorials.

2.4 Problem Reports

PR 01-129 and PR 01-136: Support the transmission of VISA and instrument driver handles between test procedures.

The required enhancement is provided in the current release - see Sections 2.3.4 and 2.3.5.

PR 01-137 (partial): Simplify the procedure of opening a file in IDE.

A part of the required enhancements are provided in the current release - see Section 2.3.6.