Forum Discussion
How to test Workload Developed in Local Environment
Ashwath_Bala_S thanks for building!
I will leverage your question to improve the documentation accordingly, so anything you can share about what was clear/less clear would be amazing.
In Dev mode: Fabric Developer Mode MUST be enabled in your workspace settings to test custom workloads. An important concept to is that when you run the DevGateway the package is registered to Fabric backend and when you run your client Fabric loads additional manifests files (such as product.json) are being loaded to the client session - this allows complete e2e testing from your local environment.
So everytime you make a change to the manifests files you should point re-build the nuget and than run the devgateway pointing it to: MANIFEST_PACKAGE_FILE_PATH.
For detailed explaination of the above: Microsoft Fabric workload environment - Microsoft Fabric | Microsoft Learn
If you want to test your .nupkg and .zip format, you role must be Fabric Admin to enable developer mode. Once you have this reole then you can do your testing workload development kit locally.
Please follow the below accepted solution and official docs. It might helps you.
Solved: Fabric Developer Mode not visible - Workload Devel... - Microsoft Fabric Community
Microsoft Fabric Workload Development Kit - Microsoft Fabric | Microsoft Learn
Please let me know if it works for you.
Thank you!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
Thank You suparnababu8 ,
Is there any official Microsoft Documentations that we can refer to test the developed Workload (in .nupkg and .zip format) to test in my local environment?
Thanks in Advance!
Ashwath_Bala_S thanks for building!
I will leverage your question to improve the documentation accordingly, so anything you can share about what was clear/less clear would be amazing.
In Dev mode: Fabric Developer Mode MUST be enabled in your workspace settings to test custom workloads. An important concept to is that when you run the DevGateway the package is registered to Fabric backend and when you run your client Fabric loads additional manifests files (such as product.json) are being loaded to the client session - this allows complete e2e testing from your local environment.
So everytime you make a change to the manifests files you should point re-build the nuget and than run the devgateway pointing it to: MANIFEST_PACKAGE_FILE_PATH.
For detailed explaination of the above: Microsoft Fabric workload environment - Microsoft Fabric | Microsoft Learn