Support for test plan targets with container paths outside the workspace directory

[terrytanvc]

Hi, I’m trying to use it in a repository where the .xcworkspace is not located at the repository root, and some Swift packages live outside the workspace directory as sibling folders.

RepositoryRoot/
├── Project/
│   ├── App.xcworkspace
│   ├── App.xcodeproj
│   ├── TestPlans/
│   │   └── App.xctestplan
│   └── AppSource/
│       └── ...
│
├── Modules/
│   ├── API/
│   │   ├── Package.swift
│   │   └── Sources/
│   ├── FeatureA/
│   │   ├── Package.swift
│   │   └── Sources/
│   ├── FeatureB/
│   │   ├── Package.swift
│   │   └── Sources/
│   └── FeatureC/
│       ├── Package.swift
│       └── Sources/
│
└── ...

The important part is that the workspace and test plan live under Project/, while some Swift packages live outside that directory as sibling folders under Modules/. As a result, the test plan contains package test targets with container paths like container:../Modules/FeatureA.

When I use the workspace path as the base path, the tool fails while reading the test plan because some test targets have container paths that include ../, for example pointing to packages outside the workspace directory.

Is this repository layout currently supported?

Thank you in advance.

[mikeger]

Hey @terrytanvc ,

thanks for reaching out. I think this setup could work out of the box, mostly because the tool is trying to work with absolute paths at all times. However, it might be the case that in some specific place it's not correctly unwrapping paths with ... I think the easiest way would be to try to run it naively and to see the result. If there are any issues, please share what is not working and it should be pretty straightforward to fix in specific cases.

Best regards
Michael