You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a task parameter that allows the specifying of multiple exclude filters for folders/files to run coverage against.
Reason: Within our source folder which contains our poweshell scripts which we want to get coverage data for, we have a "ServiceFabric" folder that includes a load a Microsoft provided scripts that are needed for our implementation, but because are third-party code we don't write unit tests for.
Because they are in our source folder, they get included in our coverage data which messes up up our results. We have a workaround for this during local developmentby using a custom script to generate the coverage data.
Azure DevOps Extension you are using
Pester
Where are you running it?
TFS 2018
Version of Extension/Task
V7
Requirement
Add a task parameter that allows the specifying of multiple exclude filters for folders/files to run coverage against.
Reason: Within our source folder which contains our poweshell scripts which we want to get coverage data for, we have a "ServiceFabric" folder that includes a load a Microsoft provided scripts that are needed for our implementation, but because are third-party code we don't write unit tests for.
Because they are in our source folder, they get included in our coverage data which messes up up our results. We have a workaround for this during local developmentby using a custom script to generate the coverage data.
But there is no mechanism to specify this sort of filtering in our CI process using the Pester task at the moment.
I was thinking something like the search pattern parameter in the Index Sources & Publish Symbols task https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/index-sources-publish-symbols?view=azure-devops
The text was updated successfully, but these errors were encountered: