Skip to content
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

Long test data results in Contents of string '{test name}' exceeds max of '449', string has been truncated. messages #1139

Closed
dougbu opened this issue Feb 24, 2017 · 4 comments

Comments

@dougbu
Copy link
Contributor

dougbu commented Feb 24, 2017

When using the xunit and xunit.runner.visualstudio v2.2.0 packages in a recent copy of Visual Studio 2017 RC, messages such as the above appear frequently in the Output window. Not sure whether such test name truncation is in itself a problem e.g. not executing or reporting on some tests. But, the extra output definitely makes it difficult to see messages about other problems.

The aspnet/Mvc repo hits this problem fairly frequently. (See the dougbu/migration branch until I get that switch to use MSBuild and the xunit.runner.visualstudio package in.) I haven't checked all tests that cause this output. But, test data tends to involve Types with long names and POCO classes with many properties e.g. DisplayFormatAttribute.

See also a similar nUnit bug: nunit/nunit#59.

@cknaap
Copy link

cknaap commented Mar 27, 2017

And at the same time this happens, the Test Explorer does not finish it's progress bar. If I run just the one test with 16 cases that (all) cause this '449' message, the progress bar stops at 50%.

@bradwilson
Copy link
Member

Closed for age.

@dougbu
Copy link
Contributor Author

dougbu commented Nov 10, 2017

@bradwilson the problem may be longstanding but it hasn't gone away. Issue still exists in the latest xUnit packages. And, it seems like the xUnit team could make changes similar to whatever the nUnit team did to avoid the problem.

I don't have much time to work on this but could investigate further if a PR would be of interest. LMK…

@bradwilson
Copy link
Member

Please provide a PR to fix the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants