Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Samples
Starter stores
A fully functional sample online store, provided in store archive format with WebSphere Commerce. Starter stores are samples designed to be used as a base from which a customized online store can be created. Starter stores are translated into several languages and support multiple Web browsers and platforms. Starter stores are fully accessible, with the exception of the Madisons mobile starter store. Accessibility guidelines for mobile devices are not well defined or well established.
Mobile starter stores
WebSphere Commerce provides optimized starter stores for mobile devices such as smart phones containing Web browsers. Mobile starter stores demonstrate best practices in mobile store development with WebSphere Commerce, and can act as a base for implementing mobile storefronts.
Smart phone and tablet starter stores
Smart phone and tablet starter stores provide rich storefronts for several mobile devices and platforms. They can be viewed on mobile devices using the mobile web, or deployed as native or hybrid applications.
Testing your store
WebSphere Commerce provides a test assets package that contains documentation and tools to help introduce, plan, and run Functional Verification Testing (FVT) for your store.
Storefront Test Automation Engine usage
This section describes how you can use the Storefront Test Automation Engine to use data files, enable change flows in tests, capture screenshots while tests are running, work with Secure Socket Layer certificates, and increase the reliability of your tests.
Store cleanup
Clean up the store between test cases to prevent a single test failure from cascading to other tests. Doing so increases test reliability.

Store cleanup

Clean up the store between test cases to prevent a single test failure from cascading to other tests. Doing so increases test reliability.

For example, a cleanup script might perform the following actions:

Reset the change flow options back to predefined default values
Reset the store language to a default value
Reset the store currency to a default value
Empty the shopping cart
Empty the wish list

This way, if a test case fails and leaves the store in the middle of a transaction, the next test to run will still start from a known state.