Local end-to-end project in REEF.NET

[Andrew Chung <af...@gmail.com>]

Hi all,

I've noticed that our local end-to-end tests and some of our unit tests are
both put in O.A.R.Tests, which is unfortunate because O.A.R.Tests is a
friend project to many other projects and allows it to access internal
fields -- we are thus "blind" in the sense that we do not know if we have
unknowingly hidden an API that is meant to be exposed.

On that note, I propose to separate unit and end-to-end tests in
O.A.R.Tests into 2 projects, with the project hosting the end-to-end tests
not being a friend project to any other projects.

What do you think?

Thanks,
Andrew

Re: Local end-to-end project in REEF.NET

[Markus Weimer <ma...@weimo.de>]

On 2016-01-14 07:57, Andrew Chung wrote:
> On that note, I propose to separate unit and end-to-end tests in
> O.A.R.Tests into 2 projects, with the project hosting the end-to-end tests
> not being a friend project to any other projects.
> 
> What do you think?

This sounds good. We should also have a single launcher for all of them,
as we currently add a new project whenever we need a new .exe, which
isn't sustainable in the long run.

The same "friend" business actually repeats itself one level higher:
NuGet and MSBuil do not share the same dependency mechanism. Hence,
dependencies *within* a solution are different from dependencies
*across* solutions. This means that our examples and tests currently do
not ensure that our NuGets actually are complete and work.

It might make sense to move our examples and integration tests into
their own solution altogether to also check for that. However, that
creates the added complexity of managing the dependency between them and
the REEF NuGets. Maybe best to do it one step at a time.

Markus