Testing Extensions on a Local Server in SuiteCommerce

TL;DR Opening

Testing SuiteCommerce extensions locally before deploying them to a live environment is essential to ensure everything functions correctly. This article outlines how to efficiently test extensions on a local server using Node.js and Gulp.

How to Test Your Extension Locally

To effectively test your SuiteCommerce extensions, follow these steps:

1. Start Your Local Server: Before testing, ensure that your local server is active. Navigate to your Commerce website on the local server.

   • This can typically be achieved with the command:
     bashCopy

     gulp extension:local

   This command compiles your source files and sets up a LocalDistribution directory.

2. Change Display Types: Visit a product list page and alter the display type. Notice that the grid and table views will not change, as illustrated below:

   

3. View the Detailed List: Switching to the list display type should show detailed descriptions for each product:

   

Important Considerations

• Typically, extensions should be tested locally before going live. If your extension includes SuiteScript or JSON configuration files, you must deploy those to your NetSuite account.
• SuiteScript services will not be accessible until deployment, and JSON changes won’t apply until they are deployed as well.
• If manifest files are updated, remember to restart the local server to see those changes reflected.

Conclusion

Testing your SuiteCommerce extensions on a local server is a crucial step in the development process. This allows you to verify functionality and performance before the final deployment to your live site. Following the steps outlined here will help ensure your extensions operate as intended before going live.