bluedroid stack: Pair/Scan/Set name/Discoverable etc basic feature

All blocking bugs have been resolved. Close as resolved fixed. Thanks for everyone, especially Shawn. :)

Hi, I will be creating test cases (if needed). For bluedroid, we'd like to test on PTS. Can you create one PTS profile for bluedroid GAP and create another PTS profile for bluez GAP? (Or, will the profile be the same?) We need to verify if the behavior would be the same in bluez and bluedroid.

(In reply to Walter Chen[:ypwalter][:wachen] from comment #2) > Hi, I will be creating test cases (if needed). > For bluedroid, we'd like to test on PTS. > Can you create one PTS profile for bluedroid GAP and create another PTS > profile for bluez GAP? (Or, will the profile be the same?) We need to verify > if the behavior would be the same in bluez and bluedroid. Sure we will, but as we discussed before, I think 'aurora' is the best branch for PTS testing since it's more stable and at least feature complete. Therefore I would say that we should start testing from your test cases.

Ok then, we will run PTS whenever it goes to aurora and only doing some test cases modification and UI testing as for now.

Basic testing is done. https://bugzilla.mozilla.org/show_bug.cgi?id=937973 This bug opens accordingly. And the verification pends on bug 937973 now. Also, for test cases now: 8576,8578,8569,6935 modified 8569,6935,3518,3575,3520,3523,2479,1397 tagged 6751-6754 name modified Related test cases are marked as "gap" tag, and you should be able to find test cases by "gap" tag in moztrap. I will do the test cases creation soon.

Cases for v1.2 also tagged accordingly to the list above for reference.

Just merged original bluetooth settings test cases from "Settings" suite. Trying to modify the bad test cases created by others and reduce the duplicated tests cases. We will clean the test cases a little bit more to make sure that QAnalyst can do their job for us. Test cases 10746&10747 added

It's done testing