#197 Add UDP packet for "checkpoint message" for QSpy backend to display

[Anonymous]

When the QUTest framework is used to build a large test suite, the Qspy text output (on screen, redirected stdout, or Screen Output to a File in QSPY -- SCREEN_OUT feature) becomes quite lengthy and repetitive. Even though the "target reset" messages serve to separate different tests, it is difficult to find which output block is associated with the particular test being developed or maintained.

If there were a "checkpoint" message added in the "to the QSPY Back-end" group, that carries a string to write to the screen, then the test name could be written at the beginning of processing an individual test, and failing status could be marked in the Qspy output as well. Then the engineer could search the output for these "checkpoint" messages and quickly find the Qspy data surrounding the test expectation failure.

Currently the only way to accomplish this is to re-invent Qspy's logfile logic in the python scripts by writing out every _PKT_TEXT_ECHO payload to a new file, interleaved with the messages coming from the test scripts.

This feature request differs from #118 in that the checkpoint message would not send any data to the target.

[Quantum Leaps]

This feature request has been implemented in QTools 7.2.0.
Specifically, QUTest scripts now send "markers" to the QSPY output.
--MMS

[Anonymous]

Thanks very much! I see this feature in the release notes https://www.state-machine.com/qtools/history.html#qtools_7_2_0 and the new note() function in qutest is documented.

However I can't find the new QSPY_SHOW_NOTE message mentioned in the protocol documentation.
https://www.state-machine.com/qtools/qspy_udp.html#udp_QSPY

[Anonymous]

The documentation has been updated online:
https://www.state-machine.com/qtools/qspy_udp.html#udp_QSPY

--MMS