aspnetcore/test/Microsoft.AspNet.Mvc.Format...
Doug Bunting 271e19e61a Remove use of `IsMono` to no-op a test
- use `[ConditionalFact]` or `[ConditionalTheory]` instead
  - in some cases test was already conditional
- move other `IsMono` checks into data sets where possible
  - not reported as skipped but at least not counted as successful

nit: switch from `[ConditionalTheory]` to `[ConditionalFact]` as appropriate
- slightly more efficient since xUnit won't check for data
2015-09-10 11:55:51 -07:00
..
Internal
Models
FlushReportingStream.cs
Microsoft.AspNet.Mvc.Formatters.Xml.Test.xproj
XmlAssert.cs
XmlAssertTest.cs Remove use of `IsMono` to no-op a test 2015-09-10 11:55:51 -07:00
XmlDataContractSerializerInputFormatterTest.cs Remove use of `IsMono` to no-op a test 2015-09-10 11:55:51 -07:00
XmlDataContractSerializerOutputFormatterTest.cs Remove use of `IsMono` to no-op a test 2015-09-10 11:55:51 -07:00
XmlSerializerInputFormatterTest.cs Remove use of `IsMono` to no-op a test 2015-09-10 11:55:51 -07:00
XmlSerializerOutputFormatterTest.cs
project.json