Correlating Unit Tests

[michael-hawker]

Each feature should have their own unit test project, these should be easy to run within VS for the developer.

At the same time we want the CI/pipeline to run all the unit tests together and report any issues back.

[XAML-Knight]

Devil's Advocate: relaxing the unit test requirement would probably increase developer engagement (else, how is the Labs project different from the Community Toolkit?)

[michael-hawker]

@XAML-Knight unit tests aren't required to do an initial PR and start a project in labs. But we want to have the same infrastructure so that as an experiment progresses unit tests, samples, docs, and potentially ui tests can also be added. That way everything can be built here more collaboratively and without needing to be done all in a single-go.

Once everything is built-here, we'll know it's all set to transition into the main repo.

[Arlodotexe]

Waiting on #4 before taking this.

[mrlacey]

#82 handles this by including the shared project for the tests of each experiment.

Once that PR is in and there is more than one experiment in the repo this can be confirmed and closed.

[mrlacey]

I believe this can be closed. @Arlodotexe or @michael-hawker to confirm