More docs about unit-test

Author: veblush

README.md

@@ -50,8 +50,19 @@ Tests in Json.NET are updated to be able to run under
 All tests pass under Microsoft .NET 3.5 but with UnityEditor some of them fail
 because there are not-implemented features and bugs in Unity3D-Mono framework.
 
-Result:
-![Test status](https://raw.githubusercontent.com/SaladbowlCreative/Json.Net.Unity3D/master/docs/UnitTestSummary.png) [Detailed Description](./docs/UnitTest.md)
+Test Result:
+
+| Profile        |:white_check_mark: Passed | :x: Failed | :white_circle: Ignored |
+| :------------- | -----------------------: | ---------: | ---------------------: |
+| Microsoft.NET  |                     1448 |          0 |                      1 |
+| Unity3D-Mono   |                     1435 |         13 |                      1 |
+
+Detailed Description is [here](./docs/UnitTest.md) to tell you what failed and why.
+
+## Unity Compatibility
+
+This library is tested on Unity 4.7, 5.2 and 5.3. For AOT environment like iOS, you
+need to use IL2CPP instead of obsolute Mono-AOT because IL2CPP handles generic code better than Mono-AOT. With Mono-AOT configuration, AOT related exception would be thrown.
 
 ## FAQ
 

docs/UnitTest.md

@@ -2,20 +2,43 @@
 
 ![Test](https://raw.githubusercontent.com/SaladbowlCreative/Json.Net.Unity3D/master/docs/UnitTestResult.png)
 
-## What failed
-
-### DateTimeFormat with CultureInfo doesn't cover all locale
-
-##### ReadAsDateTimeOffsetIsoDate
+## Failed tests
+
+- Newtonsoft.Json.Tests.Converters.IsoDateTimeConverterTests
+  - SerializeFormattedDateTimeNewZealandCulture
+- Newtonsoft.Json.Tests.JsonConvertTest
+  - WriteDateTime
+- Newtonsoft.Json.Tests.JsonTextReaderTest
+  - ReadAsDateTimeOffsetIsoDate
+- Newtonsoft.Json.Tests.Linq.JTokenReaderTest
+  - ReadAsDateTimeOffset_String
+  - ReadAsDateTimeOffsetString
+- Newtonsoft.Json.Tests.Serialization.JsonSerializerTest
+  - DateFormatStringWithDateTimeOffset
+  - DateFormatStringWithDictionaryKey_DateTimeOffset
+  - DateFormatStringWithDictionaryKey_DateTimeOffset_ReadAhead
+  - DateTimeDictionaryKey_DateTime_Iso
+  - DateTimeDictionaryKey_DateTime_Iso_Local
+  - DateTimeDictionaryKey_DateTimeOffset_Iso
+- Newtonsoft.Json.Tests.Utilities.DateTimeUtilsTests
+  - NewDateTimeOffsetParse
+  - NewDateTimeParse
+
+## Why did tests fail?
+
+Most of them failed because DateTime and DateTimeOffset in Unity3D-Mono
+cannot handle UTC formatted string well. (postfix Z or +09:00, fraction part of ISO time.)
+
+For example, ReadAsDateTimeOffsetIsoDate failed with this message because
+DateTimeOffset didn't get UTC timezone in parsing "2011-08-01T21:25Z".
 
 ```
 Expected: 08/01/2011 21:25:00 +00:00
   But was:  08/01/2011 21:25:00 +09:00
 ```
 
-### DateTimeOffset cannot parse formatted string well
-
-##### SerializeFormattedDateTimeNewZealandCulture
+SerializeFormattedDateTimeNewZealandCulture failed because DateTime in Unity3D-Mono
+generated different date-time string from .NET one.
 
 ```
 Expected string length 40 but was 32. Strings differ at index 1.
@@ -24,7 +47,8 @@ Expected string length 40 but was 32. Strings differ at index 1.
   ------------^
 ```
 
-##### DateFormatStringWithDateTimeOffset
+DateFormatStringWithDateTimeOffset failed because DateTimeOffset in Unity3D-Mono
+cannot parse user-defined time format well such as "yyyy'-pie-'MMM'-'dddd'-'dd".
 
 ```
 Newtonsoft.Json.JsonReaderException : Could not convert string to DateTimeOffset: