TestStand ATML Toolkit New Features and Changes

Learn about updates—including new features and behavior changes—introduced in each version of TestStand ATML Toolkit.

Discover what's new in the latest releases of TestStand ATML Toolkit.
Note If you cannot find new features and changes for your version, it might not include user-facing updates. However, your version might include non-visible changes such as bug fixes and compatibility updates. For information about non-visible changes, refer to your product Release Notes on ni.com.

ATML Toolkit 2017 New Features

The following list describes the new features in the ATML Toolkit 2017 and other changes since the ATML Toolkit 2013.

  • Compliance with ATML TD 1.01 and 3.0
  • Version-agnostic installation
    • The ATML Toolkit 2017 installer can install with future versions of TestStand. The installer installs files to a separate non-TestStand location, and uses the TestStand Version Selector to copy files to supported versions of TestStand.
    • The ATML Toolkit example files are now located in the <TestStand Public>\Examples\Toolkits\ATMLTDTranslator directory and the language resource files are located in the <TestStand>\Components\Language\English directory.
  • Support for TestStand 64-bit
    • ATML Toolkit 2013 and earlier were only compatible with TestStand 32-bit.
  • Ability to disable automatic code generation
    • Creates steps from an ATML TD file using the None adapter.
    • Supports the custom code generator to generate custom code modules.
  • Improvements for the ATML Test Description Translator Configuration dialog, including support for pointing to a specific schema location.
    • Schema files are located in a separate tab with information about the schema's location and namespace.

ATML Toolkit 2013 New Features

The following list describes the new features in the ATML Toolkit 2013 and other changes since the ATML Toolkit 2012.

  • You can now generate XML reports that validate against the approved version 6.01 of the ATML Test Results and Session Information schema that the ATML standard defines. You can also continue to generate reports that validate against the non-finalized version 5.0 or approved version 2.02 of the schema. Select ATML 6.01 Standards Report Document from the Report Format ring control on the Contents tab of the Report Options dialog box to generate an ATML report that validates against version 6.01 of the schema. TestStand provides the following style sheets, located in the <TestStand>\Components\Models\TestStandModels\ATML\Stylesheets directory, for generating an ATML Test Results 6.01 report. You can customize the style sheets directly.
  • TR6_Expand.xsl—Displays reports similar to TR6_report.xsl, with expandable and collapsible sections for each step or for the entire report.
  • TR6_Horizontal.xls—Displays reports in a horizontal, tabular, indented, format with data for each step in one or more rows.
  • TR6_report.xls—Displays reports in a vertical, tabular, indented format with data for each step in multiple rows. Customizable, color-coded rows visually separate relevant information, such as step group, status, and so on.
  • The ATML Test Results report generator extension DLL can implement the following new functions to modify the content of the ATML TR report.
    • Event_Extension
    • Parameter_Extension
    • TestResults_TestResult_Extension

ATML Toolkit 2012 New Features

The following list describes the new features in the ATML Toolkit 2012 and other changes since the ATML Toolkit 2010.

  • The ATML Test Results (TR) report generator supports the non-finalized version 5.0 of the ATML Test Results and Session Information schema.
  • In addition to using the Locals.Atml_Rpt_Options.ExtDLLAbsPath property in the GetATMLReport sequence of the reportgen_atml.seq sequence file to provide the path of an extension DLL when you generate an ATML TR 2.02 report, you can also now use the Parameters.ReportOptions.Atml_Rpt_Options.ExtensionDLLAbsolutePath property in the ReportOptions callback to complete the same task.
  • You can use the Parameters.ReportOptions.Atml_Rpt_Options.ExtensionDLLAbsolutePath property in the ReportOptions callback to provide the path of an extension DLL when you generate an ATML TR 5.0 report.
  • The ATML Toolkit 2012 includes the following new exported TR report generator extension functions:
    • ResultSet_EnvironmentalData
    • ResultSet_Events_All
    • SessionAction_EnvironmentalData
    • Test_EnvironmentalData
    • TestGroup_EnvironmentalData
    • TestResults_Site
    • TestResults_TestProgram_All
  • The ATML Toolkit 2012 includes the following new TR report generator functions:
    • Get_Atml_ReportBody
    • Get_Atml_ReportFooter
    • Get_Atml_ReportHeader

ATML Toolkit 2012 Compatibility and Known Issues

The ATML Toolkit includes the following behavior changes between version 2010 and version 2012.

Behavior ATML Toolkit 2010 Behavior ATML Toolkit 2012 Behavior
Directory structure of TR schemas <TestStandModels>\ATML\Schemas <TestStandModels>\ATML\Schemas\ATML 2.02 and <TestStandModels>\ATML\Schemas\ATML 5

ATML Toolkit 2010 New Features

The following list describes the new features in the ATML Toolkit 2010 and other changes since the ATML Toolkit 1.0. This list only summarizes each new feature. Refer to the documentation listed for a particular feature for more information about that feature.

  • Enhanced ATML Test Description Translator
    • Translating Limits Associated with Steps Translated from <TestGroupCall> Elements
    • Localization Support
  • Improved Incremental Update Support
  • Instructions for Completing the Test Program
  • Deleting Sequence File and Code Module Constructs
  • New ATML Test Results Report Style Sheet
  • Sequence File Updater Application

Enhanced ATML Test Description Translator

The ATML Test Description (TD) translator now supports translating limits associated with steps translated from <TestGroupCall> elements and localizing error and log messages.

Translating Limits Associated with Steps Translated from <TestGroupCall> Elements

In the case in which a TD instance document contains an <Action> element with a <Behavior> child element that contains a <TestGroupCall> child element, the translator in the ATML Toolkit 2010 uses the <TestLimits> element to determine the appropriate type of step to generate in the translated sequence file. Depending on the content of the <TestLimits> element, the translator generates a Pass/Fail Test, Numeric Limit Test, Multiple Numeric Limit Test, or String Value Test step. The translator in the ATML Toolkit 1.0 always generated a Pass/Fail Test step in this case.

Refer to the Determining Test Steps to Create for <Limit> Elements topic for more information about how the translator determines step types.

Localization Support

The ATML Toolkit 2010 adds support for localizing user interface strings. The following toolkit features contain strings you might want to localize:

  • Dialog box messages when an error occurs during translation or an incremental update
  • Log file entries the translator generates for each translation or incremental update
  • The string labels that display in the ATML Test Description Translator Configuration dialog box and the Update Options dialog box

The ATML Toolkit 2010 includes an ATMLTDString.ini string resource file, located in the <TestStand Public>\Components\Language\English directory. You can modify the strings in the resource file to modify the error or log messages. To support error and log messages for multiple languages, copy the resource file and place it in the required language directory in the <TestStand Public>\Components\Language directory.

Improved Incremental Update Support

The ATML Toolkit 2010 adds support for updating existing LabVIEW or LabWindows/CVI code modules the translator created for a previously translated sequence file.

  • LabVIEW Code Modules—When incrementally updating a previously translated sequence file, the translator determines whether a VI already exists at the path you specify in the LabVIEW VI Path control on the Code Module Settings tab of the ATML Test Description Translator Configuration dialog box. If the VI exists at the path you specified and the VI has a name that is the same as the value of the name attribute of the parent <Action> element, the translator updates in the VI connector pane the existing block diagram labels that correspond to the <AutomaticGeneration>, <Description>, <Extension>, <IeeeStd1641>, and <Operations> child elements of the <Behavior> element. If the VI does not exist, the translator creates a new VI.
  • LabWindows/CVI Code Modules—When incrementally updating a previously translated sequence file, the translator determines whether a function already exists in the C source file at the path you specify in the LabWindows/CVI Source File Path control on the Code Module Settings tab of the ATML Test Description Translator Configuration dialog box. If the source file already exists at the path you specified and the file contains a function with a name that is the same as the value of the name attribute of the parent <Action> element, the translator updates the comments in the function definition that correspond to the <AutomaticGeneration>, <Description>, <Extension>, <IeeeStd1641>, and <Operations> child elements of the <Behavior> element. If the function does not exist, the translator creates a new function in the source file.

The translator also updates block diagram labels or function comments that correspond to the <LocalSignal>, <TestLimit>, <Parameter>, <SessionDatum>, and <TestResult> child elements of the parent <Action> element.

In addition, the ATML Toolkit 2010 adds support for incrementally updating TestStand steps, attributes, and variables created from the child elements of a <TestGroup> element of the TestGroupParallel type.

Instructions for Completing the Test Program

The translator cannot translate all elements in a source TD instance document to TestStand constructs, such as steps, sequences, or code modules. The translator stores these elements in TestStand variables, attributes, or comments, but the generated sequence file does not use the variables, attributes, or comments.

The ATML Toolkit 2010 translation log file lists the elements the translator translated but cannot implement and describes how you must implement the required functionality to complete the test program. The log file uses subsections for the sequences and steps that contain the information you must implement. The translator generates the log file in the same directory that it generates the translated sequence file.

Deleting Sequence File and Code Module Constructs

The General Settings tab of the ATML Test Description Translator Configuration dialog box now includes a Delete Previously Generated Sequence File and Code Module Constructs option, which is enabled by default.

When you enable this option, the translator deletes TestStand steps, sequences, and local variables and block diagram labels in LabVIEW code modules or function comments in LabWindows/CVI code modules created during the previous translation. The translator deletes these items when incrementally updating a sequence file if you have deleted the corresponding elements from the source TD instance document.

When you disable this option, the translator retains TestStand steps, sequences, and local variables and block diagram labels in LabVIEW code modules or function comments in LabWindows/CVI code modules when incrementally updating a sequence file, even if you have deleted the corresponding elements from the source TD instance document. The translator deletes in the retained TestStand constructs the attributes previously created for the attributes of translated elements in the source TD instance document. For comments in retained code modules, the translator deletes from the comments the <ATMLTranslatorComment> and </ATMLTranslatorComment> tags previously created for some elements in the source TD instance document.

New ATML Test Results Report Style Sheet

The ATML Toolkit 2010 includes a new ATML Test Results report style sheet, TR_horizontal.xsl, located in the <TestStand>\Components\Models\TestStandModels\ATML\StyleSheets directory. The style sheet displays an ATML Test Results report in a concise tabular format with expand and collapse sections.

Select Configure»Report Options to launch the Report Options dialog box. Click the Contents tab, select ATML Report Document from the Report Format ring control, and select TR_horizontal.xsl from the Stylesheet ring control to select the new style sheet when you generate an ATML Test Results report.

Sequence File Updater Application

The ATML Toolkit 2010 changes the prefixes of the types contained in the ATMLTDTypes.ini and ATMLTD_IEEE1641_Types.ini type palette files and also renames the Attributes subproperty of the types as ATMLAttributes. As a result of these naming changes, the ATML Toolkit 2010 does not correctly incrementally update sequence files you originally translated using the ATML Toolkit 1.0. Refer to ATML Toolkit 2010 Compatibility and Known Issues for more information about these naming changes.

You can use the Sequence File Updater application to convert sequence files you originally translated using the ATML Toolkit 1.0 to a sequence file you can use for an incremental update using the ATML Toolkit 2010. Complete the following steps to install and launch the Sequence File Updater application.

  1. Copy the ATMLSequenceFileConverter directory from the ATML Toolkit installer directory, located on the ATML Toolkit 2010 media, to a directory on the computer.
  2. Double-click SequenceFileConverter.exe, located in the ATMLSequenceFileConverter directory, to launch the Update Sequence Files Translated with the ATML Toolkit 1.0 dialog box.
  3. Use the Path of Sequence File to be Updated control to specify the path of the sequence file translated using the ATML Toolkit 1.0.
  4. Optionally, use the Path of Test Description File (Optional) control to specify the path of the source TD instance document used to generate the sequence file, if the source TD instance document is available.
  5. Click OK to update the sequence file for the ATML Toolkit 2010.

ATML Toolkit 2010 Compatibility and Known Issues

The ATML Toolkit includes the following behavior changes between version 1.0 and version 2010. Refer to the list of ATML Toolkit 2010 Known Issues on the manufacturer's web site for a list of known issues in the ATML Toolkit 2010. You can also view this list by date.

Behavior ATML Toolkit 1.0 Behavior ATML Toolkit 2010 Behavior
When translating the <Datum> child element of a <Parameter> element. The translator translates the parent <Action> element as a TestStand step, the <Parameter> element as a parameter of the step, and the <Datum> element as a local variable of the sequence that contains the step created for the <Action> element. The value expression for the parameter contains the lookup string for the local variable created for the <Datum> element. The translator translates the parent <Action> element as a TestStand step and the <Parameter> element as a parameter of the step but no longer creates a local variable when translating <Datum> elements of the following types:
  • binary
  • boolean
  • double
  • hexadecimal
  • integer
  • octal
  • string
  • unsigned integer
Instead, the value expression for the parameter contains the value of the <Parameter> element.
When translating the <EntryPoints>/<ActionEntryPoints> element. The translator completes the following steps to translate the <ActionEntryPoints> element.
  1. Identifies the <Action> element that the actionID attribute of the first <ActionEntryPoints>/<ActionEntryPoint> element references.
  2. Identifies the sequence that corresponds to the first <TestGroup> element that contains a reference to the <Action> element identified in step 1.
  3. Inserts a Goto step in the Setup step group of the sequence identified in step 2.
  4. Specifies that the destination step for the Goto step is the step that corresponds to the <Action> element identified in step 1.
  5. Translates the <EntryPoints> parent element as a Sequence Call step and inserts the step into the MainSequence.
 The translator completes the following additional steps to add new functionality when translating the <ActionEntryPoints> element.
  1. Adds a Boolean parameter to the sequence that contains the Goto step.
  2. Specifies the value of the parameter as False.
  3. Specifies that the lookup string of the parameter is the precondition of the Goto step.
  4. Specifies that the Sequence Call step the translator created for the <EntryPoints> parent element passes a value of True for the Boolean parameter created in step 1.
As a result, other Sequence Call steps that call the sequence in which the Goto step exists pass a default value of False for the Boolean parameter, and the Goto step executes only once.
When translating the <EntryPoints> child element of a <TestGroup> element of the TestGroupSequence type. The translator creates an EntryPoints container local variable in the translated sequence and translates individual <EntryPoint> elements as child containers of the EntryPoints container. The translator also stores all attributes of an <EntryPoint> element under an Attributes container local variable. You must specify that the first step in the translated sequence is the primary entry point because the translator does not support any other option. For an EntryPoint element with an ID attribute value that matches the value of the primaryEntryPointID attribute of the parent <EntryPoints> element, the translator inserts a Goto step as the first step of the Main step group in the translated sequence. The destination for the Goto step is the step the translator creates for a <Step> element with an ID attribute value that is the same as the value of the stepID attribute of the <EntryPoint> element.
The ATMLTDTypes.ini type palette file, located in the <TestStand Public>\Components\TypePalettes directory, contains data types from the TestDescription.xsd, Common.xsd, and HardwareCommon.xsd ATML TD schema files. The ATMLTD_IEEE1641_Types.ini type palette file, located in the same directory, contains data types from the STDTSF.xsd, STDBSC.xsd, and STDTSFLib.xsd IEEE Std 1641 standard schema files. The types defined in both type palette files include an ATML prefix on the type names. The translator translates attributes defined in the ATML and IEEE 1641 schemas as a subproperty, named Attributes, in the types defined in TestStand. The translator translates XML elements and attributes with the name Value as a local variable, named ATML_Value, in the translated sequence. The types defined in the ATMLTDTypes.ini type palette file include an NI_ATML prefix on the type names. The types defined in the ATMLTD_IEEE1641_Types.ini type palette file include an NI_ATMLSTD prefix on the type names. The translator translates attributes defined in the ATML and IEEE 1641 schemas as a subproperty, named ATMLAttributes, in the types defined in TestStand. The translator translates XML elements and attributes with the name Value as a local variable, named NI_ATMLValue, in the translated sequence.
Note The ATML Toolkit 2010 does not correctly incrementally update sequence files you originally translated using the ATML Toolkit 1.0. The ATML Toolkit 2010 includes a Sequence File Updater application to convert sequence files you originally translated using the ATML Toolkit 1.0.

ATML Toolkit 2010 Bug Fixes

The following items are changes from the ATML Toolkit 1.0 to the ATML Toolkit 2010, unless otherwise specified.

Use this Toggle Expansion button to expand or collapse the following sections. You must enable the Allow Blocked Content option in Microsoft Internet Explorer to collapse each section. You must expand each section you want to print or search.
 General
ID Fixed Issue Issue Details
215986 Including the ATML Test Results report generator in a TestStand deployment installs the report generator to both TestStand 4.1.1 and TestStand 4.2 directories If you install the ATML Test Results report generator component of the TestStand ATML Toolkit 1.0 for both TestStand 4.1.1 and TestStand 4.2, build a deployment, and run the deployment installer on a different computer, the installer installs the ATML Test Results report generator component in both the TestStand 4.1.1 and TestStand 4.2 directories, even if one of those versions of TestStand does not exist on the computer.
255867 The ATML Toolkit is not compatible with TestStand 2010 TestStand 2010 introduces a restriction that prevents the translator from creating a subproperty named Attributes when the property also contains attributes. If the translator in the ATML Toolkit 1.0 encounters this restriction, the translator returns an error during translation.
 Installation
ID Fixed Issue Issue Details
188737 The ATML Toolkit 1.0 uninstaller does not remove the ATMLTD_IEEE1641_Types.ini type file from the <TestStand Public>\Components\TypePalettes directory If you enable the Use IEEE 1641 Data Types in TestStand option on the General Settings tab of the ATML Test Description Translator Configuration dialog box, the translator adds the ATMLTD_IEEE1641_Types.ini file to the <TestStand Public>\Components\TypePalettes directory. Uninstalling the ATML Toolkit does not remove the ATMLTD_IEEE1641_Types.ini type file from the <TestStand Public>\Components\TypePalettes directory.
201735 The toolkit installs the TestStand ATML Toolkit Help in the default <TestStand>\Doc\Help directory when TestStand is not installed in the default installation directory The toolkit installs the TestStand ATML Toolkit Help in the default <TestStand>\Doc\Help directory when TestStand is not installed in the default installation directory.
218266 The ATML Toolkit autorun.exe dialog box does not display correctly The ATML Toolkit autorun.exe dialog box might not display correctly if you make a different window active after you launch the autorun.exe but before the autorun.exe dialog box displays.
245573 Reinstalling the ATML Toolkit creates duplicate Configure ATML TD Translator menu items in the Tools menu If you repair the existing ATML Toolkit installation or uninstall and then reinstall the toolkit, the TestStand Tools menu includes a duplicate entry for the Configure ATML TD Translator menu item for each time you repaired or installed the toolkit.
 Test Description Translator
ID Fixed Issue Issue Details
183549 The translator does not recognize the installation of LabVIEW 2009 (64-bit) The translator runs as a Windows 32-bit On Windows 64-bit (WoW64) process on 64-bit operating systems, which causes registry queries from the translator to be redirected to the Wow6432Node registry node and prevents the translator from recognizing the installation of 64-bit versions of LabVIEW in the 64-bit registry.
186711 Limit values for a custom step type that is similar to Numeric Limit Test, Multiple Numeric Limit Test, or String Value Test step types do not update during an incremental update If the translator uses the customType attribute of an <Action> element to specify a custom step type and the custom step type definition is similar to the definition of the Numeric Limit Test, Multiple Numeric Limit Test, or String Value Test step types, the translator does not update the limit values of the step during an incremental update.
186913 The ATML Test Description Translator Configuration dialog box takes longer to load when the computer is connected to a network but not connected to the internet The ATML Test Description Translator Configuration dialog box DLL contains a Microsoft Authenticode signature that causes the dialog box to take longer to load when the computer is connected to a network but not connected to the Internet. Refer to the Microsoft KnowledgeBase article 936707, located at support.microsoft.com/kb/936707, for more information about how Authenticode signatures affect application load times.
198055 Incremental update skips any <TestGroup> element of the TestGroupParallel type The translator does not incrementally update a TestStand sequence the translator previously created for a <TestGroup> element of the TestGroupParallel type.
201786 The translator does not enable additional results for parameters of Sequence Call steps the translator creates for <Action> elements The translator does not enable additional results for parameters of Sequence Call steps the translator creates for <Action> elements.
208443 The translator does not properly incrementally update <TestGroup> elements If you remove a <TestGroup> element from a previously translated TD instance document, the translator does not properly remove the sequence the translator previously created for the <TestGroup> element during an incremental update. If you change the name of a <TestGroup> element in a previously translated TD instance document, translator does not properly update the name of the sequence the translator previously created for the <TestGroup> element during an incremental update. If two Sequence Call steps call into the same sequence, and during an incremental update the translator changes one of the Sequence Call steps to no longer call into the sequence, the translator incorrectly deletes the sequence from the sequence file even though a Sequence Call step that calls into the sequence still exists.
209833 The translator does not use the <NominalValue> child elements of <TestResult> elements to specify the default values for VI indicators If an <Action> element contains <TestResult> elements, the translator uses the <TestResult> elements to store the output parameters of the <Action> element. If the LabVIEW code module the translator creates for such an <Action> element does not actually wire data to one of these output parameters, the indicator should default to the value that the <NominalValue> child element of the respective <TestResult> element specifies. When generating LabVIEW VIs, the translator does not specify the default values of indicators to match the values that the <NominalValue> elements of the respective <TestResult> elements specify.
219534 The translator does not properly recognize year-based versions of LabVIEW and LabWindows/CVI The translator incorrectly evaluates year-based versions of LabVIEW and LabWindows/CVI as versions earlier than LabVIEW 8.2.1 and LabWindows/CVI 8.1.1.
234677 The translator incorrectly populates parameter values for a Sequence Call step that calls a sequence created for a <Step> element that exists under a <TestGroup> element of the TestGroupParallel type The translator incorrectly populates parameter values for a Sequence Call step that calls a sequence created for a <Step> element that exists under a <TestGroup> element of the TestGroupParallel type and references an <Action> element that contains a <Behavior>/<TestGroupCall> child element.
234678 The translator hangs when you execute it in a LabVIEW-built user interface The translator hangs when you execute it in a TestStand User Interface built with LabVIEW.
243363 The translator does not update the data source for Multiple Numeric Limit Test steps when the number of parameters exceeds the number of limits The translator does not update the data source for Multiple Numeric Limit Test steps when the number of parameters exceeds the number of limits.
286139 The translator incorrectly skips some custom code generator callbacks during an incremental update When performing an incremental update, the translator skips the TranslateTestGroup custom code generator callback for <TestGroup> elements and the PreTranslateStep and PostTranslateStep custom code generator callbacks for <Step> and <ActionReference> elements.
289410 The translator incorrectly specifies the Load Option and Step Failure Causes Sequence Failure run options for a step translated from an <ActionReference> element The translator incorrectly specifies the Load Option and Step Failure Causes Sequence Failure run options for a step the translator creates for an <ActionReference> child element of a <TestGroup> element of the TestGroupParallel, TestGroupDiagnosticModel, TestGroupSerial, or TestGroupUnspecifiedOrder type. The translator incorrectly specifies Load dynamically for the Load Option run option and True for the Step Failure Causes Sequence Failure run option when the translator should specify Preload when execution begins and False, respectively.
294302 The translator returns the error 'Item is locked, protected, or in use and cannot be deleted.' when you use the example custom code generator VIs The translator returns the error 'Item is locked, protected, or in use and cannot be deleted.' when you configure the translator to use the LabVIEW custom code generator VIs, located in the <TestStand Public>\Components\Translators\ATMLTDTranslator\Examples\Code Generator\LabVIEW directory.
297288 The translator does not properly call the LabVIEWParameter.UpdateClusterMapping method for container parameters of LabVIEW steps created for <ActionReference> child elements of <TestGroup> elements of the TestGroupParallel type The translator does not properly call the LabVIEWParameter.UpdateClusterMapping method for container parameters of LabVIEW steps created for <ActionReference> child elements of <TestGroup> elements of the TestGroupParallel type.
98211 The translator hangs if you close the LabWindows/CVI environment during translation Closing the LabWindows/CVI environment while the translator is generating LabWindows/CVI code modules causes the translator to hang.
 Test Results Generator
ID Fixed Issue Issue Details
165526 The ATML Test Results report generator does not correctly process the Default Numeric Format setting The ATML Test Results report generator does not correctly process the setting you specify in the Default Numeric Format control on the Contents tab of the Report Options dialog box. When you select ATML Report Document from the Report Format ring control on the Contents tab of the Report Options dialog box, the Default Numeric Format control and Edit Format button are disabled.
209830 The ATML Test Results report generator does not process and include descriptions for Sequence Call steps in the ATML report The ATML Test Results report generator does not process and include descriptions for Sequence Call steps in the ATML report.
220888 The ATML Test Results report generator does not process and include the results of step post actions in the ATML report The ATML Test Results report generator does not process and include the results of step post actions in the ATML report.
221937 The ATML Test Results report generator omits Sequence Call step names from the ATML report The ATML Test Results report generator omits Sequence Call step names from the ATML report and instead uses the generic name TestGroup to record Sequence Call steps.
228564 The ATML Test Results report generator does not include <Event>, <Data>, or <Description> elements under <TestGroup> elements in the ATML report The ATML Test Results report generator does not include <Event>, <Data>, or <Description> elements under <TestGroup> elements in the ATML report.
231930 The ATML Test Results report generator does not include additional results when you enable the Is Limit option but do not enable the Is Measurement option If you configure an additional result for a step and enable the Include in Report option, the generated ATML Test Results report displays the additional result. However, if you also enable the Is Limit option but do not enable the Is Measurement option, the report does not display the additional result. The report does correctly display the additional result if you enable the Include in Report and Is Measurement options but you do not enable the Is Limit option.