EdgeWave Software - Remote Filtering Project
Windows RFC 2.0 Beta1 Test Plan
Supported Windows: Windows XP (SP3), Vista, Win 7
Tester's Name
Logged in Administrator permissions
Logged on User name
OS (include 32 or 64 bit)
OS Edition
Processor 32 or 64 bit
Physical or VM install
Browsers
Browser Versions (32vs64bit app.)
Wireless/Wired Connection
Test Cases
Test Case sbs_1: Get to know your system’s performance
Steps: Expected Results:
Before starting the software installation process, use
each one of the supported browsers and surf to the Notice page load times.
following sites. Overall system CPU usage.
Use this info as a bench mark for further tests once
Supported browsers: the product is installed.
- Internet Explorer on Windows,
- Firefox on Windows
- Safari on Windows
- Chrome on Windows
Load any of these URLS:
http://www.w3.org
http://www.cbs.com
http://www.cnet.com
http://www.youtube.com
http://www.myspace.com
Result: Please indicate the browsers you used (including version) and results
Test Case sbs_2: Verify RFC completes installation with no errors
Steps: Note Version and Build indicated in the Registry
1- Run the .exe
2- Provide the supplied .key file during installation
3-Change the MACHINEID field if desired.
4- Click yes for reboot. Note: you must reboot for RFC
to function properly.
1
Result/Comments:
Test Case sbs_3: Verify upon successful installation, all processes have started
Expected Results:
Steps:
1.Verify both "St. Bernard Remote" "St. Bernard
Windows OS : Right Click my computer ->manager -
Redirector", and “rfclient_updater”services are
>Services and Applications ->Services
started
2. Go to Windows Task Manager, select Processes tab
Check the checkbox to show all system processes
and verify that rfcd.exe , SBSRedirector.exe and
rfclient_updater.exe are running
Results:
Test Case sbs_4: Verify non-blocked sites load
Steps: Expected Results:
1. On your iprism, set a policy for your remote
filtering client. No delay in page load
2. Load as many of the supported browsers (see test Check CPU usage for rfcd.exe and SBSRedirector.exe
sbs_1) as you can on Windows
3. Attempt to access a site that should not be
blocked.
Result:
Test Case sbs_5: Verify page redirect when visiting a blocked site
Steps: Expected Results:
- Verify you are redirected to an ACCESS DENIED
Using the same policy as Test Case 4, attempt to page.
access a site that should be blocked. - Confirm that the Redirect Page is loaded quickly
[few seconds]
- Verify no images, partial images, or text is displayed
from the offensive site
Result:
2
Test Case sbs_6: Verify Consistent Page load of blocked and non-blocked sites
Expected Results:
Steps:
- Check that client behaves per policy.
1. Continue to open new tabs in your browser or new
Page load time for both non-blocked sites and the
windows and alternate between visiting blocked and
redirect page meet acceptable time. [3-5 seconds or
non-blocked sites.
so]
2. Check CPU usage as this is occurring.
- Check CPU usage on test machine as this is
occurring
Result:
Test Case sbs_7: Verify when the machine resumes from hibernation the RFC is active
Expected Results:
Steps:
1. Verify the RFC is functioning correctly
RFC should function properly after waking from
2. Put the machine into hibernation
hibernation.
3. Wake the machine
Result:
Test Case sbs_-8: Verify RFC Filters when computer wakes up from sleep
Steps: Expected Results:
RFC should continue to filter when computer wakes
1. Browse to various websites and make sure RFC is up from sleep.
filtering as it should
2. Put laptop to sleep
Result:
Test Case sbs_-9: Verify other applications/ chats/ tools can function when RFC is installed
Steps: Expected Results:
Use your standard applications and tools, including -RFC continued to filter user traffic
chat applications, and verify they function correctly -RFC cpu usage remains low
-Non of the application/chat features are hindered by
RFC
3
Result: If you find a conflict with RFC, please note application name and version.
Test Case sbs_10: Verify windows updates are not obstructed by the RFC
Steps: Expected Results:
1. Goto Control Panel -> System and Security->
Windows update. Windows updates should not be obstructed by the
2. Check if Windows updates are not obstructed by RFC
the RFC.
Result:
Test Case sbs_11: Verify if user - has anti-virus software installed, then any AV updates are not obstructed
by the RFC
Steps: Expected Results:
Virus scanner updates should not be obstructed by
Install RFC on Windows machine with a virus scanner RFC.
product already installed.
Verify RFC functionality by visiting a site that should
be redirected.
Attempt to update the virus scanner.
Result:
Test Case sbs_12: Verify RFC Performance
Steps: Expected Results:
Throughout testing, check for the following and
ensure they are within acceptable range: No delay in page load
1. CPU usage Check CPU usage for rfcd.exe and SBSRedirector.exe
2. Page load time
Compare times with RFC loaded to times noted in
Test Case 1
Result:
Test Case sbs_13: Verify Filtering under Captive Portal
4
Steps: Expected Results:
Visit a Starbuck's or other institution where WiFi is Policy should be adhered as on premises.
provided Note, Blocked sites should be obstructed by RFC not
Start the PC and make sure RFC is running other filtering agent.
Login to the institution's authorization page
Surf to blocked and non-blocked sites
Result:
Test Case sbs_14: Verify RFC software cannot be tampered with
Steps: Expected Results:
1. From the Windows Task Manager, end the rfcd - RFCD process: RFCD process should restart
process. automatically.
2.Wait up to 30 seconds. Confirm expected result for - SBSRedirector process: SBSRedirector process
RFCD process. should restart automatically.
3. From the Windows Task Manager, end the
SBSRedirector process.
4. Wait up to 30 seconds. Confirm expected results
for SBSRedirector process.
Result:
Test Case sbs_15: Verify Reporting
Log into iPrism. On your iPrism, run the Iprism
Expected Results:
Report Manager. Confirm that client events are
Client events should all appear on the iPrism reports.
propagated to iPrism reports.
Users and policy should be identified.
Result:
5