ShopSite Screen Flow:
a Guide for Linguistic Testers


Introduction

This document outlines the functional flow of the ShopSite User Interface. It is not meant to be a test procedure for functional test or linguistic test. The goal is to provide a complete list of screens in each of the different ShopSite products, so that people testing a translation don't have to go through all the functionality for each product (that is, screens that are identical across products can be easily identified).

Part I of this document provides general information for preparing the test environment. Part II contains the list of screens. Part III explains how to test the ShopSite online help.


PART I

Goals

The goal of this document is to guide the linguistic tester through the ShopSite screens in such a way as to display all the screens, at least once, in a complete manner.

Audience

This document is addressed in particular to the tester responsible of the linguistic test of a localized version of ShopSite. In addition to knowledge of the language, this document assumes that the testers are familiar with web browsers and applications.

Linguistic Verification

It is assumed that the testers have detailed test cases to guide them through all the linguistic checking. The following are minimal quality criteria:

Testers are encouraged to work closely with Open Market regarding any problems that might prevent achieving a quality translation.

Test environment

This document does not contain instruction on how to install and configure ShopSite. The assumption is that the testers can access ShopSite SC and ShopSite TX systems that already have the test language installed.

What it is needed?

These are the pre-requisites testing:

In addition, the tester should have available the following items:

The ShopSite administrator, for both SC and TX, should provide the testers with the following information:

Basic Flow

There are two users accessing ShopSite screens:

The merchant access the Store Configuration interface to configure and change the store settings, while the buyer access the store front and makes purchases.

The ShopSite administrator should provide the two URLs for testing. They look like these:

The merchant URL provides access to the main ShopSite screen, from which all other screens are accessible. Depending on the particular product, Pro or Manager or Lite or Express, some screens will be visible and some will not. ShopSite Pro contains almost 90% of all screens, therefore the main list of screens is based on this product. For the other products, a list of different screens is provided. Because of the differences between ShopSite SC and TX, two lists of screens are provided in this document: the full set of screens for SC and only the different ones for TX.

Files structure

ShopSite SC

In the ShopSite Images directory there are locale directories for each English locale that come with the default product, such as en-US. If there is not already, create a directory with the locale you are translating to, for example for French fr-FR – here you will copy all the translated images following the same structure as in the en-US directory.

In the HTML Output Directory there is a /media directory where the images are kept. You should replace them with your translated images.

In the ShopSite Directory, in the directory /ss there is the file localeinfo.dat which contains the locale definitions. You should add an entry for the locale you are translating to. It is a text file, follow the instructions in the comments at the top of the file.

In the first screen of the wizard of your store, in the field Choose your language you should select the language you are translating to. From this point on you should see all the translated screens and images.

ShopSite TX

ShopSite TX requires two servers: the ShopSite server and the Transact server.

For both SC and TX, make sure you have an entry for your locale in the file localeinfo.dat as explained above.

Message catalog compilation

The source for the message catalog ShopSiteMsg.cat are .msg files that come with your localization kit. A Makefile is provided along with these files. Once the files have been translated, just run make from the directory where the msg files and the Makefile are located. Then copy the output file in your locale directory as explained above.


Part II

List of Screens in ShopSite SC Pro

The screens are referenced by the title as it appears in the browser page. Some screen names change when clicking on buttons; in this case the button name is referenced between parenthesis.

ShopSite SC Mgr

This is the delta from SC Pro version.

No additional or different screens.

ShopSite SC Lte

This is the delta from SC Pro version.

ShopSite SC Exp

This is the delta from SC Pro version.

No additional or different screens.

ShopSite TX Pro

This is the delta from SC Pro version.

Many of these screens are the screens found in the screen_packs directory of the localization kit, and they show the filename at the bottom. There are some screens for which the body comes from the Transact server and the head comes from ShopSite. For these screens only the head should be linguistically checked since the body has already been verified in Transact; these screens are identified in the list below with (TX) aside the screen name.

Please note: the set of screens of Commerce Setup have all the same screen title, so in the list below they have been referenced with the filename that is visible at the bottom.

ShopSite TX Mgr

This is the delta from TX Pro version.

No additional or different screens

ShopSite TX Lte

This is the delta from TX Pro version.

No additional or different screens

ShopSite TX Exp

This is the delta from TX Pro version.


PART III

Help files

Because the help files for all ShopSite products are produced from a single set of source files, you can verify greater than 90% of the help text by viewing the ShopSite SC Pro and ShopSite TX Pro help. Rather than viewing the help for each product screen, you can simply sequentially open the files in each help directory.