View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0009005CTT UA Scripts1 - Script Issuepublic2023-06-13 11:372023-10-13 15:22
ReporterGigantic Heisenberg Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionduplicate 
Summary0009005: testresult mismatch in 1.04.502 current version of CTT
Description

testresult enum differ from the definition given by C:\Program Files (x86)\OPC
Foundation\UA 1.04\Compliance Test Tool\help\project_name.results.xml.htm.
The numerical values should be assigned to the following meanings:

  1. Fail/Error
  2. Warning
  3. Not Implemented
  4. Skipped
  5. Not Supported
  6. OK/Log
  7. Back-trace.

But the implemented assignment is:

  1. Fail/Error
  2. Warning
  3. Not Implemented
  4. Skipped
  5. Not Supported
  6. OK/Log
  7. Back-trace.
Steps To Reproduce
  1. Delete the uaprofiles.xml file and the maintree folder of a newly created ctt project.
  2. Extract the content of testresults.zip, which is attached to this ticket, to the folder of the recently created projects.
  3. execute the following lines in the same folder:
    "C:\Program Files (x86)\OPC Foundation\UA 1.04\Compliance Test Tooll\uacompliancetest.exe"^
    --settings ".\default.ctt.xml"^
    --selection test.selection.xml^
    --result test.results.xml^
    --hidden^
    --close
Additional Information

Issue was not present in version 1.4.500

TagsNo tags attached.
Attached Files
testresults.zip (10,758 bytes)
Files Affected

Relationships

duplicate of 0008730 closedAlexander Allmendinger CTT UA Binary Test log report of UACTT v1.04.11-1.04.502 contains invalid testresult value 

Activities

Alexander Allmendinger

2023-06-16 12:11

developer   ~0019493

With the package version "V1.04.11-01.00.502" there have been script and binary updates. If you check the binaryversion.xml installed with the CTT you'll find a more detailed changelog of the addressed issues and changes. The relevant change here is MantisId 6719, which introduced a new test result in the middle of the enum. For more details please check the related mantis issues.
To indicate potential changes in the results.xml, we extended the information in the XML with the binary used to generate the results. This should allow users of the CTT to identify loading old results in a newer version and indicate potential mismatches.

Regarding the version information not indicating the update in the binaries, could you please indicate where you checked the version information? I just want to make sure we are not missing one spot to update when generating the version infos. Also please let me know whether you are using the Windows version or the AppImage for Linux.

Paul Hunkar

2023-06-16 16:19

administrator   ~0019507

Please answer the question, added by Alex as a comment?

Alexander Allmendinger

2023-10-12 11:36

developer   ~0020146

Thanks for the feedback.
As agreed with the reporter, this issue already has been addressed in newer version and also in the latest September release the help was updated with the information. No further changes are needed.

Paul Hunkar

2023-10-13 15:22

administrator   ~0020172

Agreed it was a duplicate

Issue History

Date Modified Username Field Change
2023-06-13 11:37 Gigantic Heisenberg New Issue
2023-06-13 11:37 Gigantic Heisenberg File Added: testresults.zip
2023-06-16 12:00 Alexander Allmendinger Relationship added duplicate of 0008730
2023-06-16 12:11 Alexander Allmendinger Note Added: 0019493
2023-06-16 16:19 Paul Hunkar Assigned To => Alexander Allmendinger
2023-06-16 16:19 Paul Hunkar Status new => feedback
2023-06-16 16:19 Paul Hunkar Note Added: 0019507
2023-06-19 15:06 Gigantic Heisenberg Status feedback => assigned
2023-10-12 11:36 Alexander Allmendinger Status assigned => resolved
2023-10-12 11:36 Alexander Allmendinger Resolution open => duplicate
2023-10-12 11:36 Alexander Allmendinger Note Added: 0020146
2023-10-13 15:22 Paul Hunkar Status resolved => closed
2023-10-13 15:22 Paul Hunkar Note Added: 0020172