Testing your add-on

Core to the development of your add-on is the testing process. During the development of your add-on for eLabNext, you will be testing your add-on during two stages: the development and the deployment process.

Testing during development

While developing your add-on, you can test it in the SDK development environment (sandbox). Testing can be done by hosting your add-on on an HTTPS web server and adding it to the SDK development environment (sandbox) as a custom add-on through the Side Loading functionality. When your add-on has been sideloaded in the sandbox environment, you can observe your add-on's behavior in the eLabNext environment. This will allow you to test the functionality of your add-on and make any necessary changes to the code. A key component in this process is your browser's developer tools, allowing you to debug your add-on and observe its behavior in the eLabNext environment. Here, errors and warnings will be displayed, and you can use the console to log information about your add-on's behavior. This can help you to identify and fix any issues with your add-on.

Don't forget that after testing with side loading has been completed, you should remove the following element from your code:

context.init();

This function is only needed for side loading and add-on development and must be removed from the code when this goes to the Marketplace during the publishing and release processes.

Testing for publish and release to the Marketplace

Once you have completed the development of your add-on, you can test it in the eLabNext Marketplace. This is part of the Publishing process. When you have filled out all mandatory fields and uploaded your add-on code, you can publish your add-on to the Sandbox Marketplace. The add-on can then be installed and tested for its functionality. Besides this, it is also important to "test" the Marketplace page for the add-on. Users of your add-on should find all necessary information about the add-on and how to use it. This includes the add-on's description, screenshots, and contact information.