Merge pull request #1 from morrisjoe/morrisjoe-patch-1

Update live-unit-testing-faq.md

Author: Greg Van Liew

docs/test/live-unit-testing-faq.md

@@ -29,6 +29,25 @@ translation.priority.ht:
 ---
 # Live Unit Testing Frequently Asked Questions
 
+## What's new in Live Unit Testing for Visual Studio 2017 version 15.3? 
+
+**Answer:**
+
+- Support for .NET Core/.NET Standard and performance improvements are the 2 big standouts. You will notice performance is significantly faster after the very first full build and run of tests under Live Unit Testing. You will also perceive significant performance improvement in subsequent starts of Live Unit Testing on the same solution. We now persist data generated by Live Unit Testing and reuse it as much as possible with upto-date checks. Besides these major additions, the following enhancements have also been done: 
+
+  - A new beaker icon is now used to distinguish a test method from regular methods. An empty beaker icon indicates that the specific test in not included in Live Unit Testing. 
+
+  - When clicking on a test method from the pop-up UI window of a Live Unit Testing coverage icon, you now have the option to debug the test right from that context within the UI window and without having to leave the code editor. This is very handy especially when you are looking at a failed test.  
+
+  - Couple more configurable options have been added to Tools/Options/Live Unit Testing/General. You can cap the memory used for Live Unit Testing. You can also specify the file path for persisted Live Unit Testing data directory for your open solution. 
+
+  - Couple more menu items have been added under menu bar of Test/Live Unit Testing. One called 'Reset Clean' to delete the persisted data and generate it again .The other called 'Options', to jump to Tools/Options/Live Unit Testing/General.
+  
+  - We added mechanism to recognize the the following attributes, if you want to specify in source code to exclude targetted test methods from Live Unit Testing.
+    - For xUnit: [Trait("Category", "SkipWhenLiveUnitTesting")]
+    - For NUnit: [Category("SkipWhenLiveUnitTesting")]
+    - For MSTest: [TestCategory("SkipWhenLiveUnitTesting")]
+
 ## Does Live Unit Testing work with .NET Core?  
 
 **Answer:**
@@ -195,7 +214,7 @@ Live Unit Testing starts a build whenever it detects that source files have chan
 
 **Answer:**
 
-Live Unit Testing currently doesn't work well with the Lightweight Solution load feature if all projects in the solution are not yet loaded. You may get incorrect coverage information in such scenarios.
+Live Unit Testing currently doesn't work well with Lightweight Solution load feature. It works only after at least one of the test projects is loaded. Until then it won't work because currently Live Unit Testing is dependent on at least one of the test projects referencing a test adapter (MSTest, xUnit or NUnit) being loaded.
 
 ## Why does Live Unit Testing does not capture coverage from a new process created by a test?