1
edit
Changes
Created page with 'MMDI Android and A&D devices integration Test '''Purpose:''' using build-in test code (<nowiki>index.ht</nowiki>ml, <nowiki>app.js</nowiki>) to perform system level test for An…'
MMDI Android and A&D devices integration Test
'''Purpose:''' using build-in test code (<nowiki>index.ht</nowiki>ml, <nowiki>app.js</nowiki>) to perform system level test for Android and A&D devices.
'''Android devices:'''
1. HTC Desire Z (Android version 2.2).
2. MOTOROLA RAZR V (Android version 4.04).
'''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:
**:# Android device is in the “discoverable” state.
**:# Android A&D Bluetooth server is “listening”.
** to get the status we need the following process:
**:# Start the test application (named: NexJ MMDI))
**:# Enable Bluetooth (need only when Bluetooth is at disabled state)
**:# Request for Discoverable (Bluetooth discoverable state lasts for only 5 minutes for many Android devices.)
**:# Start listen A&D Devices
**:# 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:
::# Make a measurement on an A&D device.
::# Enter the PIN (39121440) when prompt on an Android device.
::# The measurement reading(s) should be showed on the screen.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
UA-767
|
3
|
pass
|
Mar 8, 2013
|
Wei
|
|-
|
Review-2
|
HTC
|
UC-321
|
3
|
pass
|
Mar 8, 2013
|
Wei
|
|-
|
Review-2
|
MOTOROLA
|
UA-767
|
|
|
|
|
|-
|
Review-2
|
MOTOROLA
|
UC-321
|
|
|
|
|
|}
'''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:
::# Click “Is Bluetooth Enabled” button, the screen should show “BT is enabled”.
::# Click “Disable Bluetooth” button, screen should show “Disable BT was successfully” and the Bluetooth icon should disappear from Android top bar.
::# Click “Is Bluetooth Enabled” button, screen should show “BT is not enabled”.
::# 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.
::# Click “Is Bluetooth Enabled” button, the screen should show “BT is enabled”.
::# Take a measurement, the Android screen should show the readings.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
UA-767 or UC-321
|
3
|
pass
|
Mar 8, 2013
|
Wei
|
|-
|
Review-2
|
MOTOROLA
|
UA-767 or UC-321
|
|
|
|
|
|-
|
Review-2
|
|
|
|
|
|
|
|}
'''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:
::# Click “Listen to A&D Devices” button, the screen should show “BT listening started”.
::# Take a measurement, the Android screen may show the readings.
::# Click “Request for Discoverable” button, then click “Yes” for the pop-up.
::# Take a measurement, the Android screen should show the previous readings, then the current readings.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
Readings are Received at step 1?
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
UA-767
|
No
|
3
|
pass
|
Mar 8, 2013
|
Wei
|
|-
|
Review-2
|
HTC
|
UC-321
|
No
|
3
|
pass
|
Mar 8, 2013
|
Wei
|
|-
|
Review-2
|
MOTOROLA
|
|
|
|
|
|
|
|-
|
|
|
|
|
|
|
|
|
|}
'''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:
::# Take a measurement, the Android screen should show the readings.
::# Click “Stop Listening” button, the Android screen should show “BT listening stopped”.
::# Take a measurement, no readings should show up at the app’s data area.
::# Click “Listen to Discoverable” button, the Android screen should show “BT listening started”.
::# Take a measurement, the screen should show the previous readings then the current readings.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
UA-767
|
2
|
Fail
|
Mar 8, 2013
|
Wei
|
Fail to get readings at step 5
|-
|
Review-2
|
HTC
|
UC-321
|
2
|
pass
|
Mar 8, 2013
|
Wei
|
After several attempt, system Error: Activity NexJ MMDI (in application DevicePlugins is not responding. Force close? Or Wait?
|-
|
Review-2
|
MOTOROLA
|
UA-767
|
|
|
|
|
|-
|
Review-2
|
MOTOROLA
|
UC-321
|
|
|
|
|
|}
'''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:
::# Click “Paired/Bounded-Device” button, the Android screen should show a list of paired devices for the Android device.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
/
|
2
|
pass
|
Mar 8, 2013
|
Wei
|
|-
|
Review-2
|
MOTOROLA
|
|
|
|
|
|
|}
'''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:
::# Make the two devices in a certain distance.
::# Take a measurement by randomly choosing different medical devices (UA-767 or UC-321), the Android screen should show the readings.
::# Repeat step 2 for 5 more times.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
distance
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
UA-767 and UC-321
|
3m
|
|
|
|
Wei
|
|-
|
Review-2
|
HTC
|
UA-767 and UC-321
|
5m
|
|
|
|
Wei
|
|-
|
Review-2
|
HTC
|
UA-767 and UC-321
|
10m
|
|
|
|
Wei
|
|-
|
Review-2
|
MOTOROLA
|
|
|
|
|
|
|
|}
'''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:
::# Click "Disable Bluetooth".
::# Click “Stop Listening” button.
::# Take a measurement, the Android screen should not show the readings.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
UA-767 or UC-321
|
|
|
|
|
|-
|
Review-2
|
MOTOROLA
|
|
|
|
|
|
|}
'''Test Summary Records'''
{| class="prettytable"
|-
|
Version
|
Summary
|
Date
|-
|
Review-2
|
|
|}
'''Purpose:''' using build-in test code (<nowiki>index.ht</nowiki>ml, <nowiki>app.js</nowiki>) to perform system level test for Android and A&D devices.
'''Android devices:'''
1. HTC Desire Z (Android version 2.2).
2. MOTOROLA RAZR V (Android version 4.04).
'''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:
**:# Android device is in the “discoverable” state.
**:# Android A&D Bluetooth server is “listening”.
** to get the status we need the following process:
**:# Start the test application (named: NexJ MMDI))
**:# Enable Bluetooth (need only when Bluetooth is at disabled state)
**:# Request for Discoverable (Bluetooth discoverable state lasts for only 5 minutes for many Android devices.)
**:# Start listen A&D Devices
**:# 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:
::# Make a measurement on an A&D device.
::# Enter the PIN (39121440) when prompt on an Android device.
::# The measurement reading(s) should be showed on the screen.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
UA-767
|
3
|
pass
|
Mar 8, 2013
|
Wei
|
|-
|
Review-2
|
HTC
|
UC-321
|
3
|
pass
|
Mar 8, 2013
|
Wei
|
|-
|
Review-2
|
MOTOROLA
|
UA-767
|
|
|
|
|
|-
|
Review-2
|
MOTOROLA
|
UC-321
|
|
|
|
|
|}
'''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:
::# Click “Is Bluetooth Enabled” button, the screen should show “BT is enabled”.
::# Click “Disable Bluetooth” button, screen should show “Disable BT was successfully” and the Bluetooth icon should disappear from Android top bar.
::# Click “Is Bluetooth Enabled” button, screen should show “BT is not enabled”.
::# 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.
::# Click “Is Bluetooth Enabled” button, the screen should show “BT is enabled”.
::# Take a measurement, the Android screen should show the readings.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
UA-767 or UC-321
|
3
|
pass
|
Mar 8, 2013
|
Wei
|
|-
|
Review-2
|
MOTOROLA
|
UA-767 or UC-321
|
|
|
|
|
|-
|
Review-2
|
|
|
|
|
|
|
|}
'''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:
::# Click “Listen to A&D Devices” button, the screen should show “BT listening started”.
::# Take a measurement, the Android screen may show the readings.
::# Click “Request for Discoverable” button, then click “Yes” for the pop-up.
::# Take a measurement, the Android screen should show the previous readings, then the current readings.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
Readings are Received at step 1?
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
UA-767
|
No
|
3
|
pass
|
Mar 8, 2013
|
Wei
|
|-
|
Review-2
|
HTC
|
UC-321
|
No
|
3
|
pass
|
Mar 8, 2013
|
Wei
|
|-
|
Review-2
|
MOTOROLA
|
|
|
|
|
|
|
|-
|
|
|
|
|
|
|
|
|
|}
'''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:
::# Take a measurement, the Android screen should show the readings.
::# Click “Stop Listening” button, the Android screen should show “BT listening stopped”.
::# Take a measurement, no readings should show up at the app’s data area.
::# Click “Listen to Discoverable” button, the Android screen should show “BT listening started”.
::# Take a measurement, the screen should show the previous readings then the current readings.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
UA-767
|
2
|
Fail
|
Mar 8, 2013
|
Wei
|
Fail to get readings at step 5
|-
|
Review-2
|
HTC
|
UC-321
|
2
|
pass
|
Mar 8, 2013
|
Wei
|
After several attempt, system Error: Activity NexJ MMDI (in application DevicePlugins is not responding. Force close? Or Wait?
|-
|
Review-2
|
MOTOROLA
|
UA-767
|
|
|
|
|
|-
|
Review-2
|
MOTOROLA
|
UC-321
|
|
|
|
|
|}
'''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:
::# Click “Paired/Bounded-Device” button, the Android screen should show a list of paired devices for the Android device.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
/
|
2
|
pass
|
Mar 8, 2013
|
Wei
|
|-
|
Review-2
|
MOTOROLA
|
|
|
|
|
|
|}
'''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:
::# Make the two devices in a certain distance.
::# Take a measurement by randomly choosing different medical devices (UA-767 or UC-321), the Android screen should show the readings.
::# Repeat step 2 for 5 more times.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
distance
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
UA-767 and UC-321
|
3m
|
|
|
|
Wei
|
|-
|
Review-2
|
HTC
|
UA-767 and UC-321
|
5m
|
|
|
|
Wei
|
|-
|
Review-2
|
HTC
|
UA-767 and UC-321
|
10m
|
|
|
|
Wei
|
|-
|
Review-2
|
MOTOROLA
|
|
|
|
|
|
|
|}
'''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:
::# Click "Disable Bluetooth".
::# Click “Stop Listening” button.
::# Take a measurement, the Android screen should not show the readings.
::# Exit the test app.
Test Records:
{| cellspacing="1" cellpadding="3" border="2"
|-
|
Version
|
Android Device
|
Medical Device
|
Repeat number
|
Pass or Fail
|
Test Date
|
By
|
Notes
|-
|
Review-2
|
HTC
|
UA-767 or UC-321
|
|
|
|
|
|-
|
Review-2
|
MOTOROLA
|
|
|
|
|
|
|}
'''Test Summary Records'''
{| class="prettytable"
|-
|
Version
|
Summary
|
Date
|-
|
Review-2
|
|
|}
