I’m seeking clarification regarding our recent app submission which was rejected due to insufficient code coverage, despite our internal testing showing we meet the requirements.
As you can see from our coverage report above, we appear to be meeting the recommended 80% coverage threshold for marketplace apps. All our metrics - statements, branches, functions, and lines - are above 80%.
Questions for the Community:
Has anyone encountered a similar situation where their app was rejected despite meeting coverage requirements?
Are there specific areas or types of coverage that receive additional scrutiny during review?
What testing tools and methods do you recommend for ensuring comprehensive coverage?
Are there any common pitfalls or blind spots we should look out for in our coverage analysis?
@Damanpreet_Singh
A file named “.report.json” will be created in the app root folder by the FDK CLI. It’s where the metadata regarding the code coverage is stored in the packed app.
The “.report.json” file is missing from your submitted app package. Could you please check if this file exists in your local app folder and is packed along with the app package when using the “fdk pack” command?
If it was missed to add while packing, could you uninstall and reinstall FDK to see if it works again?