JUnit Conversion: Fix empty message for errors without tags

When the assertion fails due to an error without <err> or <append> tags, the reported error message is empty. Fixed by reporting the entire error source string when no tag could be found. In this case, the stack trace is empty and the type is reported as "Unknown".
logmanoriginal · Apr 19, 2024 · 72b69d9 · 72b69d9
1 parent efe7d95
commit 72b69d9
Show file tree

Hide file tree

Showing 5 changed files with 36 additions and 32 deletions.
diff --git a/JUnit Conversion/Get Error Details from Error Cluster.vi b/JUnit Conversion/Get Error Details from Error Cluster.vi
diff --git a/...sts/Convert Assert Event Data to Test Case - Error (no tags) - Message is Error Source.vi b/...sts/Convert Assert Event Data to Test Case - Error (no tags) - Message is Error Source.vi
diff --git a/... Tests/Convert Assert Event Data to Test Case - Error (no tags) - Stack Trace is empty.vi b/... Tests/Convert Assert Event Data to Test Case - Error (no tags) - Stack Trace is empty.vi
diff --git a/...rsion Tests/Convert Assert Event Data to Test Case - Error (no tags) - Type is Unknown.vi b/...rsion Tests/Convert Assert Event Data to Test Case - Error (no tags) - Type is Unknown.vi
diff --git a/Tests/JUnit Conversion Tests/JUnit Conversion Tests.lvlib b/Tests/JUnit Conversion Tests/JUnit Conversion Tests.lvlib