You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a test script containing an expression (vs. a section document) is evaluated, the entire expression's source code is output. For a long test script, this can add a bit of clutter to the output window.
Example
Test script:
"abc"
Output (only selected properties shown):
[3:51:40 PM] [Info] RunTestBattery result [
{
"Details": "\"abc\"", <------------ full source code output here
"Method": "PQTest.RunTest",
"Type": "PQTest.Expression"
}
]
Desired Solution
Can the full source code not be echoed out?
Alternatives and Workarounds
No response
Additional Context
In contrast, full source code is not output when the test script contains a section document:
Test script:
section Test;
shared A = "abc";
Output (only selected properties shown):
[3:52:03 PM] [Info] RunTestBattery result [
{
"Details": "A", <---------------- just the section member name is output
"Method": "A",
"Type": "PQTest.RunTest"
}
]
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Problem
When a test script containing an expression (vs. a section document) is evaluated, the entire expression's source code is output. For a long test script, this can add a bit of clutter to the output window.
Example
Test script:
Output (only selected properties shown):
Desired Solution
Can the full source code not be echoed out?
Alternatives and Workarounds
No response
Additional Context
In contrast, full source code is not output when the test script contains a section document:
Test script:
Output (only selected properties shown):
The text was updated successfully, but these errors were encountered: