Embed
Email

Mac_uTest_RFC2 Beta1 Testplan

Document Sample

Shared by: cuiliqing
Categories
Tags
Stats
views:
5
posted:
10/31/2011
language:
English
pages:
5
EdgeWave Software - Remote Filtering Project

MAC RFC 2.0 Beta1 Test Plan



Supported Platforms: 10.5.8 and Mac 10.6.4 [32bit and 64bit kernel]

Tester's Name

Logged in Administrator permissions

Logged on User name

OS

OS Edition

Processor 32 or 64 bit

Physical or VM install

Browser

Browser Version (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, load

one of the supported browsers and surf to the Notice page load times.

following sites and any others you wish. Overall system CPU usage.

Use this info as a bench mark for further tests once

Supported browsers: the product is installed.

- Firefox on Mac

- Safari on Mac

- Chrome on Mac



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: Place Your test results Here









Test Case sbs_2: Verify RFC completes installation with no errors

Steps: Note version and Build

1- Run the .pkg

2- Provide supplied .key file during installation

3- Change the MACHINEID field if appropriate.

4-Continue to install as guided by installer until the

reboot pop-up box appears.

5- Click yes for reboot. Note: you must reboot for RFC

to function properly.







1

Result:









Test Case sbs_3: Verify upon successful installation, all processes have started

Steps: Expected Results:



Mac OS: Applications -> Utilities -> Activity Monitor -> The RFCD process is running

Show All Processes -> Filter rfcd



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 using Activity Monitor

sbs_1) as you can on Windows

3. Attempt to access a site that should not be

blocked.



4- Enter a URL for a non-blocked site



Result:









Test Case sbs_5: Verify page redirect when visiting an offensive site

Steps: Expected Results:

Using the same policy as Test Case 4, attempt to - Verify you are redirected to a BLOCKED 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

-Check CPU usage for rfcd specifically









2

Result:









Test Case sbs_6: Verify Consistent Page load of offensive and none offensive sites

Steps: Expected Results:

1. Continue to open new tabs in your browser or new - Check that client behaves per policy.

windows and alternate between visiting blocked and Page load time for both non-blocked sites and the

non-blocked sites. redirect page meet acceptable time. [3-5 seconds or

2. Check CPU usage on test machine as this is so]

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:

Verify the RFC agent is functioning correctly

RFC should function properly after waking from

Put the machine into hibernation

hibernation.

Wake the machine



Result:









Test Case sbs_-8: Verify RFC Filters when computer wakes up from sleep

Steps: Expected Results:

1- Surf and make sure RFC is filtering as it should RFC should continue to filter when computer wakes

2- Put laptop to sleep up from sleep.



Mac:

Activity Monitor shows rfcd running, Console logs

don’t show any RFS connection errors.

Result:









Test Case sbs_-9: Verify RFC Filtering – Network Transition









3

Steps: Expected Results:

Disconnect from wired and enable wireless, or

disable wireless and connect to wired RFC should continue to function after transitioning

between networks.

Note: any changes in CPU usage that may occur as a

cause of network changes.

Result:









Test Case sbs_-10: Verify Other applications/tools are operable when the RFC is installed.

Steps: Expected Results:

1-Load Mac specific applications like iDisk, iTunes,

iLife, iWork, etc and verify they function correctly -RFC continued to filter user traffic

2-Load chat applications -RFC CPU usage remains low

3-Load any other application/tool that you use and -Application/chat functionality is not hindered by RFC

verify the RFC continues to function correctly.



Please spend some time exercising those apps while

the RFC is installed

Result: If you find a conflict with RFC, please note application name and version.









Test Case sbs_11: Verify Filtering under Captive Portal

Steps: Expected Results:

Visit a Starbucks or other institution where WiFi is Non-offensive sites should be unobstructed;

provided offensive sites should be redirected by RFC.

Start the PC and make sure RFC is running Note, These sites should be obstructed by RFC not

Login to the institution's authorization page other filtering agent.

Surf to offensive and non-offensive sites take a note of CPU usage for rfcd



Result:









Test Case sbs_12: Verify software updates are not obstructed by the RFC

Expected Results:

Steps:

Go to the apple menu and Click on Software Updates

Mac Software updates should not be obstructed by

Your system will be check for software updates, click

the RFC

on yes to install any suggested.









4

Result:









Test Case sbs_13: 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 Mac 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_14: 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 using Activity Monitor

2. Page load time



Compare times with RFC loaded to times noted in

Test Case 1

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



Other docs by cuiliqing
7 Recipes from Joe A.
Views: 2  |  Downloads: 0
Re-installingXPMode
Views: 3  |  Downloads: 0
telefonica_en
Views: 4  |  Downloads: 0
3220 Chap 6 demos
Views: 2  |  Downloads: 0
chap history.docx
Views: 3  |  Downloads: 0
Subcontractor Bid Form - The Fountains
Views: 1  |  Downloads: 0
English
Views: 1  |  Downloads: 0
DESIGNER'S SCHEDULE USE
Views: 1  |  Downloads: 0
Security Service Providers
Views: 45  |  Downloads: 0
By registering with docstoc.com you agree to our
privacy policy

You are almost ready to download!

You are almost ready to download!