Testing Themes Locally on SuiteCommerce for Optimization

You can test your theme customizations on a local server before deploying to NetSuite. This is crucial for ensuring the frontend changes work correctly and provides a controlled environment for testing.

Why Test Locally?

Testing your SuiteCommerce themes locally allows you to make adjustments and verify functionalities in real time. The local server is especially beneficial for checking changes related to skins or for Sass variables exposed to the SuiteCommerce Theme Manager (SMT).

How to Test Your Theme on a Local Server

Follow these steps to effectively test your theme:

1. Set Up Your Environment:

   • Open your terminal and navigate to your top-level development directory.

2. Run the Gulp Command: To compile and deploy your theme locally, execute the following command:

   bashCopy

   gulp theme:local

   Warning: This command updates the manifest.json file for your theme, potentially overwriting any manual changes. To prevent data loss, use this command instead:

   bashCopy

   gulp theme:local --preserve-manifest

3. Access Your Theme in a Browser: Using the structure below, replace the variables with your configurations:

   • http://<DOMAIN_NAME>/c.<ACCOUNT_ID>/<SSP_APPLICATION>/shopping-local.ssp
   • http://<DOMAIN_NAME>/c.<ACCOUNT_ID>/<SSP_APPLICATION>/my_account-local.ssp
   • http://<DOMAIN_NAME>/c.<ACCOUNT_ID>/<SSP_APPLICATION>/checkout-local.ssp

   Variable Replacement:

   Variable	Replacement
   DOMAIN_NAME	Your NetSuite website domain (e.g., http://www.mysite.com)
   ACCOUNT_ID	Your NetSuite account ID (e.g., c.123456)
   SSP_APPLICATION	Root URL for the application (use scs for SuiteCommerce)

4. Update Changes After Launch: If you add files or make changes after starting the local server, remember to rerun the gulp theme:local command to include those updates, as Gulp.js does not automatically handle new files.

Output of the Gulp Command

When you run gulp theme:local, it compiles all source files and builds the local distribution in the LocalDistribution/tmp directory. This includes all your Sass and template files. The local server initializes watch tasks, which will automatically recompile source files upon detecting changes.

Next Steps

Once you've completed testing your theme locally, the next stage is deploying the theme to NetSuite. After deployment, don’t forget to activate your theme for it to be visible on your website.

Key Points to Remember

• Testing locally minimizes risks before deployment.
• Always manage your manifest.json carefully to avoid data loss.
• Ensure subsequent changes are reflected by rerunning the Gulp commands as needed.

Source: This article is based on Oracle's official NetSuite documentation.