When a test errors out on Adobe CF, the tag stack is not picked up by the "testbox run" command. Likely due to differences in how JSON is serialized.
Attachments
1
Gliffy Diagrams
Activity
Show:
Brad Wood March 30, 2018 at 6:04 PM
An erroring test spec should present like this:
Notice, the full stack trace is NOT present, but the error message as well as the file name and line number of the error are presented to the user which should be enough information to track down the problem without making the output unreadable.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
When a test errors out on Adobe CF, the tag stack is not picked up by the "testbox run" command. Likely due to differences in how JSON is serialized.