PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue
I'm not sure if the described issue is actually a problem or if it's intentional behavior. Namely, if both the source app and test app have the same name, the RunAl-Pipeline will copy the test app into both the Apps and TestApps folders. In this case, the source app will be overwritten by the test app if the same app name is specified in both app.json files. I would expect the copying process to be based on the appId from the corresponding app.json file, but it appears to operate based on the app name instead.
Scripts used to create container and cause the issue
Yeah, that scenario is not supported, and I have no plans of changing things to support it.
Recommendation would be to include test in the name of the test app or like.
PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue I'm not sure if the described issue is actually a problem or if it's intentional behavior. Namely, if both the source app and test app have the same name, the RunAl-Pipeline will copy the test app into both the Apps and TestApps folders. In this case, the source app will be overwritten by the test app if the same app name is specified in both app.json files. I would expect the copying process to be based on the appId from the corresponding app.json file, but it appears to operate based on the app name instead.
Scripts used to create container and cause the issue
Full output of scripts
Screenshots
Additional context