Note: This page describes work done for the first pilot phase in Cloud4all (2013).

While the integration tests aim at testing that the setting handlers work fine, the main objective of the pilot scenarios tests is to make sure that the user listeners and the transformations performed by the MatchMakers work fine.

Prerequisites

Material

Two computers, one with Windows 7 and one with Linux, both computers with the latest version of GPII installed.
One USB
[Optional] One NFC reader and one rewritable NFC tag

Windows 7

If you haven't already done so, download:
Make sure your internet connection is working, preferably with no proxies.

Linux

If you haven't already done so, download in the folder(s) of your choice:
- orca_snapshot
- linux_snapshot
Make sure your internet connection is working, preferably with no proxies.

Test scripts

Screenreader, from Linux to Windows

screenreader_orca

Prerequisites

Load token 'screenreader_orca' in the USB
- In the USB device, create a text file with the content 'screenreader_orca'; save the file as '.gpii-user-token'
Make sure NVDA is closed.

Testing with the Rule Based Matchmaker

Take a snapshot of NVDA's configuration.
- Open a CMD, go to the folder where you stored 'nvda_settings.cmd' and type 'nvda_snapshot.cmd > PS_RB_screenreader_orca_before.txt'
In the Windows computer, start the GPII with the Rule Based Matchmaker (in the command line, go to the folder where you have installed GPII - e.g. C:/gpii_pilots/windows - and type start_RB.cmd)
Insert the USB
Check that the login has worked
- Console UsbUserListener.exe should display the message 'User with token screenreader_orca was successfully logged in."
- If NVDA does not start automatically, it is a bug.
- In the command line, go to the folder where you have stored nvda_settings.cmd and type 'nvda_snapshot.cmd > PS_RB_screenreader_orca_during.txt'.
- Check that PS_screenreader_orca_RB_during.txt contains at least the following configuration [1].
Extract the USB
- Console UsbUserListener.exe should display the message 'User with token screenreader_orca was successfully logged out."
Check that the configuration of NVDA is the same as before inserting the USB
- If NVDA has not closed, this is a bug.
- In the CMD, type 'nvda_snapshot.cmd > PS_screenreader_orca_RB_after.txt'
- Check that PS_RB_screenreader_orca_before.txt and PS_screenreader_orca_RB_after.txt are EXACTLY the same. If not, this is a bug.
Close GPII and the user listener

[1] PS_screenreader_orca_RB_during.txt

reportHelpBalloons = False
speakTypedCharacters = False
speakTypedWords = True
sayCapForCapitals = False
autoSayAllOnPageLoad = False
rate = 17.20430107526882
rateBoost = true
symbolLevel = 300
voice = en\en-wi

Testing with the Statistical Matchmaker

Repeat the procedure with the ST MM - change RB by ST in all places where ST appears

TECH8

This test will use the NFC reader. If are not going to use a NFC reader during the tests, you can skip the test or do it with a USB key.

Prerequisites

In a NFC tag, write a plain text with the text 'TECH8'
Connect the NFC reader to your Windows computer
Make sure NVDA is closed

Testing with the Statistical Matchmaker

Take a snapshot of NVDA's configuration.
- Open a CMD, go to the folder where you stored 'nvda_settings.cmd' and type 'nvda_command.cmd > PS_ST_TECH8_before.txt'
In the Windows computer, start the GPII with the statistical Matchmaker
- Start the NFC User Listener (Double-click on UsbUserListener)
- In the command line, go to the folder where you have installed GPII - e.g. C:/gpii_pilots/windows - and type start_ST.cmd
Id yourself with the NFC tag on the NFC reader
Check that NVDA's configuration has changed
- If NVDA does not start automatically, it is a bug.
- In the command line, go to the folder where you have stored nvda_settings.cmd and type 'nvda_settings.cmd > PS_ST_TECH8_during.txt'.
- Check that PS_RB_during_screenreader_orca.txt contains at least the following configuration [2].
Id yourself with the NFC tag on the NFC reader
Check that the configuration of NVDA is the same as before logging in
- If NVDA has not closed, this is a bug.
- In the CMD, type 'nvda_settings.cmd > PS_ST_TECH8_after.txt'
- Check that PS_ST_TECH8_before.txt and PS_ST_TECH8_after.txt are EXACTLY the same. If not, this is a bug.
Close GPII and the user listener(s)

[2] PS_ST_TECH8_during.txt

reportHelpBalloons = False
speakTypedCharacters = False
speakTypedWords = True
sayCapForCapitals = False
autoSayAllOnPageLoad = 1
rate = 75
rateBoost = true
symbolLevel = 300
voice = es

OS settings, from Linux to Windows

os_gnome.json

Prerequisites

Load token 'os_gnome' in the USB
- In the USB device, create a text file with the content 'screenreader_orca'; save the file as '.gpii-user-token'

Testing with the Rule Based Matchmaker

Take a snapshot of NVDA's configuration.
- Open a CMD, go to the folder where you stored 'win7_settings.cmd' and type 'win7_snapshot.cmd > PS_RB_os_gnome_before.txt'
In the Windows computer, start the GPII with the Rule Based Matchmaker (in the command line, go to the folder where you have installed GPII - e.g. C:/gpii_pilots/windows - and type start_RB.cmd)
Insert the USB
Check that the login has worked
- Console UsbUserListener.exe should display the message 'User with token screenreader_orca was successfully logged in."
- In the command line, go to the folder where you have stored nvda_settings.cmd and type 'win7_snapshot.cmd > PS_RB_os_gnome_during.txt'.
- Check that PS_during_screenreader_orca_RB.txt contains at least the following configuration [3].
Extract the USB
- Console UsbUserListener.exe should display the message 'User with token screenreader_orca was successfully logged out."
Check that the configuration of NVDA is the same as before inserting the USB
- In the CMD, type 'win7_snapshot.cmd > PS_RB_os_gnome_after.txt'
- Check that PS_RB_os_gnome_before.txt and PS_RB_os_gnome_after.txt are EXACTLY the same. If not, this is a bug.
Close GPII and the user listener

[3] PS_RB_os_gnome_during.txt

HKEY_CURRENT_USER\Software\Microsoft\ScreenMagnifier
    Magnification    REG_DWORD    0x96
HKEY_CURRENT_USER\Software\Microsoft\ScreenMagnifier
    Invert    REG_DWORD    0x1
HKEY_CURRENT_USER\Software\Microsoft\ScreenMagnifier
    FollowFocus    REG_DWORD    0x0
HKEY_CURRENT_USER\Software\Microsoft\ScreenMagnifier
    FollowCaret    REG_DWORD    0x0
HKEY_CURRENT_USER\Software\Microsoft\ScreenMagnifier
    FollowMouse    REG_DWORD    0x1
HKEY_CURRENT_USER\Software\Microsoft\ScreenMagnifier
    MagnificationMode    REG_DWORD    0x2
HKEY_CURRENT_USER\Control Panel\Cursors
    (Predeterminado)    REG_SZ    Aero de Windows
    Scheme Source    REG_DWORD    0x2
    Arrow    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_arrow.cur
    Help    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_helpsel.cur
    Hand    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_link.cur
    AppStarting    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_working.ani
    Wait    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_busy.ani
    NWPen    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_pen.cur
    No    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_unavail.cur
    SizeNS    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_ns.cur
    SizeWE    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_ew.cur
    SizeNWSE    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_nwse.cur
    SizeNESW    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_nesw.cur
    SizeAll    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_move.cur
    UpArrow    REG_EXPAND_SZ    %SystemRoot%\cursors\aero_up.cur

TECH10

Prerequisites

In a NFC tag, write a plain text with the text 'TECH10'
Connect the NFC reader to your Windows computer

Testing with the Statistical Matchmaker

Take a snapshot of Windows 7 configuration.
- Open a CMD, go to the folder where you stored 'win7_command.cmd' and type 'win7_command.cmd > PS_ST_TECH10_before.txt'
In the Windows computer, start the GPII with the statistical Matchmaker
- Start the NFC User Listener (Double-click on UsbUserListener)
- In the command line, go to the folder where you have installed GPII - e.g. C:/gpii_pilots/windows - and type start_ST.cmd
Id yourself with the NFC tag on the NFC reader
Check that NVDA's configuration has changed
- Magnifier should launch. If not, this is a bug.
- In the command line, go to the folder where you have stored nvda_settings.cmd and type 'nvda_settings.cmd > PS_ST_TECH10_during.txt'.
- Check that PS_RB_during_screenreader_orca.txt contains at least the following configuration [4].
Id yourself with the NFC tag on the NFC reader
Check that the configuration of NVDA is the same as before logging in
- If NVDA has not closed, this is a bug.
- In the CMD, type 'nvda_settings.cmd > PS_ST_TECH10_after.txt'
- Check that PS_ST_TECH10_before.txt and PS_ST_TECH10_after.txt are EXACTLY the same. If not, this is a bug.
Close GPII and the user listener(s)

[4] PS_ST_TECH10_during.txt

HKEY_CURRENT_USER\Software\Microsoft\ScreenMagnifier

   Magnification    REG_DWORD    0x96