Cloud4all Pilot Scenario Tests
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.
Contents
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:
- 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
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_SZ %SystemRoot%\cursors\aero_arrow_xl.cur Help REG_SZ %SystemRoot%\cursors\aero_helpsel_xl.cur Hand REG_SZ %SystemRoot%\cursors\aero_link_xl.cur AppStarting REG_SZ %SystemRoot%\cursors\aero_working_xl.ani Wait REG_SZ %SystemRoot%\cursors\aero_busy_xl.ani NWPen REG_SZ %SystemRoot%\cursors\aero_pen_xl.cur No REG_SZ %SystemRoot%\cursors\aero_unavail_l.cur SizeNS REG_SZ %SystemRoot%\cursors\aero_ns_xl.cur SizeWE REG_SZ %SystemRoot%\cursors\aero_ew_xl.cur SizeNWSE REG_SZ %SystemRoot%\cursors\aero_nwse_xl.cur SizeNESW REG_SZ %SystemRoot%\cursors\aero_nesw_xl.cur SizeAll REG_SZ %SystemRoot%\cursors\aero_move_xl.cur
UpArrow REG_SZ %SystemRoot%\cursors\aero_up_xl.cur
Screenreader, from Windows to Linux
screenreader_nvda
Prerequisites
- Load token 'screenreader_nvda' in the USB
- In the USB device, create a text file with the content 'screenreader_nvda'; save the file as '.gpii-user-token'
- Make sure ORCA is closed.
Testing with the Rule Based Matchmaker
- In the Linux computer, start the GPII with the Rule Based Matchmaker
- Click the system key, type GPII and then click on 'GPII Rule Based'
- Insert the USB
- Check that the login has worked
- If ORCA does not start automatically, it is a bug.
- In the command line, go to the folder where you have stored orca_settingsand type 'python orca_snapshot screenreader_nvda > PS_RB_screenreader_nvda_during.txt'.
- Check that PS_RB_screenreader_nvda_during.txt contains at least the following configuration [5].
- 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 ORCA has not closed, this is a bug.
- Close GPII and the user listener
[5] PS_RB_screenreader_nvda_during.txt
enableEchoByWord: True
enableEchoByCharacter: False
EnableTutorialMessages: False
enableBraille: False
verbalizePunctuationStyle: 0
enableSpeech: True
voices.default.family: {u'locale': u'en', u'name': u'en-westindies'}
voices.default.rate: 102.272727273
TECH9
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 'TECH9'
- Connect the NFC reader to your Linux computer
- Make sure Orca is closed
Testing with the Statistical Matchmaker
- In the Windows computer, start the GPII with the statistical Matchmaker
- Click the system key, type GPII and then click on 'GPII Statistical'
- Id yourself with the NFC tag on the NFC reader
- Check that ORCA's configuration has changed
- If ORCA 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 'python orca_snapshot TECH9 > PS_ST_TECH9_during.txt'.
- Check that PS_ST_TECH9_during.txt contains at least the following configuration [6].
- Id yourself with the NFC tag on the NFC reader
- Check that logging out has worked
- If ORCA has not closed, this is a bug.
- Close GPII and the user listener(s)
[6] PS_RB_TECH9_during.txt seeAllStyle: 1 enableEchoByWord: True enableEchoByCharacter: False EnableTutorialMessages: False enableBraille: False verbalizePunctuationStyle: 0 enableSpeech: True voices.default.family: <span style="color: rgb(255, 165, 0);">{u'locale': u'en', u'name': u'en-westindies'}</span> voices.default.rate: <span style="background-color: rgb(255, 165, 0);">102.272727273</span> Check if the GNOME Orca screenreader is running: YES
OS settings, from Windows to Linux
os_win7
Prerequisites
- Load token 'os_win7' in the USB
- In the USB device, create a text file with the content 'os_win7'; save the file as '.gpii-user-token'
Testing with the Rule Based Matchmaker
- In the Windows computer, start the GPII with the statistical Matchmaker
- Click the system key, type GPII and then click on 'GPII Statistical'
- Id yourself with the NFC tag on the NFC reader
- Check that the login has worked
- In the command line, go to the folder where you have stored linux_snapshot and type 'python linux_snapshot > PS_RB_TECH11_during.txt'.
- Check that PS_RB_TECH11_during.txt contains at least the following configuration [8].
- Id yourself with the NFC tag on the NFC reader (Log out)
- Check that the configuration of Linux is the same as before inserting the USB
- In the CMD, type 'python linux_snapshot > PS_RB_TECH11_after.txt'
- Check that PS_RB_TECH11_before.txt and PS_RB_TECH11_after.txt are EXACTLY the same. If not, this is a bug.
- Close GPII and the user listener
[7] PS_RB_os_win7_during.txt
#Magnifier settingsmag-factor: x screen-position: full-screen show-cross-hairs: False
- Magnifier settings
gtk-theme: Adwaita icon-theme: gnome text-scaling-factor: 1.0
cursor-size: 24
TECH11
Prerequisites
- In a NFC tag, write a plain text with the text 'TECH11'
- Connect the NFC reader to your Linux computer
- Make sure Orca is closed
Testing with the Statistical Matchmaker
- In the Windows computer, start the GPII with the statistical Matchmaker
- Click the system key, type GPII and then click on 'GPII Statistical'
- Id yourself with the NFC tag on the NFC reader
- Check that ORCA's configuration has changed
- If ORCA 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 'python orca_snapshot TECH9 > PS_ST_TECH9_during.txt'.
- Check that PS_ST_TECH9_during.txt contains at least the following configuration [6].
- Id yourself with the NFC tag on the NFC reader
- Check that logging out has worked
- If ORCA has not closed, this is a bug.
- Close GPII and the user listener(s)