Add unit test project to solution

[mrlacey]

Add a feature to add a unit test project to the solution. This should include a reference to the app project.

Need to consider what, if any, test(s) to include by default.

[jamesmcroft]

Similar to my comments in #300 - would this be optional as it currently is when creating a new blank project?

[crutkas]

why not just allow someone to opt in as a system level and make the whole project straight up testable. With that said, I can see how to do UI testing, but to do stub out a proper unit test without any business logic? feels odd as not sure how much would be testable

[mrlacey]

My thinking was that by making this a "feature" it becomes optional.
Yes, there's not a lot we can test but by making it easy to add unit testing to the solution we can hopefully help with its adoption.

Even if we only added a single test which included Assert.Inconclusive("TODO: Write some tests"); I would consider this better than doing nothing.

[magol]

Perhaps add some commented examples of some types of tests that you can perform just to show how to best write tests based on selected conditions.

The conditions for writing tests differ depending on the chosen framework (Code behind, MVVM Basic, MVVM light, PRISM), how Dependency injection is performed, chosen unit test and mock framework, etc.

[mrlacey]

Once we get to FCU as a minimum SDK and split out potentially X-Plat functionality this could be 3 options:

• Add a UWP unit test project that references the main app for testing the functionality it contains
• A NetCore 2.0 project using MSTest that references the X-Plat library for testing X-Plat functionality
• A NetCore 2.0 project using XUnit that references the X-Plat library for testing X-Plat functionality

[mrlacey]

moving back to backlog as timeline for major restructuring is now undetermined