-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test discovery may fail and does not discover all tests #66
Comments
I can second that one. It fails for me as well: Operation failed. The index entry of length 903 bytes for the index 'Idx_Stale_StateValue_DisplayName' exceeds the maximum length of 900 bytes. When this occurs and the test explorer updates it will show a very limited number of my tests. Closing and re-opening visual studio will show the expected number of tests after a rebuild. |
Hi, |
Hello,
And the test display name generated by xunit is:
I was not able to understand why this name is so long. You can reproduce the issue with this snippet: Basically you need to things to have the issue:
@bradwilson |
The limitation is a Visual Studio limitation, so the truncation should happen there (in particular, when creating the Visual Studio test case object). No need to punish everybody else. :) I think basically saying anything > 450 characters would just to a .Substring(0, 447) with a |
… is longer than 447 characters.
Fixed by #70 |
The test discovery fails every times in one of our project with the error message
Operation failed. The index entry of length 903 bytes for the index 'Idx_Stale_StateValue_DisplayName' exceeds the maximum length of 900 bytes.
When it fails the discovery is stopped and a lot of tests are not being discovered.
It seems that the test adapter may generate too long names or ids.
NUnit had the same issue, if found some bugs about it
nunit/nunit-vs-adapter#68
I have not been able to find the test triggering the error but I eventually update the issue if I do.
The text was updated successfully, but these errors were encountered: