Closed Bug 1161889 Opened 9 years ago Closed 9 years ago

[Bluetooth][PTS][2.2][L][FC] TC_AG_OAC_BV_01_I failed

Categories

(Firefox OS Graveyard :: Bluetooth, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: twen, Assigned: jaliu)

References

Details

Attachments

(1 file)

##STR
Test case : TC_AG_OAC_BV_01_I started
	- SDP Service record for PTS: 'Headset HS' successfully registered
	- MTC: Creating and closing a service level connection with the IUT in order to create a pairing
	- MTC: TS_spp_disable_tester: SPP already disabled
	- Using SDP to determine IUT RFCOMM server channel number.
	- ProtocolDescriptorList: IUT reports that its RFCOMM server channel number is 2
	- ProfileDescriptorList: Headset Profile version retrieved successfully
	- AT: SPP connect succeeded
	- AT: SPP connection enabled
	- AT: Service Level Connection disabled
	- AT: SPP connect succeeded
	- AT: SPP connection enabled
	- MTC: SPP Connection established from IUT
	- FATAL ERROR (AT): unexpected OK received
	- MTC received unexpected EXIT message from AT component
	- HCI: Audio Connection enabled
	- HCI: Audio Connection disabled
	- AT: Service Level Connection disabled
	- MTC: Test case ended
Final Verdict:INCONC
TC_AG_OAC_BV_01_I finished

## Version
Build Number: 20150428041949
Blocks: 1159612
Summary: [Bluetooth][PTS][2.2] TC_AG_OAC_BV_01_I failed → [Bluetooth][PTS][2.2][L][FC] TC_AG_OAC_BV_01_I failed
#Updated Build Version
Gaia-Rev        9f6b1b9082662ba2c14168fc66bb02b4df3141e5
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/e79c19bf19bf
Build-ID        20150428002500
Version         37.0
Device-Name     hammerhead
FW-Release      5.1
FW-Incremental  eng.cltbld.20150428.041949
FW-Date         Tue Apr 28 04:20:07 EDT 2015
Bootloader      HHZ12d
Jamin will take a look.
Assignee: nobody → jaliu
See Also: → 1142390
I ran this test case with pvt build nexus-5-L_v2.2 and the verdict is PASS.

> Test case : TC_AG_OAC_BV_01_I started
>     - SDP Service record for PTS: 'Headset HS' successfully registered
>     - MTC: Creating and closing a service level connection with the IUT in order to create a pairing
>     - MTC: TS_spp_disable_tester: SPP already disabled
>     - Using SDP to determine IUT RFCOMM server channel number.
>     - ProtocolDescriptorList: IUT reports that its RFCOMM server channel number is 2
>     - ProfileDescriptorList: Headset Profile version retrieved successfully
>     - AT: SPP connect succeeded
>     - AT: SPP connection enabled
>     - AT: Service Level Connection disabled
>     - AT: SPP connect succeeded
>     - AT: SPP connection enabled
>     - MTC: SPP Connection established from IUT
>     - HCI: Audio Connection enabled
>     - HCI: Audio Connection disabled
>     - MTC: Audio Connection disabled by IUT
>     - AT: Service Level Connection disabled
>     - MTC: Test case ended
>     -Final Verdict: PASS
> TC_AG_OAC_BV_01_I finished

I noticed the PTS instruction [1] of the 2nd step can be quite confusing and unclear.
[1] "If the IUT is an Audio Gateway (AG), a call may need to be active."

If I understand it correctly, the tester should put an *outgoing* call first, then click the 'OK' button. 
P.S. The call must remain active during the test.

By following this procedure, the test will be passed without any problem.
The expected HSP message sequence should like be this ...

      AT+CKPD=200
AG  <-------------  HS  
           OK  
AG  ------------->  HS   

However, if the tester put a *incoming* call to the IUT, the test will be terminated immediately.
As far as I know, PTS don't expected to receive the AT command 'RING' in this test case.

       RING (incoming Call)  --> [Unexpected AT command]
AG  ------------->  HS

According to the Bluetooth HSP spec. 4.2.2, it should send 'RING' commands when IUT receives an incoming call. It should not be treated as an illegal behavior.

One tricky thing here is that the PTS instruction doesn't ask user to put an incoming call to IUT during that the test. 

It seems a bit confusing to the tester.
Personally, I don't think it's a bug of FxOS.

Hi Teri,
Thank you for reporting this issue.
Would you mind to test it again and make an *outgoing* call in step 2 ?

Thank you.
Flags: needinfo?(twen)
Thanks Jamin, after following your instructions, the test is now passed.
Close this as worksforme.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(twen)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: