aspnetcore/test/Microsoft.AspNet.Mvc.DataAn...
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
..
Properties
CompareAttributeAdapterTest.cs Remove use of `IsMono` to no-op a test 2015-09-10 11:55:51 -07:00
DataAnnotationsClientModelValidatorProviderTest.cs
DataAnnotationsMetadataProviderTest.cs
DataAnnotationsModelValidatorProviderTest.cs
DataAnnotationsModelValidatorTest.cs
DataMemberRequiredBindingMetadataProviderTest.cs
DataTypeClientModelValidatorProviderTest.cs [Fixes #2817] Support client side validation for all numeric types 2015-08-13 17:32:13 -07:00
DefaultModelClientValidatorProviderTest.cs
MaxLengthAttributeAdapterTest.cs
Microsoft.AspNet.Mvc.DataAnnotations.Test.xproj
MinLengthAttributeAdapterTest.cs
ModelMetadataProviderTest.cs Fix #2776 - Add implicit [BindRequired] for value type properties 2015-08-13 15:35:54 -07:00
NumericClientModelValidatorTest.cs [Fixes #2817] Support client side validation for all numeric types 2015-08-13 17:32:13 -07:00
RangeAttributeAdapterTest.cs
RequiredAttributeAdapterTest.cs
Resources.resx
StringLengthAttributeAdapterTest.cs
TestModelNameProvider.cs
TestResources.cs
project.json Update project.json to have warningsAsErrors accept a bool. 2015-09-02 15:35:13 -07:00