Move test-networks out of the core and bin/anduril

[Kristian Ovaska]

Test-networks is in practise only used for testing the Scala support of the engine. Thus, it can be moved to utils/test-workflow and it would not be visible for end users.

[Ville Rantanen]

for bundles, like 'tools', test-networks has been also a good platform to show use-cases (like so many testcases for components are actually more use-cases than testing functionality). There are many components where the usage is very much linked to other components, and it makes sense to show how they work together.

Testcases and test-networks may not be the best places to show how to use components, but it's the best place so far. Good also because they get run periodically, and we can keep them in working condition.

Maybe we should have another way of displaying 'tutorial' kind of component usage

[Kristian Ovaska]

Automated testing and end-user demos are different things and they are often (though not always) contradictory. If you look at some of the test-networks in testsystem, they look very strange because they are systematically testing various features. They would be bad demos.

I have deleted a couple test-networks from testsystem because I couldn't see what features they were (automatically) testing. I guess they were demos, then.

For components, test cases can double-function as demos because the component interface is much simpler. But test cases should still be primarily tests, i.e. they should validate that the output is corrent.

We need another way of documenting and demoing bundles.