Create test for using a manual project

[AlanCoding]

SUMMARY

Let me explain:

I am only doing this in support of another objective - which will involve:

• create a collection, maybe packaging it
• create a git repository that references this collection in requirements.yml
• using a runner branch that makes use of some data from the collection
• connecting back-end event processing to data that runner relays on to it through event data

This was looking like a lot of steps, so I wanted to start on some infrastructure to put more and more of these all in the same place - which has to be the live tests.

So far this seems to be going rather well to copy the mock repo folders to the projects folders and using them in a job template.

I am so-far unclear about whether requirements.yml could be supported in this way. I actually think it won't...

So the next step would be to try to do git init and use the requirements as a file:// git requirement... both for the original project, and for the collection inside of the requirements.yml (not sure if this is allowed), and this requires patching the isolation paths as well. But baby steps.

Right now I mainly need to see what the fallout of patching playbooks monkey patch will be.

ISSUE TYPE

• Bug, Docs Fix or other nominal change

COMPONENT NAME

• API

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud