Linux bluetooth development
 help / color / mirror / Atom feed
* [PATCH] android/pts: RFCOMM PTS 5.3 update
@ 2014-10-09 15:15 Sebastian Chlad
  2014-10-10  8:36 ` Szymon Janc
  0 siblings, 1 reply; 2+ messages in thread
From: Sebastian Chlad @ 2014-10-09 15:15 UTC (permalink / raw)
  To: linux-bluetooth; +Cc: Sebastian Chlad

PTS tests results for RFCOMM on PTS 5.3.
PICS' and PIXITs checked against PTS 5.3.
---
 android/pics-rfcomm.txt  |  2 +-
 android/pixit-rfcomm.txt |  2 +-
 android/pts-rfcomm.txt   | 22 ++++++++--------------
 3 files changed, 10 insertions(+), 16 deletions(-)

diff --git a/android/pics-rfcomm.txt b/android/pics-rfcomm.txt
index 9dfb32e..c970363 100644
--- a/android/pics-rfcomm.txt
+++ b/android/pics-rfcomm.txt
@@ -1,6 +1,6 @@
 RFCOMM PICS for the PTS tool.
 
-PTS version: 5.2
+PTS version: 5.3
 
 * - different than PTS defaults
 # - not yet implemented/supported
diff --git a/android/pixit-rfcomm.txt b/android/pixit-rfcomm.txt
index 07810d2..187f3b4 100644
--- a/android/pixit-rfcomm.txt
+++ b/android/pixit-rfcomm.txt
@@ -1,6 +1,6 @@
 RFCOMM PIXIT for the PTS tool.
 
-PTS version: 5.2
+PTS version: 5.3
 
 * - different than PTS defaults
 & - should be set to IUT Bluetooth address
diff --git a/android/pts-rfcomm.txt b/android/pts-rfcomm.txt
index 9bfc7a2..d869ee0 100644
--- a/android/pts-rfcomm.txt
+++ b/android/pts-rfcomm.txt
@@ -1,7 +1,7 @@
 PTS test results for RFCOMM
 
-PTS version: 5.2
-Tested: 17-July-2014
+PTS version: 5.3
+Tested: 08-October-2014
 Android version: 4.4.4
 
 Results:
@@ -17,29 +17,23 @@ Test Name		Result	Notes
 TC_RFC_BV_01_C		PASS	rctest -n -P 1 <btaddr>
 TC_RFC_BV_02_C		PASS	rctest -r -P 1
 TC_RFC_BV_03_C		PASS	rctest -r -P 1
-TC_RFC_BV_04_C		FAIL	PTS issue #12421
-				PTS issue #12414
-				NOTE: DISC on DLC is expected; IUT disconnects
-					rfcomm session (close)
+TC_RFC_BV_04_C		PASS	NOTE: use ets provided in PTS issue #12414
 TC_RFC_BV_05_C		PASS	rctest -n -P 4 <btaddr>
 				Note: test requires IUT to connect on the given
 				channel. sdptool browse <btaddr> to check the
 				channel.
 TC_RFC_BV_06_C		PASS	rctest -r -P 1
 TC_RFC_BV_07_C		PASS	rctest -r -P 1
-TC_RFC_BV_08_C		INC	PTS issue #12397
-				NOTE: Incorrect frame type sent in response to
-					the DISC command
+TC_RFC_BV_08_C		PASS	rctest -r -P 1
+				Note: use ets provided in PTS issue #12397
 TC_RFC_BV_11_C		PASS	rctest -r -P 1
-TC_RFC_BV_13_C		FAIL	PTS issue #12397
-				NOTE: IUT sent the correct frame type (UIH)
-				but the parameters did not match the
-				requirements
+TC_RFC_BV_13_C		PASS	rctest -r -P 1
+				Note: use ets provided in PTS issue #12397
 TC_RFC_BV_14_C		N/A
 TC_RFC_BV_15_C		PASS	rctest -r -P 1
 TC_RFC_BV_17_C		PASS	rctest -d -P 1
 TC_RFC_BV_19_C		PASS
 TC_RFC_BV_21_C		INC	PTS issue #12421
 TC_RFC_BV_22_C		INC	PTS issue #12421
-TC_RFC_BV_25_C		INC	PTS issue #12421
+TC_RFC_BV_25_C		INC	PTS issue #12621
 -------------------------------------------------------------------------------
-- 
1.8.5.3


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] android/pts: RFCOMM PTS 5.3 update
  2014-10-09 15:15 [PATCH] android/pts: RFCOMM PTS 5.3 update Sebastian Chlad
@ 2014-10-10  8:36 ` Szymon Janc
  0 siblings, 0 replies; 2+ messages in thread
From: Szymon Janc @ 2014-10-10  8:36 UTC (permalink / raw)
  To: Sebastian Chlad; +Cc: linux-bluetooth

Hi Sebastian,

On Thursday 09 of October 2014 17:15:44 Sebastian Chlad wrote:
> PTS tests results for RFCOMM on PTS 5.3.
> PICS' and PIXITs checked against PTS 5.3.
> ---
>  android/pics-rfcomm.txt  |  2 +-
>  android/pixit-rfcomm.txt |  2 +-
>  android/pts-rfcomm.txt   | 22 ++++++++--------------
>  3 files changed, 10 insertions(+), 16 deletions(-)
> 
> diff --git a/android/pics-rfcomm.txt b/android/pics-rfcomm.txt
> index 9dfb32e..c970363 100644
> --- a/android/pics-rfcomm.txt
> +++ b/android/pics-rfcomm.txt
> @@ -1,6 +1,6 @@
>  RFCOMM PICS for the PTS tool.
>  
> -PTS version: 5.2
> +PTS version: 5.3
>  
>  * - different than PTS defaults
>  # - not yet implemented/supported
> diff --git a/android/pixit-rfcomm.txt b/android/pixit-rfcomm.txt
> index 07810d2..187f3b4 100644
> --- a/android/pixit-rfcomm.txt
> +++ b/android/pixit-rfcomm.txt
> @@ -1,6 +1,6 @@
>  RFCOMM PIXIT for the PTS tool.
>  
> -PTS version: 5.2
> +PTS version: 5.3
>  
>  * - different than PTS defaults
>  & - should be set to IUT Bluetooth address
> diff --git a/android/pts-rfcomm.txt b/android/pts-rfcomm.txt
> index 9bfc7a2..d869ee0 100644
> --- a/android/pts-rfcomm.txt
> +++ b/android/pts-rfcomm.txt
> @@ -1,7 +1,7 @@
>  PTS test results for RFCOMM
>  
> -PTS version: 5.2
> -Tested: 17-July-2014
> +PTS version: 5.3
> +Tested: 08-October-2014
>  Android version: 4.4.4
>  
>  Results:
> @@ -17,29 +17,23 @@ Test Name		Result	Notes
>  TC_RFC_BV_01_C		PASS	rctest -n -P 1 <btaddr>
>  TC_RFC_BV_02_C		PASS	rctest -r -P 1
>  TC_RFC_BV_03_C		PASS	rctest -r -P 1
> -TC_RFC_BV_04_C		FAIL	PTS issue #12421
> -				PTS issue #12414
> -				NOTE: DISC on DLC is expected; IUT disconnects
> -					rfcomm session (close)
> +TC_RFC_BV_04_C		PASS	NOTE: use ets provided in PTS issue #12414
>  TC_RFC_BV_05_C		PASS	rctest -n -P 4 <btaddr>
>  				Note: test requires IUT to connect on the given
>  				channel. sdptool browse <btaddr> to check the
>  				channel.
>  TC_RFC_BV_06_C		PASS	rctest -r -P 1
>  TC_RFC_BV_07_C		PASS	rctest -r -P 1
> -TC_RFC_BV_08_C		INC	PTS issue #12397
> -				NOTE: Incorrect frame type sent in response to
> -					the DISC command
> +TC_RFC_BV_08_C		PASS	rctest -r -P 1
> +				Note: use ets provided in PTS issue #12397
>  TC_RFC_BV_11_C		PASS	rctest -r -P 1
> -TC_RFC_BV_13_C		FAIL	PTS issue #12397
> -				NOTE: IUT sent the correct frame type (UIH)
> -				but the parameters did not match the
> -				requirements
> +TC_RFC_BV_13_C		PASS	rctest -r -P 1
> +				Note: use ets provided in PTS issue #12397
>  TC_RFC_BV_14_C		N/A
>  TC_RFC_BV_15_C		PASS	rctest -r -P 1
>  TC_RFC_BV_17_C		PASS	rctest -d -P 1
>  TC_RFC_BV_19_C		PASS
>  TC_RFC_BV_21_C		INC	PTS issue #12421
>  TC_RFC_BV_22_C		INC	PTS issue #12421
> -TC_RFC_BV_25_C		INC	PTS issue #12421
> +TC_RFC_BV_25_C		INC	PTS issue #12621
>  -------------------------------------------------------------------------------
> 

Applied (after moving PTS issues into same line as affected test name). Thanks.

-- 
Best regards, 
Szymon Janc

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-10-10  8:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-09 15:15 [PATCH] android/pts: RFCOMM PTS 5.3 update Sebastian Chlad
2014-10-10  8:36 ` Szymon Janc

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox