Test the extension

To test your extension, we have two modes:

1. Developer Mode - Helps you to test your extension during the developing phase of the extension.
2. Production Mode - Helps you to test/use your extension once the extension is developed and installed in your Zoho Desk portal.

Here, we are testing the extension in the Developer mode.

1. Open Terminal or Command prompt and navigate to your project folder.
2. Execute zet run command to start the server from the extension directory.
   • If you use Mozilla Firefox, open https://127.0.0.1:5000/plugin-manifest.json in a new tab, and click Advanced ---> Accept the Risk and Continue.
   • If you use Google Chrome, open https://127.0.0.1:5000/plugin-manifest.json in a new tab and click Advanced ---> Proceed to Unsafe -> widget.html. 
     If the Proceed to Unsafe option does not appear, enable the chrome://flags/#allow-insecure-localhost Chrome flag and restart the browser
     
     
3. Log in to your Zoho Desk account. If you do not have a Zoho Desk account, you can sign up here.
4. On the top-right corner of Zoho Desk, click Setup icon.
5. In Setup page, click Build Extensions under the Developer Space.
   
   

6. On the Build Extensions page, click Enable Developer Mode.

   
   
   This action refreshes the page and activates the Developer Mode.
   The extension will be installed in your Zoho Desk portal and you can see your widget as shown below.

   Note: By default the widget location will be ticket's right panel so the widget is loaded at the right panel of the ticket. You can test your extension to verify if it behaves the way you intended.

7. Go to widget.html file in your project folder and modify the default text given.
8. To view the changes in widget, refresh the corresponding widget.
   
   
   
   Once you reload the extension, it will be rendered with the changes you have made.  
   
   
9. After testing the extension, click Disable Developer Mode on the Build Extensions page to disable developer mode.

   Note: If you make any changes to the plugin-manifest file, a full refresh or marketplace refresh is required to reflect the changes.