Weekly Integration Test Plan

From wiki.gpii
Jump to: navigation, search

Scenario one

Windows 7:

Setup:

  • Windows 7 machine with
    • NVDA
    • Google chrome plugin installed
  • RFID card with the user token: vladimir

Background:

Vladimir is a user with low vision on a business trip in Munich.

  • He is a Windows user who usually combines
    • JAWS; high contrast, large cursor with mousetrails
    • He speaks english but not German.
  • Tomorrow he has a meeting. He arrives at the hotel in the evening and remembers he forgot to pay his landlady before he left.
  • He goes to the lobby and sits in front of a Windows 7 workstation there to access his bank and pay the rent bill.
  • The computer does not have JAWS installed

Preparation:

  • Use the device reporter file installedSolutionsVladimirLobby.json
  • Use the rule based MM [requires pull/310 ]


Test:

  • Touch the vladimir “KeyToken” to the workstation RFID reader.


Expected:

  • At the OS level: it activates a larger mouse pointer with mouse trails, activates high contrast
  • In the AT level: NVDA is activated and configured (high speechRate, no auto-say-all on pageload)


Test:

  • Open the chrome browser and load a website


Expected:

  • At the browser-plug in (Cloud4chrome) level:, high contrast is activated.
    • Still needs this pull request <[2]> to be accepted
    • the white on black theme should be enabled


Test:

  • Key out Vladimir


Expected:

  • All the above changes on OS and browser level should be changed to their previous values
    • Known bugs:
      • regarding cursor size which sometimes stay big after logout: <[3]> - system can be restored by restoring the standard theme.
      • Theme doesn't revert to the proper theme after logging out from high-contrast mode <[4]> - system can be restored by manually selecting the standard theme
  • Chrome browser should NOT be closed but high contrast should be disabled
    • Unimplemented - pending pull request (JAVI): <[5]>
  • NVDA should be closed.

Ticket vending machine:

Setup:

  • Any computer with a browser and internet connection can be used for this test.


Background:

  • The next morning, Vladimir goes to a bus station to buy a ticket at a ticket vending machine.
  • Since we don’t have a ticket vending machine available for testing we will check the online flowmanager input/output functionality.


Test:


Expected:

  • The following output should be expected on the screen:
{"de.fraunhofer.iao.C4A-TVM":{"fontSize":"big","contrastTheme":"yellow-black","buttonSize":"big"}}

Android phone:

Simple case (TBD by Kasper)

Complex case, involving two apps, contexts and environment sensing

Setup:

  • Android phone machine with
    • Smart twitter client installed
    • Talkback installed and able to talk
      • Check that by using the normal menus of the system, somewhere along the lines of Settings > Accessibility > Talkback
  • RFID card with the user token: vladimir


Test:

  • key in to the phone


Expected:

  • The screen reader should be launched automatically


Test:

  • Open the twitter client
  • Go to a bright place (or use another mobile flash light, a lamp...)


Expected:

  • Fontsize should increase
  • Brightness should increase
  • black on white theme should be enabled in the twitter client


Test:

  • Go to a dark place or block the light sensor


Expected:

  • Font size should decrease (or stay the same)
  • Brightness should decrease (or stay the same)
  • black on white theme should be enabled in the twitter client


Test:

  • Go to a loud place or make a constant sound


Expected:

  • The speechrate should decrease
  • The volume should increase


Scenario Two


Background:

  • Focus on how the Cloud4all/GPII can allow single devices in a classroom to adapt to many different individuals throughout a day. One device encountering many individuals.
  • We visit a Teacher in a classroom with many students who have disabilities. Here we can see how individual devices can adapt to different users. We can also see how the Cloud4all/GPII can make the adaptation process easier and much simpler to understand for the teacher. The teachers do not themselves have to learn all the different devices and how to set each on up for each different student.
  • These same attributes and advantages would also apply in other public, shared places like libraries, and public access points as well as in homes where people need to share computers, TV systems, thermostats and other electronic devices in the home.
  • In the classroom there is a 60/40 classroom with 40% of the children having disabilities. In the school, all the students who need adaptations have had a session with the school therapists and have a needs and preference set determined for them and saved in the cloud.
    • Some tire significantly during the day, and have more than one set of needs & preferences which the switch between depending on their abilities at any point in time.
    • Some brought their preference sets from their old school and the therapists just gave the students a chance to try them out on the new devices here and save any adjustments they needed to make.
    • Others were new to the Cloud4all/GPII and worked with the therapists and a PMT to get their first Preference sets.


Linux:

Setup:

  • Linux with Fedora 20
  • RFID tags with the following tokens:
    • mary
    • manuel

Test Mary:

Expected:

  • On-screen keyboard comes up on screen

Test:

  • Key out

Expected:

  • On-screen keyboard disappears

Test Manuel:

  • Key in with the ‘manuel’ RFID token

Expected:

  • built-in magnifier is launched with magnification factor 200%

Test:

  • Key out

Expected:

  • Magnifier is stopped

Windows 7:

Setup:

  • Windows 7 machine with:
    • Read&Write Gold
    • SuperNova
    • NVDA
  • Device reporter file:
    •  Use the device reporter file: review3/installedSolutionsClassroomWindows.json
  • RFID tags with the following tokens:
    • li
    • chris
    • franklin


Test Chris:

  • Key in with the ‘chris’ RFID token


Expected: 


Test:

  • Manually launch Supernova


Expected:


Test:

  • Manually close Supernova
  • Key out


Expected:


Test Li: (This whole scenario depends on https://github.com/GPII/universal/pull/304)

  • Key in with the li RFID token


Expected:

  • Supernova should be launched
  • Magnification should be on and should be set to 200%
  • Speech should be on and set to appr. 200 WPM
  • NVDA and built in magnifier should NOT be launched


Test:

  • Manually launch built in magnifier:


Expected:

  • magnification factor should be set to 200%


Test:

  • Kill built in magnifier and launch NVDA


Expected:

  • Speech rate should be 200 WPM


Test:

  • Kill NVDA manually
  • Log Li out using the keytoken


Expected:

  • Supernova should be stopped


Test Franklin:

  • Key in with the ‘franklin RFID token


Expected:

  • Read&Write gold should be launched
  • RWG should have the following settings:
  • Icons should be big
  • Text should be displayed under the icons
  • Screen reading should be disabled


Test:

  • Key franklin out using the keytoken


Expected:

  • RWG should be stopped


Android:


Test Chris:

  • Make sure GPII isn’t running on the on the phone
  • Manually open Mobile Accessiblity
  • Log in with Chris


Expected:

  • Speech rate should be high
  • If a braille display is connected, it should be enabled


Test Li:

  • Key in with Li


Expected:

  • Speech rate should be low
  • If a braille display is connected, it should be disabled


Test:

  • Log back in with Chris:


Expected:

  • Speech rate should be high
  • If a braille display is connected, it should be enabled