Collapse/remove projects under src/installer/tests/Assets/TestProjects

[elinor-fung]

Many projects in src/installer/tests/Assets/TestProjects only have minor differences - multiple projects can become one with different behaviour based on command line arguments to reduce the cost of restoring/building the test assets (and including them in a helix payload when we get to that point)

Likely candidates: PortableApp*, RuntimeProperties, AppWith*, LightupApp

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

Issue Details

---

null

Author:	elinor-fung
Assignees:	-
Labels:	test-enhancement, area-Host
Milestone:	-

[am11]

@elinor-fung, are these operations relevant to host testing:

runtime/src/installer/tests/Assets/TestProjects/StandaloneApp/Program.cs

Lines 17 to 18 in 21e9913

	// A small operation involving NewtonSoft.Json to ensure the assembly is loaded properly
	var t = typeof(Newtonsoft.Json.JsonReader);

If it is not possible that the assembly loading functionality could regress without breaking other (non-host) tests in the runtime repo (e.g. test_dependencies uses live host for libraries tests), we can clean up Newtonsoft dependency from TestProjects assets as well.

[elinor-fung]

For most cases, I think they are not relevant. I think they were mostly there to test basic dependency resolution, but also muddied with relying on the SDK/build. Aside from what you mentioned about coverage via the live host being used in libraries tests now, since those TestProjects assets were added @vitek-karas has done a lot of work to create more targeted component tests for that area.

There are a couple tests that intentionally do things to target moving around / configuring dependencies that use it, but I think they could/should be changed to do things differently.