It seems like PTS can do the testing automatically with the DUT, a dongle from BTSIG (https://bluetoothstore.org/) and the right test description from Launch Studio (https://www.bluetooth.com/develop-with-bluetooth/test-tools/profile-tuning-suite). If anyone self qualified the BlueZ host on a product using this method, could she/he please share the steps and experiences? How does one work out what elements of the BT standards are required in the product? (to know what to include in the ICS) Is it sufficient to say: "We want to be a Central device that connects to Peripherals, and interprets GATT commands" and based on that select "Central" and "GATT" in the Launch Studio project, and fix all conflicts/dependencies in the ICS generation step? Be Well, Alan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
