Test Planx - HEAnet Mirror Service

rabidwestvirginiaNetworking and Communications

Oct 26, 2013 (3 years and 10 months ago)

93 views

1

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Test plan

Introduction

The test plan submitted with
Memba Velodoc Outlook Add
-
In
is kept minimal so as to be easy to
reproduce. We have unit tests which rely on Visual Studio Unit Testing framework and simple
manual test cases
.

Test environment
s

Prerequisites

The prerequisites for running
Memba Velodoc Outlook Add
-
In
and the
corresponding
tests are
:

1.

Windows XP, Windows 2003, Windows Vista or Windows 2008;

2.

Office 2003 or Office 2007

3.

Visual Studio 2008 (only for the unit tests)

Settings up file tran
sfer
server
platforms

Please refer
to the “Installation Guide” which explains how to set up compatible file transfer server
platforms.
We assume here that file transfer server platforms are up and running.

Test environment
s

The test

environments
we are usi
ng for
testing
Memba Velodoc Outlook Add
-
In
are:

Env. 1



Windows XP + Office 2003 + latest service packs and windows updates



LAN connection to the Internet



Hotmail or Gmail email address



File transfer platforms on the LAN

(except Velodoc.net and Amazon S3)

Env. 2



Windows Vista + Office 2003 + latest service packs and windows updates



LAN connection to the Internet



Hotmail or Gmail email address



File transfer platforms on the LAN

(except Velodoc.net and Amazon S3)

Env. 3



Windows
Vista

+ Office 2007 + latest
service packs and windows updates



LAN connection to the Internet



Hotmail or Gmail email address



File transfer platforms on the LAN

(except Velodoc.net and Amazon S3)

Env 4



Windows 2008 Std + Office 2007 + latest service packs and windows updates



LAN
connection to the Internet



Hotmail or Gmail email address



File transfer platforms on the LAN (except Velodoc.net and Amazon S3)

2

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Env 5



Download
Mi
crosoft Exchange 2007
SP1
VHD


32 bi瑳




Add

Office 2003 + latest service packs and windows updates



Add
Visual Studio 2008



LAN connection to the Internet



Exchange mailbox



File transfer platforms on the LAN (except Velodoc.net and Amazon S3)

These test env
ironments are all set

up as virtual machines

and localized in International English
.

Environments 1 to 4 are used for manual test cases. Environment 5 is used
both for manual tests and

unit tests.

Important
limitations

We would need more test environments especially to
consider
:



Localized (non
-
English) versions of Windows

and Office
,



64
-
bit platforms,



File transfer platforms
of various brands
located on the Internet

(for example our current
tests are only completed with IIS FTP Server and not FTP servers from other brands)
,



Proxies and firewalls,



Spam/phishing filters
,



Highly secured client deployments (where active directory policies really limit what a user
can do)
.

Bug reports

All defects and suggestions should be reported to
http://www.codeplex.com/velodocaddin/Thread/List.aspx

after checking that you are not adding a
duplicate.

Any bug report s
hould include
:



A description of the environment (Windows and Office version, mail server, firewall, ...);



Steps to reproduce the defect;



a copy of the trace which you can obtain either by configuring a trace listener in an
app.config file

as described in
http://msdn.microsoft.com/en
-
us/library/system.diagnostics.textwritertracelistener.aspx

or by
run
ning

Systernal’s
D
ebugView

while executing the application:

3

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.



Units tests

All unit tests reside in the
Unit
Tests project of the Velodoc
Outlook Add
-
In

solution.

You may want to
add the “Full Class Name” column to the list to make it easier to manage your test fixtures in the
Test View.


Before running
the
unit tests

in the Visual Studio
environment
, you need to configure
them

to match
the file transfer platforms

which
you have deployed as per the “Installation Guide”.

For this purpose
4

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


each plug
-
in test class file (e.g. FTPPlugInTest
.cs
) contains private helpers which return plug
-
in
settings as a NameValueCollection. You need to adapt these settings to your own co
nfiguration.

Note that the unit tests transfer the files in the “My Music” and in the “My Pictures” folders. This is
coded

in
TransferBuilderDataHelper.cs.



Manual

test

case
s

We recommend you look at the video located at
http://silverlight.services.live.com/invoke/66737/VelodocAddIn/iframe.html

(high definition
-

requires Silverlight) or
http://www.youtube.c
om/watch?v=0c
-
qivirz8Q

(low definition


requires
Flash)
before running the tests. This video
quickly demonstrates

how the software works

which
should be helpful since th
e

following test
cases

do not include screenshots
.

The following test cases should

respectively be completed
in the various
test
environments
described above
, which include several versions of Windows and Office
.

IMPORTANT:
All test

case
s should be executed under a user account which is only member of the
User
s

group

or Power User
s

grou
p
.

Running tests as an Administrator account is pointless.

5

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Test case 1: Installation

Standard course of action
s
:

Download the setup archive

from
http://www.codeplex.com/velodocaddin

and
extract in a directory

Setup archive download
ed

and extracted

Run setup.exe

from the extraction directory
and
accept Microsoft licenses

Note: on Vista with UAC, you may have to allow
several actions to continue.

Setup executes and:



Installs
.Net F
ramework 3.5



Installs Memba.Update.exe



Installs Office Interop Assemblies



Installs VSTO runtime



Displays the Velodoc installer

Follow the procedure in the Velodoc Installer,
answer each question and click Next, the
n

click
Finish to confirm the installation

Velodoc Installer successively displays:



A welcome screen



A prerequisites screen



A license information screen



An installation folder screen



A confirm installation screen



A progress bar



A read me screen



A
completion

screen

Go to Control Panel
-
> Add or Remove Programs
(Programs and Features in Vista) and check
installed features

Check that you have entries for:



.Net Framework 3.5



Memba Software Updates



Office
Primary
Interop Assemblies

(not
listed if Office has been installed with
.NET programmability)



VSTO runtime



Memba Velodoc Outlook Add
-
In

Open a
W
indows
E
xplorer and
check that
required
directories have been created



Memba Software Update always installs
in

%ProgramFiles%
\
Memba
\
Upd
ate
\




Velodoc Outlo
ok Add
-
In installs in

%ProgramFiles%
\
Memba
\
Velodoc
\
Outl
ook Add
-
In
\


by default but this
directory can be changed.

Launch regedit.exe and open
HKLM
\
SOFTWARE
\
Memba
\
Velodoc
\
Controller



Check that you have two values named
path and process
. The path should
resolve

to an existing executable
.

6

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Open the task scheduler and run the

Me浢a
Sof瑷are UpTa瑥


瑡Vk



Check that you have a task scheduled
every two weeks to launch
Memba.Update.exe



Check that the

Me浢a Sof瑷are
UpTa瑥


瑡Vk execu瑥V

Open PinTowV Firewall



Check that
Memba.Transfer.Controller.exe is
unblocked

If you have installed the .NET framework SDK,
open
"C:
\
Program
Files
\
Microsoft.NET
\
SDK
\
v2.0
\
Bin
\
mscorcfg.msc"



Check
that
runtime access policies
have
been created
under Machine
-
>

Code
Groups
-
> All_Code
-
>
My_Computer_Zone

-
>
Memba.Transfer.1

for each assembly
located in the installation directory

Go to Start menu
-
> All Programs and click
each
of
the newly added menu items

Do the same with the newly added Desktop
icons.



Click
“Memba Velodoc File Transfer
Suite” and check that a new dialog
TiVplaXV wi瑨 an orange accorTion. 䍬ick
瑨e TownloaT bu瑴onV anT cUeck 瑨a琠
瑨e linkV are valiT.



Click Memba Velodoc
-
> Open Add
-
In
Documentation
Folder
and check that
the documentation fold
er opens in a
windows explorer



Click Memba Velodoc
-
> Memba
Velodoc
Transfer Controller and check
that a new tray icon

loads

in the
windows task bar

(you may have to
unblock the controller in Windows
Firewall)
.



Click Memba Velodoc
-
> Velodoc Add
-
In
Communi
ty on Codeplex and check that
a Codeplex opens in a new browser
window.

7

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Alternate courses of actions:

1.

Change the installation
directory

(include Unicode characters)

2.

Select GPL License or MEMBA EULA

(
the
Memba EULA requires the purchase of a license
number
)

3.

Do some guerrilla testing by cancelling and restarting setup
, uninstalling and re
-
installing, ...

Known issues:



In some instances, the install of prerequisites fails with a message “operation cancelled by
the user”.
In 瑨iV caVe, V
i浰lX V瑡r琠Ve瑵p
again.



The programmatic configuration of Windows firewall does not seem to work
on

Vista

which
requires to manually unblock the controller
.

Test case 2: Configuration

Standard course of action
s
:

T
he following course of actions depends on the file transfer

server platform used and should be
completed successively with:



Velodoc Enterprise Edition,



Velodoc XP Edition,



An FTP server,



A Microsoft BITS server,



A UNC file share,



An Amazon S3 account.

Open
Memba Velodoc Transfer Controller

fr
om
Start
menu
-
> All
Programs
-
> Memba Velodoc

A new tray icon is displayed in the task bar
.

Right click the tray icon and click Open in the
contextual menu

The monitor dialog of the controller is
displayed

Select menu File
-
> Account Settings

The account settings dialog is
displayed

Click the button with a green cross icon in the toolbar

A new account dialog is displayed

8

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Name your account “My [X] account” where [X]
correVponTV 瑯 瑨e plug
-
in Velec瑥T, 瑨en click OO:



[X] = “Velodoc” for Velodoc Enterprise Ed.



[X] = “XP” for

VeloToc XP NTi瑩on



[X] = “FTP” for an FTP Server



[X] = “BITS” for a Microsoft BITS account



[X] = “UNC” for a UNC file Share account



[X] = “S3” for an Amazon S3 account

The new “My [X] account” is added to the
liV琠on 瑨e lef琠of 瑨e accoun琠Ve瑴ingV Tialo
g

anT iV Velec瑥T
.

䍨eck 瑨a琠瑨e na浥 of 瑨e firV琠瑡b
TiVplaXeT on 瑨e rigU琠
wUicU
iTen瑩fieV
瑨e

plug
-


TeVigna瑥T bX 瑨e
Velec瑥T
accounW
:



“Velodoc


for VeloToc Nn瑥rpriVe
NT.



“WCF” for Velodoc XP Edition



“FTP”= FTP for an FTP Server



“BITS”

= BITS for a MicroVof琠BITS
accounW



“UNC”

= UN䌠for a UN䌠file SUare
accounW



“Amazon S3”

= S3 for an A浡zon
S3 accounW

䍯nfigure:



The host (if applicable)



Upload and/or download paths (if applicable)



The username, password, access key, secret
key and/or email (if applicable)



Proxy settings (if applicable)

Then click the
Test

button.

For more information,
follow

the

InV瑡lla瑩on GuiTe

.

If accoun琠Ve瑴ingV are valiT a 浥VVage box
should confirm “Plug
-
in settings are valid”.

If accoun琠Ve瑴ingV are invaliT
, a 浥VVage
box VUoulT TiVplaX an error 浥VVage.


PUen Xou are Tone configuring accoun瑳, cloVe 瑨e
accoun琠Ve瑴ingV Tialog box.

If Xou Uave no琠VaveT, a 浥VVage box
VUoulT warn Xou 瑯 Vave Xou cUange
V. 䍬ick
QeV anT reopen 瑨e accoun琠Ve瑴ingV 瑯
cUeck 瑨a琠Xou cUangeV Uave been
co浭m瑴eT anT reloaTeT.

Selec琠浥nu File
-
> Op瑩onV

TUe op瑩onV Tialog iV TiVplaXeT.

Select option “Always”

in 瑨e Op瑩onV Tialog anT click
OO. Re
-
open 瑨e Tialog 瑯 cUeck 瑨a琠瑨e valueV Uave
cUangeT.

䍬ick 䍡ncel 瑯 cloVe.

C
Ueck 瑨a琠瑨e valueV Uave cUangeT.

RigUW
-
click 瑨e 瑲aX icon anT click Nxi琠in 瑨e con瑥x瑵al
浥nu
.

Me浢a
VeloToc
TranVfer 䍯n瑲oller ex

V
.

Qou can confir洠瑨
a琠瑨e proceVV iV no
浯re liV瑥T in

瑨e PinTowV TaVk Manager
(䍴Cl + SUif琠+ NVc).

9

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Launch regedit.exe and open
HKCU
\
Software
\
Memba
\
Velodoc
\
Controller
\
Accounts

Check that your account settings have been
properly registered
.

Launch r
egedit.exe and open
HKCU
\
Software
\
Memba
\
Velodoc
\
Controller
\
Options

Check that your options have been properly
registered.

Alternate courses of actions:

1.

Open account settings by opening a new message inspector in Outlook and clicking menu
item “Add/Edit
Package” from the popup button of the Velodoc command bar (Outlook
2003) or ribbon (Ou瑬ook 2007). No瑥 瑨a琠瑨iV 浥nu i瑥洠onlX TiVplaXV accoun琠Ve瑴ingV if
瑨ere iV no accoun琠configureT;



Open account settings by opening a new message inspector in Outloo
k and clicking menu
item “Account settings” from the popup button of the Velodoc command bar (Outlook 2003)
or ribbon (Ou瑬ook 2007);



Test host
s

which do not exist

4.

Test wrong credentials

5.

Test inadequate proxy settings

6.

Do some guerrilla testing by adding an
d removing accounts,
modifying
and saving
accounts,
renaming account
s
,
switching between accounts,

closing and re
-
opening dialogs.

Test case 3: Sending a message with a non
-
compressed package

Standard course of action
s
:

Open Outlook

The main Outlook
explorer is displayed

Select menu
File
-
>
New Message

A new message inspector is displayed with a new
Velodoc command bar (Outlook 2003) or a new
ribbon popup button (Outlook 2007).
Note that
if you are using a virtual machine, some icons
may not display in

the Outlook 2003 command
bar.

Click the popup button and select menu
“Add/edit package”

The Velodoc package editor is displayed

Name your package “My package” and c
lick
button “Add files”

The open file dialog is displayed

S
elect files (multi
-
selection

should be enabled)
and click OK
.

Selected f
iles are displayed with their icons in
the package editor dialog
.

Click Save, then click Cancel to c
lose the package
editor
.

A new attachment name
d

“My package.velodoc”
is added to the Outlook message

10

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Click the

popup button and select menu
“Add/edit package” or double
-
click “My
package.velodoc” in the list of attachments to

-
open 瑨e package anT confir洠瑨a琠Xour
cUangeV Uave been VaveT.

Selec瑥T fileV are TiVplaXeT wi瑨 瑨eir iconV in
瑨e package eTi瑯r Tial
og.

ReVize 瑨e package eTi瑯r Tialog

TUe package eTi瑯r Tialog VUoulT reVize properlX.

SelecW

file
V in 瑨e liV琠anT rigUW
-
click

瑯 TiVplaX WUe
con瑥x瑵al 浥nu. Selec琠Re浯ve 瑯 re浯ve 瑨e
Velec瑥T fileV.


FileV are re浯veT fro洠瑨e
package eTi瑯r
liVW
.

Selec琠瑨e accoun琠瑨a琠will be uVeT 瑯 VenT 瑨e
package in 瑨e V瑡瑵V bar.

Accoun琠Velec瑥T.

䍬ick 瑨e cloVe box repreVen瑥T bX a croVV in 瑨e
瑩瑬e bar

A 浥VVage box TiVplaXV a warning invi瑩ng Xou 瑯
Vave Xour cUangeV. 䍬ick QeV.

Open 瑨e
Me浢a VeloTo
c TranVfer 䍯n瑲oller


浯ni瑯r 瑨e package being Ven琠(TraX Icon
-

Open).

TUe 浯ni瑯r winTow of 瑨e 瑲anVfer con瑲oller iV
TiVplaXeT.

ATT recipien瑳, a Vubjec琠anT a boTX 瑯 Xour
Ou瑬ook 浥VVage, 瑨en click 瑨e SenT bu瑴on.

TUe 浥VVage iV aTTeT 瑯 瑨e
Ou瑢ox

anT 浯veV
瑯 瑨e Sen琠I瑥浳 af瑥r being Ven琠(瑨iV iV 瑨e
Ou瑬ook V瑡nTarT uVe caVe).

䍨eck 瑨e progreVV
barV in 瑨e 浯ni瑯r winTow.

Go 瑯 Xour Sen琠I瑥浳 in Ou瑬ook anT cUeck Xour
浥VVage.

䍨eck 瑨a琠
an aTver瑩Ve浥n琠UaV been inVer瑥T
a琠瑨
e

瑯p o

瑨e


V
Vage
. 䍨eck 瑨a琠linkV Uave
been aTTeT a琠瑨e bo瑴o洠of 瑨e 浥VVage.

Make
Vure 瑨a琠瑨e fileV aTTeT are liV瑥T anT 瑨a琠瑨e
fileV re浯veT are no琠liV瑥T.

TrX 瑨e linkV. Open
瑨e VeloToc package wUicU VUoulT be reaT
-
onlX
af瑥r being Ven琮

Nxi琠OuW
look

䍨eck 瑨a琠bo瑨 Ou瑬ook anT
PinPorT

(for
Ou瑬ook 2003) proceVVeV are no 浯re liV瑥T in
瑨e PinTowV 瑡Vk 浡nager (䍴Cl + SUif琠+ NVc)

11

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Alternate courses of actions:

1.

Test with as many file types
, large sizes (i
mportant)

and names (Unicode) as possible

2.

Test with various mail servers including Exchange mailboxes

3.

Test with various configurations of Outlook:

a.

In Outlook 2003, the word editor can be enabled or disabled in Tools
-
> Options
-
>
Mail Format and there are 3 types of message bodies: HTML, RTF and
plain text.
When rich text (HTML or RTF) is edited with Word, the Velodoc add
-
in uses the
Word API to insert links in the body. When the message is plain text, the Velodoc
add
-
in modifies the body directly whether Outlook is configured to use Word or not.

When Outlook is configured not to use Word and the message is HTML, the Velodoc
add
-
in inserts the links as HTML directly. When Outlook is configured not to use
Word and the message is RTF, the Velodoc add
-
in reverts to plain text.

b.

In Outlook 2007, the w
ord editor is always enabled and there are only two options:
rich text (RTF or HTML) and plain text. When the message is rich text, the Velodoc
add
-
in uses the Word API to insert links in the body. When the message is plain text,
the Velodoc add
-
in modifi
es the body directly without using the Word API.

4.

Save as draft, r
eply to, resend and forward messages which have Velodoc attachments.

5.

Do some guerrilla testing, pausing and resuming transfers, cancelling transfers, exiting the
Memba Velodoc Transfer Contro
ller

or shutting down Windows
in the middle of a transfer,
running several transfers at the same time, ...

Test case 4: Receiving a message with a non
-
compressed package

Standard course of action
s
:

This
test case assumes that you have received a message w
ith a Velodoc
package according to t
est
case 3.

Open your inbox in Outlook and open the
received message containing a Velodoc package
in a new inspector window.

A new message inspector is displayed with a new
Velodoc command bar (Outlook 2003) or a new
ribbon popup button (Outlook 2007).

Click the links in the message body to download
the files

(Note: this is the preferred mode if the
recipient does not have the

Memba Velodoc
Outlook Add
-
In)
.

Check that
the links are resolved and that
you
can get each file.

Open the Velodoc package either by double
-
clicking it in the list of attachments or by calling
menu Add/Edit package from the Velodoc
c
ommand bar (O
utlook 20
0
3
) or the popup
button in the ribbon (Outlook 2007).

The Velodoc Package Editor displays the list of
files in the package. Check that the package is
read
-
only.

In particular, try dragging and
dropping files onto the list of files in the package
editor.

12

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


O
pen the
Memba Velodoc Transfer Controller

to
monitor the
files

being
downloaded

(Tray Icon
-
>
Open).

The monitor window of the transfer controller is
displayed.

Select files in the list and right
-
click to display the
contextual menu. Select Download to
download
the selected files

(Note: this is the preferred
mode if the recipient does have the Memba
Velodoc Outlook Add
-
In).

Either the plug
-
in uses a
registered protocol
handler

t
o download files and in this case the
package editor launches the corresponding
application (generally the web browser) to
process the download, or the plug
-
in actually
processes the download which can be monitored
in the transfer controller.

Right
-
click
to display the contextual menu in the
package editor
and select Open Folder.

A windows explorer displays the content of the
download folder
as
defined in Options (menu
File
-
>Options in the transfer controller).

Your
downloaded
files should
be found

in this

folder
.

Close the message inspector

after closing the
package editor.

Message inspector

closes.

[In Office 2007 on Vista

only
: preview handlers
are not supported on other platforms
]

Select your received message with a package in
the Inbox explorer. In
the preview pane, select
the .velodoc attachment and click the Preview
button.

The Velodoc preview handler displays the
package within the Outlook interface.

[In Office 2007 on Vista only: preview handlers
are not supported on other platforms]

Play with t
he contextual menu to download files
and open the download folder.

Files are downloaded using a registered protocol
handler (generally the browser) or the
appropriate plug
-
in.

Exit Outlook

Check that both Outlook and
WinWord

(for
Outlook 2003) processes are no more listed in
the Windows task manager (Ctrl + Shift + Esc)

13

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Alternate courses of actions:

1.

Do some guerrilla testing, pausing and resuming transfers, cancelling transfers, exiting the
Memba Velodoc Transfer Controller

in the middle of a transfer, running several transfers at
the same time, ...

2.

Play with .velodoc package files. Drag them to windows explorers, to Outlook new messages,
send them, etc.

3.

Test the preview handler in Windows Explorer (use a preview pane) after

copying a .velodoc
file to the file system.

Known issues:



Zip archives are not U
nicode
; they use code pages which is fine if the sender and recipient
use the same code page, but which raises issues otherwise.



If your links contain IP addresses like in
ftp://10.0.0.12/Download/myfile.txt
, this may trigger
the Outlook phishing filter. Prefer the use of fully qualified domain names (FQDN’s).

Test case 5: Sending a message with a compressed and encrypted pa
ckage

Standard course of action
s
:

Open Outlook

The main Outlook explorer is displayed

Select menu File
-
>New Message

A new message inspector is displayed with a new
Velodoc command bar (Outlook 2003) or a new
ribbon popup button (Outlook 2007).

Click th
e popup button and select menu
“Add/edit package”

The Velodoc package editor is displayed

Name your package “My package”


Drag and drop a hierarchy of files into the
package editor
. Make sure the hierarchy
contains duplicates (same file name in a
different
folder of the hierarchy).

The files are added to
the package editor
.

Click the close box represented by a cross in the
title bar

A message box displays a warning inviting you to
save your changes. Click Yes.

A second message warns you of duplica
tes and
informs you that compression has been enabled.
Click OK.

Drag and drop a
couple of
file
s

into your Outlook
message

(not the package editor).

Since you already have a package, you get a
message offering you to add the new files to the
current
package. Accept.

14

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Click the popup button and select menu
“Add/edit package” or double
-
click “My
package.velodoc” in the list of attachments to

-
open 瑨e package anT confir洠瑨a琠new fileV
Uave been aTTeT.

䍨eck 瑨
a琠new

fileV Uave been aTTeT 瑯 瑨e
pac
kage
.

Selec琠瑨e accoun琠瑨a琠will be uVeT 瑯 VenT 瑨e
package in 瑨e V瑡瑵V bar.

Accoun琠Velec瑥T.

䍬ick 瑨e cloVe box repreVen瑥T bX a croVV in 瑨e
瑩瑬e bar

TUe package eTi瑯r cloVeV wi瑨ou琠anX 浥VVage.

Open 瑨e
Me浢a VeloToc TranVfer 䍯n瑲oller


浯ni瑯r 瑨e package being Ven琠(TraX Icon
-

Open).

TUe 浯ni瑯r winTow of 瑨e 瑲anVfer con瑲oller iV
TiVplaXeT.

ATT recipien瑳, a Vubjec琠anT a boTX 瑯 Xour
Ou瑬ook 浥VVage, 瑨en click 瑨e SenT bu瑴on.

TUe 浥VVage iV aTTeT 瑯 瑨e Ou瑢ox anT 浯veV

瑨e Sen琠I瑥浳 af瑥r being Ven琠(瑨iV iV 瑨e
Ou瑬ook V瑡nTarT uVe caVe). 䍨eck 瑨e progreVV
barV in 瑨e 浯ni瑯r winTow.

Go 瑯 Xour Sen琠I瑥浳 in Ou瑬ook anT cUeck Xour
浥VVage.

䍨eck 瑨a琠an aTver瑩Ve浥n琠UaV been inVer瑥T
a琠瑨e 瑯p of
瑨e

浥VVage. 䍨eck

瑨a琠
a Vingle
link
瑯 瑨e co浰reVVeT arcUive UaV

been aTTeT
a琠瑨e bo瑴o洠of 瑨e 浥VVage. TrX 瑨e linkV.
Open 瑨e VeloToc package wUicU VUoulT be
reaT
-
onlX af瑥r being Ven琮

Nxi琠Ou瑬ook

䍨eck 瑨a琠bo瑨 Ou瑬ook anT PinPorT (for
Ou瑬ook 2003) proceVVeV
are no 浯re liV瑥T in
瑨e PinTowV 瑡Vk 浡nager (䍴Cl + SUif琠+ NVc)

15

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Alternate courses of actions:

1.

Test with as many file types
, large sizes (important)

and names (Unicode) as possible

2.

Test with various mail servers including Exchange mailboxes

3.

Test with
various configurations of Outlook:

a.

In Outlook 2003, the word editor can be enabled or disabled in Tools
-
> Options
-
>
Mail Format and there are 3 types of message bodies: HTML, RTF and plain text.
When rich text (HTML or RTF) is edited with Word, the Velod
oc add
-
in uses the
Word API to insert links in the body. When the message is plain text, the Velodoc
add
-
in modifies the body directly whether Outlook is configured to use Word or not.
When Outlook is configured not to use Word and the message is HTML, th
e Velodoc
add
-
in inserts the links as HTML directly. When Outlook is configured not to use
Word and the message is RTF, the Velodoc add
-
in reverts to plain text.

b.

In Outlook 2007, the word editor is always enabled and there are only two options:
rich text
(RTF or HTML) and plain text. When the message is rich text, the Velodoc
add
-
in uses the Word API to insert links in the body. When the message is plain text,
the Velodoc add
-
in modifies the body directly without using the Word API.

4.

Save as draft, r
eply t
o, resend and forward messages which have Velodoc attachments.

5.

Do some guerrilla testing, pausing and resuming transfers, cancelling transfers, exiting the
Memba Velodoc Transfer Controller

or shutting down Windows
in the middle of a transfer,
running
several transfers at the same time, ...

Test case 6: Receiving a message with a compressed and encrypted package

Standard course of action
s
:

This
test case assumes that you have received a message with a Velodoc package according to test
case 5.

Open you
r inbox in Outlook and open the
received message containing a Velodoc package
in a new inspector window.

A new message inspector is displayed with a new
Velodoc command bar (Outlook 2003) or a new
ribbon popup button (Outlook 2007).

Click the link in the

message body to download
the compressed archive (Note: this is the
preferred mode if the recipient does not have
the Memba Velodoc Outlook Add
-
In).

Check that the links are resolved and that you
can get the archive.

Open the Velodoc package either by dou
ble
-
clicking it in the list of attachments or by calling
menu Add/Edit package from the Velodoc
command bar (Outlook 2003) or the popup
button in the ribbon (Outlook 2007).

The Velodoc Package Editor displays the list of
files in the package. Check that th
e package is
read
-
only. Make sure you have the same number
of files when opening the archive with WinZip or
WinRar.

16

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Open the
Memba Velodoc Transfer Controller

to
monitor the files being downloaded (Tray Icon
-
>
Open).

The monitor window of the transfer
controller is
displayed.

Select files in the list and right
-
click to display the
contextual menu. Select Download to download
the selected files (Note: this is the preferred
mode if the recipient does have the Memba
Velodoc Outlook Add
-
In).

Either the plu
g
-
in uses a
registered protocol
handler

to download files and in this case the
package editor launches the corresponding
application (generally the web browser) to
process the dow
nload, or the plug
-
in actually
processes the download which can be monitored
in the transfer controller.

Right
-
click to display the contextual menu in the
package editor and select Open Folder.

A windows explorer displays the content of the
download folde
r defined in Options (menu File
-
>Options in the transfer controller). Your
downloaded
files should
be found

in this folder
.

Close the message inspector after closing the
package editor.

Message inspector

closes.

[In Office 2007 on Vista only: preview han
dlers
are not supported on other platforms]

Select your received message with a package in
the Inbox explorer. In the preview pane, select
the .velodoc attachment and click the Preview
button.

The Velodoc preview handler displays the
package within the Out
look interface.

[In Office 2007 on Vista only: preview handlers
are not supported on other platforms]

Play with the contextual menu to download files
and open the download folder.

Files are downloaded using a registered protocol
handler (generally the bro
wser) or the
appropriate plug
-
in.

Exit Outlook

Check that both Outlook and WinWord (for
Outlook 2003) processes are no more listed in
the Windows task manager (Ctrl + Shift + Esc)

17

Copyright © 200
7
-
200
8

Memba SA
. All rights reserved.


Alternate courses of actions:

1.

Do some guerrilla testing, pausing and resuming transfers, cancelling transfers, exiting the
Memba Velodoc Transfer Controller

in the middle of a transfer, running several transfers at
the same time, ...

2.

Play with .velodoc package files. Drag them to windo
ws explorers, to Outlook new messages,
send them, etc.

3.

Test the preview handler in Windows Explorer (use a preview pane) after copying a .velodoc
file to the file system.

Known issues:



Zip archives are not U
nicode
; they use code pages which is fine if the
sender and recipient
use the same code page, but which raises issues otherwise.



If your links contain IP addresses like in
ftp://10.0.0.12/Download/myfile.txt
, this may trigger
the Outlook phishing filter
. Prefer the use of fully qualified domain names (FQDN’s).