Bluetooth Special Interest Group Inc. BTSIG15A Manual De Usuario
Logging
131
As mentioned in
Executing a single test case
, changes to the log level may never be needed. The “Run (Debug Logs)”
features is a much better way to produce highly detailed logs for problem analysis or archival purposes.
The “Logging” page allows for the selection of one of two preset collections of events, or for a completely custom selection
of the events of interest.
of the events of interest.
•
The “Standard” preset adds “Send event” and “Receive event” to the “Minimal” setting, along with other events
(such as “Preliminary verdict”) that can be used to determine the final verdict of the test case.
(such as “Preliminary verdict”) that can be used to determine the final verdict of the test case.
•
“Full” causes highly detailed information about the inner workings of a test case to be included in the execution
log. This is a lot of information and may be overwhelming to most users.
log. This is a lot of information and may be overwhelming to most users.
Members of the PTS Technical Support or Development Teams may ask for “Full” logging when a problem occurs with a
test case. The highly detailed execution log, combined with the low level communications trace produced by the PTS
Protocol Viewer can be invaluable in attempting to determine why a test case is behaving in a certain way.
test case. The highly detailed execution log, combined with the low level communications trace produced by the PTS
Protocol Viewer can be invaluable in attempting to determine why a test case is behaving in a certain way.
As mentioned in
Introduction
, Bluetooth Low Energy test suites have a much smaller number of events that can be logged
when compared to BR/EDR test suites. In fact, for the LE test suites, there is no difference between “Standard” and “Full”.