Struture of test projects/roles

[Robin-Smets]

Like discussed on cactus day I want to propose this structure concerning test projects. test would be a subdirectory of roles (like tests-integration and tests-unit are today) and everything else would be somewhere in test.

1. test - stuff that is used for tests
   1.1 TestFramework - namespace/class library for the C# test framework (mock, helpers, custom asssers, etc.)
   1.2 scripts - non-C# scripts that are used for testing. For example data data creation scripts for integration tests or scripts like csv_diff.py (a tool in the making for comparing actual generated reports on the basis of the created file)
   1.3 tests - test files for automated testing
   1.3.1 tests-integration - integration tests
   1.3.2. tests-unit - unit tests (testing pure logic)
   1.3.3. tests-ui - Ui tests (testing razor component behaviour)
   1.3.4 tests-performance - tests that focus on performance aspects
   1.3.4.1 tests-benchmark - testing execution time
   1.3.4.2 tests-load - testing behaviour with a big amount of data that has to be processed

This structure would be the cleanest, in my opinion. But we would have to evaluate how much effort it would take to align our ansible routines with the structure and if there are any reasons that would make this structure problematic for our established processes (install, upgrade, test-install, etc)

In a branch I just moved everythhing that was not a unit test in a class library and referenced that project in the unit testing project and it worked for local unit testing. I am not 100% sure, but I think I made an upgrade on my VM with that branch, so upgrading should work without more hassle too. But I am not sure, so I will test that in due time again.