Difference between revisions of "MMDI Integration Test"

From CDOT Wiki
Jump to: navigation, search
(→‎Test Case 7)
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{Admon/obsolete}}
 +
 
=MMDI Android and A&D devices integration Test=
 
=MMDI Android and A&D devices integration Test=
  
Line 227: Line 229:
  
 
|
 
|
−
The devices are paired, but test app cannot obtain readings.
+
The devices were paired, but test app could not obtain readings.
  
 
|-
 
|-
Line 255: Line 257:
  
 
|
 
|
−
The devices are paired, but test app cannot obtain readings.
+
The devices were paired, but test app could not obtain readings.
  
 
|}
 
|}
Line 359: Line 361:
  
 
|}
 
|}
 +
 +
 +
  
 
==Test Case 3==
 
==Test Case 3==
Line 522: Line 527:
  
 
|}
 
|}
 +
 +
 +
  
 
==Test Case 4==
 
==Test Case 4==
Line 598: Line 606:
 
|-
 
|-
 
|
 
|
−
Review-2
 
−
 
 
(aac4148)
 
(aac4148)
  
Line 625: Line 631:
 
|-
 
|-
 
|
 
|
−
Review-2
 
−
 
 
(aac4148)
 
(aac4148)
  
Line 652: Line 656:
 
|-
 
|-
 
|
 
|
−
Review-2
 
−
 
 
(aac4148)
 
(aac4148)
  
Line 679: Line 681:
 
|-
 
|-
 
|
 
|
−
Review-2
 
−
 
 
(aac4148)
 
(aac4148)
  
Line 706: Line 706:
 
|-
 
|-
 
|
 
|
−
Review-2
 
−
 
 
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/13241fd6b507d7b1d168cb55ff5f313f68b48096 13241fd])
 
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/13241fd6b507d7b1d168cb55ff5f313f68b48096 13241fd])
  
Line 717: Line 715:
  
 
|
 
|
−
2
+
1
  
 
|
 
|
Line 733: Line 731:
 
|-
 
|-
 
|
 
|
−
Review-2
 
−
 
 
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/13241fd6b507d7b1d168cb55ff5f313f68b48096 13241fd])
 
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/13241fd6b507d7b1d168cb55ff5f313f68b48096 13241fd])
  
Line 744: Line 740:
  
 
|
 
|
−
1
+
2
  
 
|
 
|
Line 760: Line 756:
 
|-
 
|-
 
|
 
|
−
Review-2
+
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/b7d2f8ab17d03cdfb23aed559248b7e3c64e622d b7d2f8a])
−
 
 
−
(b7d2f8a)
 
  
 
|
 
|
Line 771: Line 765:
  
 
|
 
|
−
2
+
1
  
 
|
 
|
Line 787: Line 781:
 
|-
 
|-
 
|
 
|
−
Review-2
+
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/b7d2f8ab17d03cdfb23aed559248b7e3c64e622d b7d2f8a]))
−
 
 
−
(b7d2f8a)
 
  
 
|
 
|
Line 798: Line 790:
  
 
|
 
|
−
1
+
2
  
 
|
 
|
Line 813: Line 805:
  
 
|}
 
|}
 +
 +
 +
  
 
==Test Case 5==
 
==Test Case 5==
Line 916: Line 911:
  
 
|}
 
|}
 +
 +
 +
  
 
==Test Case 6==
 
==Test Case 6==
Line 1,078: Line 1,076:
  
 
|}
 
|}
 +
 +
 +
  
 
==Test Case 7==
 
==Test Case 7==
Line 1,153: Line 1,154:
 
|-
 
|-
 
|
 
|
−
(aac4148)
+
(aac4148)
  
 
|
 
|
Line 1,182: Line 1,183:
 
|-
 
|-
 
|
 
|
−
(aac4148)
+
(aac4148)
  
 
|
 
|
Line 1,211: Line 1,212:
 
|-
 
|-
 
|
 
|
−
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/13241fd6b507d7b1d168cb55ff5f313f68b48096 13241fd])
+
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/13241fd6b507d7b1d168cb55ff5f313f68b48096 13241fd])
  
 
|
 
|
Line 1,236: Line 1,237:
 
|-
 
|-
 
|
 
|
−
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/13241fd6b507d7b1d168cb55ff5f313f68b48096 13241fd])
+
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/13241fd6b507d7b1d168cb55ff5f313f68b48096 13241fd])
  
 
|
 
|
Line 1,261: Line 1,262:
 
|-
 
|-
 
|
 
|
−
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/b7d2f8ab17d03cdfb23aed559248b7e3c64e622d b7d2f8a])
+
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/b7d2f8ab17d03cdfb23aed559248b7e3c64e622d b7d2f8a])
  
 
|
 
|
Line 1,286: Line 1,287:
 
|-
 
|-
 
|
 
|
−
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/b7d2f8ab17d03cdfb23aed559248b7e3c64e622d b7d2f8a])
+
([https://bitbucket.org/nexj/mobile-bluetooth-adapters/commits/b7d2f8ab17d03cdfb23aed559248b7e3c64e622d b7d2f8a])
  
 
|
 
|
Line 1,310: Line 1,311:
  
 
|}
 
|}
 +
 +
 +
  
 
==Test Summary Records==
 
==Test Summary Records==
Line 1,329: Line 1,333:
  
 
|
 
|
 +
  1. HTC A7275 (Android version 2.3.3) passed the test.
 +
 +
  2. MOTOROLA XT885 (Android version 4.04) passed the test.
 +
 +
  3. MOTOROLA MB860 (Android version 2.2.1) failed in the test (connection could not be set up).
  
 +
  4. Samsung Galaxy S3 (Android version 4.1.1) failed in the test (its Bluetooth cannot work stably).
  
 
|
 
|

Latest revision as of 21:50, 26 January 2014

Important.png
This page may be obsolete.
It contains historical information.

MMDI Android and A&D devices integration Test

Purpose: using build-in test code (index.html, app.js) to perform system level test for Android and A&D devices.

Android devices: 

   1. HTC A7275 (Android version 2.3.3).

   2. MOTOROLA XT885 (Android version 4.04).

   3. MOTOROLA MB860 (Android version 2.2.1).

A&D devices: 

   1. UA-767 PBT, Blood Pressure Monitor.

   2. UC-321 PBT, Weight Scale.

Terms or phrase used in the test

  • "Android device is ready for receiving data from A&D devices"
    • This is a status of the test application, which means:
      1. Android device is in the “discoverable” state.
      2. Android A&D Bluetooth server is “listening”.
    • To get the status we need the following process:
      1. Start the test application (named: NexJ MMDI))
      2. Enable Bluetooth (need only when Bluetooth is at disabled state)
      3. Request for Discoverable (Bluetooth discoverable state lasts for only 5 minutes for many Android devices.)
      4. Start listen A&D Devices
      5. Make sure taking the first measurement within Bluetooth Discoverable state.
  • “The Android and the medical devices are paired”
    • After the first connection between a certain Android device and a certain medical device, the two devices will become paired. This can be verified by checking the Android devices’ Bluetooth paired/bonded device list.
    • In all test cases, it is assumed that the two devices are paired if not specified.



Test Case 1

Test Case Number: TC01

Test Title: Bluetooth paring test

Description: To test paring process between an Android device and an A&D device.

Pre-Conditions:

  • The Android and the medical device have been unpaired (by removing the medical device from the Bluetooth paired/bonded device list of the android device).
  • Android device is ready for receiving data from A&D devices.

Test Steps:

  1. Make a measurement on an A&D device.
  2. Enter the PIN (39121440) when prompt on an Android device.
  3. The measurement reading(s) should be showed on the screen.
  4. Exit the test app.

Test Records:

Version

Android Device

Android Version

Medical Device

Repeat number

Pass or Fail

Test Date

By

Notes

Review-2

HTC A7275

2.3.3

UA-767

3

pass

Mar 8, 2013

Wei


Review-2

HTC A7275

2.3.3

UC-321

3

pass

Mar 8, 2013

Wei


Review-2

MOTOROLA XT885

4.0.4

UA-767

2

pass

Mar 14, 2013

Wei


Review-2

MOTOROLA XT885

4.0.4

UC-321

2

pass

Mar 14, 2013

Wei


Review-2

MOTOROLA MB860

2.2.1

UA-767

2

fail

Mar 15, 2013

Wei

The devices were paired, but test app could not obtain readings.

Review-2

MOTOROLA MB860

2.2.1

UC-321

2

fail

Mar 15, 2013

Wei

The devices were paired, but test app could not obtain readings.

Test Case 2

Test Case Number: TC02

Test Title: Plugin Function test part A

Description: To test the plugin’s functions of enable-Bluetooth, disable-Bluetooth, is-Bluetooth-enabled.

Pre-Conditions: The test application has been started.

Test Steps:

  1. Click “Disable Bluetooth” button, screen should show “Disable BT was successfully” and the Bluetooth icon should disappear from Android top bar.
  2. Click “Is Bluetooth Enabled” button, screen should show “BT is not enabled”.
  3. Click “Enable Bluetooth” button, then click “Yes” for the pop-up, screen should show “Enable BT was successfully” and the Bluetooth icon should appear in Android top bar.
  4. Click “Is Bluetooth Enabled” button, the screen should show “BT is enabled”.
  5. Click "Request for Discoverable" button.
  6. Click "listen to A&D Devices" button.
  7. Take a measurement, the Android screen should show the readings.
  8. Exit the test app.

Test Records:

Version

Android Device

Medical Device

Repeat number

Pass or Fail

Test Date

By

Notes

Review-2

HTC A7275

UA-767 or UC-321

3

pass

Mar 8, 2013

Wei


Review-2

MOTOROLA XT885

UA-767 or UC-321

3

pass

Mar 15, 2013

Wei




Test Case 3

Test Case Number: TC03

Test Title: Plugin Function test part B

Description: To test the plugin’s functions of Request-for-Discoverable.

Pre-Conditions: The test application has been started.

Test Steps:

  1. Click “Listen to A&D Devices” button, the screen should show “BT listening started”.
  2. Take a measurement, the Android screen may show the readings.
  3. Click “Request for Discoverable” button, then click “Yes” for the pop-up.
  4. Take a measurement, the Android screen should show the previous readings, then the current readings.
  5. Exit the test app.

Test Records:

Version

Android Device

Medical Device

Readings are Received at step 2 ?

Repeat number

Pass or Fail

Test Date

By

Notes

Review-2

HTC A7275

UA-767

No

3

pass

Mar 8, 2013

Wei


Review-2

HTC A7275

UC-321

No

3

pass

Mar 8, 2013

Wei


Review-2

MOTOROLA XT885

UA-767

Yes

2

pass

Mar 15, 2013

Wei

The Android device’s Bluetooth visibility timeout is set to “Never”

Review-2

MOTOROLA XT885

UC-321

Yes

2

pass

Mar 15, 2013

Wei

The Android device’s Bluetooth visibility timeout is set to “Never”



Test Case 4

Test Case Number: TC04

Test Title: Plugin Function test part C

Description: To test the plugin’s functions of Listen-to-A&D-Device and stop-listening.

Pre-Conditions: Android device is ready for receiving data from A&D devices.

Test Steps:

  1. Take a measurement, the Android screen should show the readings.
  2. Click “Stop Listening” button, the Android screen should show “BT listening stopped”.
  3. Take a measurement, no readings should show up at the app’s data area.
  4. Click "Request for Discoverable" button.
  5. Click “Listen to Discoverable” button, the Android screen should show “BT listening started”.
  6. Take a measurement, the screen should show the previous readings then the current readings.
  7. Exit the test app.

Test Records:

Version

Android Device

Medical Device

Repeat number

Pass or Fail

Test Date

By

Notes

Review-2

HTC A7275

UA-767 or UC-321

6

Fail

Mar 8, 2013

Wei

Fail to get readings at step 5 ( 3 fails out of 6 attempts)

(aac4148)

HTC A7275

UA-767

4

pass

Mar 14, 2013

Wei


(aac4148)

HTC A7275

UC-321

3

pass

Mar 14, 2013

Wei


(aac4148)

MOTOROLA XT885

UA-767

3

pass

Mar 14, 2013

Edward


(aac4148)

MOTOROLA XT885

UC-321

2

pass

Mar 14, 2013

Edward


(13241fd)

HTC A7275

UA-767

1

pass

Mar 14, 2013

Wei


(13241fd)

HTC A7275

UC-321

2

pass

Mar 14, 2013

Wei


(b7d2f8a)

MOTOROLA XT885

UA-767

1

pass

Mar 14, 2013

Wei


(b7d2f8a))

MOTOROLA XT885

UC-321

2

pass

Mar 14, 2013

Wei




Test Case 5

Test Case Number: TC05

Test Title: Plugin Function test part D

Description: To test the plugin’s functions of Paired/Bounded-Device.

Pre-Conditions: The test application has been started.

Test Steps:

  1. Click “Paired/Bounded-Device” button, the Android screen should show a list of paired devices for the Android device.
  2. Exit the test app.


Test Records:

Version

Android Device

Medical Device

Repeat number

Pass or Fail

Test Date

By

Notes

Review-2

HTC A7275


/

2

pass

Mar 8, 2013

Wei


Review-2

(aac4148)

MOTOROLA XT885


/

2

pass

Mar 14, 2013

Wei




Test Case 6

Test Case Number: TC06

Test Title: stability test part A

Description: To test the application's ability of receiving a serial of measurements with different distance between the two devices.

Pre-Conditions: Android device is ready for receiving data from A&D devices.

Test Steps:

  1. Make the two devices in a certain distance.
  2. Take a measurement by randomly choosing different medical devices (UA-767 or UC-321), the Android screen should show the readings.
  3. Repeat step 2 for 3 more times.
  4. Exit the test app.

Test Records:

Version

Android Device

Medical Device

distance

Repeat number

Pass or Fail

Test Date

By

Notes

Review-2

HTC A7275

UA-767 and UC-321

2m

2

pass

Mar 12, 2013

Wei


Review-2

HTC A7275

UA-767 and UC-321

5m

2

pass

Mar 12, 2013

Wei


Review-2

MOTOROLA XT885

UA-767 and UC-321

2m

2

pass

Mar 14, 2013

Wei


Review-2

MOTOROLA XT885

UA-767 and UC-321

5m

2

pass

Mar 14, 2013

Wei




Test Case 7

Test Case Number: TC07

Test Title: stability test part B

Description: To test the application's stability after receiving illogic operation.

Pre-Conditions: Android device is ready for receiving data from A&D devices.

Test Steps:

  1. Click "Disable Bluetooth" button.
  2. Click "Listen to A&D Devices", the Android screen may show errors.
  3. Click "Request for Discoverable" button.
  4. Click “Listen to A&D Devices" button.
  5. Take a measurement, then check if Android screen can show the readings.
  6. Exit the test app.

Test Records:

Version

Android Device

Medical Device

Repeat number

Pass or Fail

Test Date

By

Notes

Review-2

HTC A7275

UA-767 or UC-321

2

/

Mar 12, 2013

Wei

App exits at step 1.

(aac4148)

MOTOROLA XT885

UA-767

3

pass

Mar 14, 2013

Edward,


Wei


(aac4148)

MOTOROLA XT885

UC-321

2

pass

Mar 14, 2013

Edward,


Wei


(13241fd)

HTC A7275

UA-767

1

pass

Mar 15, 2013

Wei


(13241fd)

HTC A7275

UC-321

2

pass

Mar 15, 2013

Wei


(b7d2f8a)

MOTOROLA XT885

UA-767

1

pass

Mar 15, 2013

Wei


(b7d2f8a)

MOTOROLA XT885

UC-321

2

pass

Mar 15, 2013

Wei




Test Summary Records

Version

Summary

Date

Review-2 

  1. HTC A7275 (Android version 2.3.3) passed the test.

  2. MOTOROLA XT885 (Android version 4.04) passed the test.

  3. MOTOROLA MB860 (Android version 2.2.1) failed in the test (connection could not be set up). 

  4. Samsung Galaxy S3 (Android version 4.1.1) failed in the test (its Bluetooth cannot work stably).


Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=MMDI_Integration_Test&oldid=104157"