Hi Zhiqiang,
On 07/08/2014 03:11 AM, Zhang, Zhiqiang wrote:
Hi Corentin & Zheng,
Many thanks for testing Bluetooth TCT tests during your implementation
of NTB.
> Sorry I can not perform and fix TCT issues on my side because I'm
focalized on making NTB compliant with Tizen Common (using
notification-service)...
What do you mean TCT issues here? Test case issue or testing
environment issue? Or the TCT timeout results of NTB (which sounds an
implementation issue)?
So far as I know, tct-bluetooth-tizen-tests got all tests pass on
Tizen 2.2.1 image.
TCT issues here mean actually issue in tizen-extensions-crosswalk (and
maybe in NTB) caused by TCT tests.
I'm aware that all of the TCT bluetooth tests are not OK right now but
I'm working on Tizen:Common NTB plugin in priority.
Actually, if you find a TCT test script issue, a pull request against
https://github.com/crosswalk-project/crosswalk-test-suite/tree/master/webapi/tct-bluetooth-tizen-tests
is more than welcome, since you are working on NTB in
tizen-extensions-crosswalk; and I can help push the sound changes to
Tizen Web TCT then.
Thanks for this information. I won't hesitate to contact you in case of
doubt.
Thanks,
Zhiqiang
*From:*Dev [mailto:[email protected]] *On Behalf Of
*[email protected]
*Sent:* Friday, July 4, 2014 11:40 PM
*To:* Zheng, Wu
*Cc:* [email protected]; Jia, Pei P; Gu, Chao Jie
*Subject:* Re: [Dev] [NTB] TCT testing bug
Hi Zheng Wu,
You're right ! I've sent a fix about
setChangeListener/unsetChangeListener API.
You can find the patch here:
https://github.com/eurogiciel-oss/tizen-extensions-crosswalk/commit/0539f4536750bc3f9904df6e5ba207a9e4321105
Btw, I saw there are many blocked timeout issues.
Sorry I can not perform and fix TCT issues on my side because I'm
focalized on making NTB compliant with Tizen Common (using
notification-service)...
Best regards,
Corentin
On 07/04/2014 12:23 PM, Zheng, Wu wrote:
HiCorentin,
1. We are testing Bluetooth TCT cases. We meet many blocked timeout issues.
The following issue has been checked by us.
2. In the test case of BluetoothAdapterChangeCallback_onnameChanged.html,
we found thatadapter.setChangeListener is registered.
After 180000ns, if the cases can't getSetName successfully info from the
listener ofadapter.setChangeListener,
It will be blocked timeout.
adapter.setChangeListener is implemented by bluetooth_instance_bluez5.cc
in tizen-extensions-crosswalk.
No any Bluetooth CAPIs is invoked in the listener process.
Can you check why the test case can't get the info from listener? Thanks.
It blocked many testcaases.
Best Regards
Zheng Wu
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
