Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

developerWorks Community:

  • Close [x]

Creating solutions on the extended sites framework in WebSphere Commerce

Part 1: Using the command layer

Michael DJ Shields (mshields@crossview.com), Solution Architect, CrossView, Inc.
Photo of Michael Shields
Michael Shields works for CrossView®, Inc. He has over a decade consulting and developing strategies to best leverage WebSphere Commerce to match client business requirements. He also has over twelve years of developing interactive web solutions using J2EE, PHP, Zend Framework, Adobe products, HTML, CSS, AJAX, jQuery, DOJO and JavaScript. Michael holds 5 patents, published over 12 tutorials on the WebSphere Commerce Information Center, and 10 tutorials on the developerWorks WebSphere Commerce zone. He holds over 12 technical certifications and a designation as a project manager (PMP).
Quan Nguyen (qnguyen@crossview.com), Solution Architect, CrossView, Inc.
Photo of Quan Nguyen
Quan Nguyen has been working for CrossView, Inc., since 1999, consulting and developing e-business solutions by leveraging WebSphere Commerce. As a Solution Architect, he has over a decade of experience, working with major B2C and B2B companies to implement robust WebSphere Commerce strategies, fulfilling their business requirements.
Raj Sanghvi (rsanghvi@crossview.com), Solution Architect, CrossView, Inc.
Photo of Raj Sanghvi
Raj Sanghvi is a Solution Architect for CrossView, Inc. He has over 6 years of experience consulting in WebSphere Commerce working for different sub systems. He also has over 10 years of experience doing software development using J2EE, Oracle, HTML, XML, and SOAP. He holds over 8 technical certifications and a designation as a project manager (CAMP). He has a Master's degree in Computer Science.
Amar Desai (amar.desai@atech.com), Solution Architect, Ascendant Technology
Photo of Amar Desai
Amar Desai is a Solution Architect at Ascendant® Technology. He has helped many top retail, banking, and dining companies materialize their vision in the e-commerce space using WebSphere Commerce. He has a penchant for applying the latest web application trends such as social commerce, precision marketing, and mobile commerce. He is a certified WebSphere Commerce developer and administrator.

Summary:  The purpose of extended sites in WebSphere® Commerce is to ensure sharable assets among different stores. This tutorial provides insight into different ways to use the store path resource that is an available-to-market framework in WebSphere Commerce. A new concept is introduced in this tutorial that provides provide granular levels of sharing with a sub-set of assets. Also, this tutorial describes how to properly extend an EJB to use the BeanFinderObject for your findBy methods to incorporate sharing queries. You will learn how to better ensure that your store's conglomerate is fully capable to share all of the integral assets to make your business successful, while keeping your software reusable and easy to maintain.

Date:  20 Oct 2010
Level:  Intermediate PDF:  A4 and Letter (143 KB | 53 pages)Get Adobe® Reader®

Activity:  23828 views
Comments:  

Regression testing

Prerequisites

This section is a review of all of the previous steps of this tutorial. It is structured such that you have a checklist of all of the touch points of testing your new assets and how they are influenced by the extended sites framework.

This section contains a brief outline of the regression tests to validate the introduction of new assets into the extended sites world. The idea is to have a number of hosted stores created, along with a number of store relationship entries along with a number of affiliates. The regression tests involve testing all of the possible combinations of these entities together, as well as testing none of them interacting.

To do a regression test, ensure that the stores and data are already setup. Therefore, to complete this section of the tutorial, you have to go back throughout the tutorial and ensure steps have been taken to get the prerequisites ready. Here is a quick checklist to review what has to be in place for a succesful regression:

Hosted stores
Ensure that you have the hosted stores created. In this regression scenario, you are required to set up three hosted stores. See Creating store Example1 to create additional hosted stores.
Test data
Ensure that you have the affiliate data setup for each of the stores and asset store. See Creating affiliates to create additional affiliate data.
STOREREL entries
Ensure that you have entered the correct store relationship entries. See Populating the store relationships for affiliates to add the store relationships according to each test. You have to make adjustments to the SQL statements based on which store you are testing and which tests you are executing. For example, if you look at the regression truth table (Table 3), the Store column is the store_id field data in the SQL statement. The Related Store* columns are considered the relatedstore_id field data in the SQL statement that you are adjusting for each row of the regression tests listed in Table 3.

Table 3. Regression testing all scenarios
Store testTest pathRelated asset store dataRelated Store 1 dataRelated Store 2 dataRelated Store 3 data
Store 1Store path default test 1-Viewed result: Affiliate 2--
Store path test 1Database entry: STOREREL
Viewed result: Affiliate 1
---
Store path test 2-Database entry: STOREREL
Viewed result: Affiliate 2
--
Store path test 3Database entry: STOREREL
Viewed result: Affiliate 1
Database entry: STOREREL
Viewed result: Affiliate 2
--
Store 2Store path default test 2--Viewed result: Affiliate 3-
Store path test 4Database entry: STOREREL
Viewed result: Affiliate 1
---
Store path test 5--Database entry: STOREREL
Viewed result: Affiliate 3
-
Store path test 6Database entry: STOREREL
Viewed result: Affiliate 1
-Database entry: STOREREL
Viewed result: Affiliate 3
-
Store 3Store path default test 3----

The interaction points above are represented as:

Store test
This is the column that corresponds to the hosted store you are opening in the browser to test the results of each scenario.
Database entry
This is the entry in the database to define the store relationship between the row store header and the column store header.
Viewed result
Based on the store relationship row, any entries that are expected to display in the testing will show here.

Section conclusion

Based on the structure of this truth table, each of the stores you are testing provide you with the expected results. You can benefit from printing this particular page and tracking the test results for each store, store relationship, and set of data that displays. After you have regressed all of the possible scenarios, then you can begin to incorporate the store relationship model into all of your requirements that involve new assets that are customized into WebSphere Commerce.

7 of 11 | Previous | Next

Comments



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=551401
TutorialTitle=Creating solutions on the extended sites framework in WebSphere Commerce
publish-date=10202010
author1-email=mshields@crossview.com
author1-email-cc=dwu@us.ibm.com
author2-email=qnguyen@crossview.com
author2-email-cc=dwu@us.ibm.com
author3-email=rsanghvi@crossview.com
author3-email-cc=dwu@us.ibm.com
author4-email=amar.desai@atech.com
author4-email-cc=dwu@us.ibm.com