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:
- Completeness of the translations: no English words should appear in the screens and messages except words that do not require translation or words that cannot be translated because of a problem in the software.
- Accuracy of the translations: no grammar, syntax, spelling errors or semantic errors in translating technical terms, and consistency with the glossary.
- Consistency of the translations: terms with the same meaning should be translated in the same way in all screens, messages, images and online help.
- Box sizing and general look: the screens should look like the original English screens with appropriate box re-sizing.
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:
- ShopSite SC installed on a Unix system
- ShopSite TX installed on a Unix system
- ShopSite SC stores for each of the languages
- ShopSite TX stores for each of the languages
- A Transact system with the translated Smart Pages (if available for that language)
In addition, the tester should have available the following items:
- A PC with a Web browser in the language that is being tested (either Microsoft Internet Explorer version 4 or later, or Netscape Navigator/Communicator version 4 or later)
- A functional e-mail account
- Access to the ShopSite help, whether on www.shopsite.com or another server (even if it is not required, it might be helpful)
The ShopSite administrator, for both SC and TX, should provide the testers with the following information:
- The URLs to the merchant interface and the store fronts for both ShopSite SC and TX stores
- The Store ID and password for each store, for both SC and TX
- Merchant username, password, security checkpoint for each store in TX
- ShopSite Host Administrator username and password (for TX, for the screen_pack command)
Basic Flow
There are two users accessing ShopSite screens:
- Merchant
- Buyer
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:
- for the merchant http://system:port/cgi-bin/ss/start.cgi
- for the buyer http://system:port/storeID/index.html
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.
- ShopSite Server
In the ShopSite CGI directory, in /nls sub-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: copy the translated message catalogs into that directory. The message catalogs are the same for ShopSite SC and TX.
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 than the en-US. These images are the same as in ShopSite SC.
In the HTML Output Directory there is a /media directory where the images are kept. You should replace them with your translated images. This is the same in ShopSite SC.
- Transact Server
In order to run ShopSite TX you need a Transact installation up and running. Locate the tms-ts directory of your Transact installation.
ShopSite TX installation creates screen-pack directories in Transact:
../tms-ts/screen_pack
../tms-ts/root/screen_packIn ../tms-ts/screen_pack/Transact_4_1_0/ShopSite directory, there are sub-directories for each supported Transact version. Choose the version of your Transact installation, for example /v4.2.1. In this 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 the translated files from the screen pack.
In the ../tms-ts/root/screen_pack/images directory there is the same structure as in ../tms-ts/screen_pack, but this time the locale subdirectories contain the images of the screen_pack. Create, if it does not already exists, a subdirectory for your locale and copy the translated screen_pack images in it.
In order to test your translation you need to run the screen_pack commands to copy these files in your store directory in Transact. Locate the screen_pack command in your ShopSite installation and execute this command:
> screen_pack -name Shopsite-host-administrator-name -password Shopsite-host-admnistrator-password -transact transact-system-name -transact_port your-transact-SSL-port -upgradeExecute this command every time you modify any file in the /tms-ts/screen_pack/Transact_4_1_0/ShopSite or ../tms-ts/root/screen_pack/images directories and you need to test it.
To test the images in the common.head.html and merHomePage.Head.html the location of "imageRoot" should be changed in the locale directory you have copied the files in. For example:
var imageRoot = "/tms-ts/screen_pack/images/Transact_4_1_0/ShopSite/v4.1.0/en-US/";in the French kit should be
var imageRoot = "/tms-ts/screen_pack/images/Transact_4_1_0/ShopSite/v4.1.0/fr-FR/";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.
- Main merchant screen
- Pages
- List of Pages
- Add Page (Basic Edit)
- Add Page (Advanced Editing)
- Modify a Page
- List of Pages (Advanced Edit)
- Assign Page
- Assign Items
- Assign Items (Page)
- Assign Items (Product)
- Assign Items (list all Products)
- Edit Page Content
- Edit Page layout
- Power Edit
- Arrange Items
- Delete Pages
- Add several pages
- Database upload: pages
- Products
- List of Products
- Add a Product (Basic editing)
- Add a Product (Advanced editing)
- Add Several Products
- Modify a Product
- Edit Product info
- Edit Product Layout
- Select Cross-sell
- Arrange Cross-sell
- Delete Products
- Power Edit
- Images
- View Images
- Edit Image Attributes
- Upload an Image
- Merchandising
- Discount Schedule
- Associates
- Add Associate
- Edit Associate Data
- Edit Associate Orders
- Delete Associate
- Search Engines
- Custom Pages
- Custom Page Upload
- OrderAnywhere Linker
- Selected links
- Order
- Your shopping cart
- Selected HTML
- All links
- All HTML
- Order API
- Orders
- View Orders
- Delete Orders
- Download Orders
- Reports
- (View History)
- Page summary
- Hosts Summary
- Referrer Summary
- Configuration
- (Clear Sales Counter)Are you sure you want to reset Sales Counter?
- Commerce Setup
- Customize Ordering System
- Payment Setup
- Processor-name setting
- Billing
- Shipping Options
- Flat shipping
- Shipping by weight
- Shipping by currency
- Flat each shipping
- Flat base each shipping
- Base shipping
- Base plus shipping
- none
- Sales Tax
- Store registration
- ShopSite MArketPlace
- Welcome to ShopSite Registration Page
- Utilities
- Change Password
- Publish
- Database Maintenance
- Products and Pages
- Backup
- Orders
- Download database
- Report of the database extract for products pages
- Shopping cart locks
- Reporting locks
- Associate locks
- Wizard
- Store Name and Welcome
- Layout & Color Theme
- Al's Tools (41)
- Footer
- Payment Type and Tax
- Configure shipping
- Publish
- Next Steps
- Preferences
- Store Text
- Locale
- Search Setting
- Page Header & Footer
- More Info Page Setting
- Hosting Service
- Links
- Keys to Seller Success
- Buyer experience
- Your shopping cart
- (Checkout)
- Thank you
- Checkout (Use separate shipping address)
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.
- List of Pages
- There is an additional line underneath the title that says "To grow beyond the 5 page limit of ShopSite Lite, click here.
- Add Several Products
- In the field Number of products to add, if entering a number bigger that the limit, there is an error message screen
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.
- Orders
- List new orders (TX)
- Find orders(TX)
- List Of Orders(TX)
- Smart Receipt(TX)
- Ship Items
- Cancel Items
- Backorder Items
- List of Bulk Processed Orders (TX)
- Find Invoices(TX)
- List Of Invoices(TX)
- Update Payment Setup
- Find Registered customers(TX)
- Change Customer Information
- Add New Payment Card (TX)
- Change Payment Card Information (TX)
- Reports
- Smart Statement File(TX)
- Commerce Reports(TX)
- Tax Reports(TX)
- Commerce Center
- Register at this store
- Commerce Setup
- StoreAndStatus
- storeProfileMenu
- storeNameAndAddress
- storeCurrencyAndLocale
- storePaymentProfile
- storePaymentEnrollment
- storeAdviceOfOrder
- Change Seller Information
- Security Checkpoint (TX)
- Change your password (TX)
- Change security checkpoint (TX)
- Add security checkpoint (TX)
- Change your contact information (TX)
- List and Add Employees
- Create employee
- Preferences
- Value Added Tax (VAT) Options (Vat applies to my store)
- Store Pages
- Hosting Service
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.