I run a CI pipeline on jenkins with VSTest running our Unit Tests and Integ Tests, the machine is Winodws Server 2016 and we have enabled the long filepath option in the registry.. My question is has VSTest taken advantage of this long file path api given by MS as I have ran into issues where the tests cannot be found due to the file adapter path being too long, thus not discovered by VSTest console..
The tests will then become available if I use a temporary custom workspace and rerun.. Any help on this would be great
Aucun commentaire:
Enregistrer un commentaire