This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 12%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENV%3C/text%3E%3C/svg%3E)
Hi Team,
In my CI-CD pipeline, while running test It was taking around 45 minutes to discovery tests. if we use batch exception every batch creation time its was waiting around 1 hour for discovering tests.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 4%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
Hello, @Nama, Vinay !
Thank you for reaching out! Azure DevOps and its services are not supported in Microsoft Q&A because the Azure DevOps team and DevOps community are actively answering questions here:
https://developercommunity.visualstudio.com/spaces/21/index.html
I didn't find any suitable answers in below link.
Previously 3 months back to identify 50k tests it took only 90 seconds but now its taking upto 45 minutes some times its little more also.
could you please help me to resolve this issue
Hi Team,
Any update on above issue.
Hello @Nama, Vinay ,
Unfortunately Azure DevOps is outside my area of specialization and is covered in its own forums. Does this sound similar to your scenario?
I am trying to find out when the discovery phase is taking this performance penalty. It seems to be a combination of having run a debug session and changing some code afterwards.
As soon as the discovery phase is completed and there is no code change afterwards, the discovery phase always runs smoothly.
Additionally, some people have reported that there was an increase in the number of files being scanned and limiting the scope of the scan helped to improve performance.
I tried this solution but it didnt helped in my scenario.
In my case after test filtering completion, again proxy discovery test entered and this process looping more than 1000 times.
so to discover tests its taking more than 45 minutes some time it took 2 hours.