-
Notifications
You must be signed in to change notification settings - Fork 326
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
Overloaded test methods result in InvalidOperationException #392
Comments
Appears to be a known limitation in xunit adapter. See xunit/xunit#1042. |
Did this work in project.json world because the xunit there wasn't using the visual studio runner? If so, did it do something different when run in VS? |
@NTaylorMullen - yeah both overloads were working with project.json. |
- thanx to @NTaylorMullen for initial conversion - e.g. AssemblyInfo.cs files were already minimized or removed :) - allow `>=` RC3 CLI's to build and run MVC - work around several dotnet migration issues; see #5482 - disable full .NET Framework runs of functional tests; see #5873 - remove `Microsoft.DotNet.InternalAbstractions` and `System.Xml.XmlDocument` dependencies - remove project.json (!!), *.xproj, .notest, and web.config files Redo earlier changes: - apply test migration to .NET 4.5.2 in *.csproj world - see 63507c8 for previous, project.json work - apply dependency version downgrade from 0097e40 in *.csproj world Make other test-related changes: - make Microsoft.AspNetCore.Mvc.TestDiagnosticListener a regular class library - add support for `/p:GenerateBaselines=true` for functional and Razor.Host tests - separate `GetCSharpTypeName_ReturnsCorrectTypeNames_ForOutParameter()` test - work around inability to deserialize a odd `ref` type - xUnit and vstest now serialize / deserialze test data more often - skip poor test mentioned in #5768 - work around microsoft/vstest#392 - rename tests to avoid duplicates - work around microsoft/vstest#419 - set up created `AppDomain`s with current `ApplicationBase`
This is known xunit issue: xunit/xunit#1042 and unfortunately there is no solution for it :( |
I'm shocked; how did this work in project.json land? It used xunit as well. |
Description
We were migrating an existing project.json based xunit test project to MSBuild. One of the test classes had a overloaded method - one as a
Fact
with no arguments and the other aTheory
withInlineData
. Once migrated, the test runner fails while running one of the overloaded method.Steps to reproduce
Expected behavior
Overloaded tests work
Actual behavior
Environment
The text was updated successfully, but these errors were encountered: