Create Improved Test Cases For File Paths Outside the LK Root

[bbimber]

[bbimber]

@labkey-jeckels: I think this question needs some thought, so I'm opening this issue.

The background is that Pipeline-related code can create scenarios that are difficult to replicate on TeamCity, and therefore automated tests can miss issues. Here are current ideas on steps to improve test coverage:

• I will make the existing SequencePipelineTests exercise cross-workbook file access: Make SequenceIntegrationTests work across-workbooks BimberLab/DiscvrLabKeyModules#364.
• ClusterModule has ClusterPipelineJob, which is a test-case pipeline job. I am going to see if I can make something that include the XarGenerator step, where I give it cross-folder filepaths as inputs/outputs.
• If future core code is going to tighten up allowable ExpData paths, it would be helpful if this had a more direct Integration test that did not require the overhead of XAR files and all of pipeline. The specific test cases I think that should include are: Container->/Shared, Container->Workbook, Workbook->Sibling-Workbook.

Other ideas are welcome.

[bbimber]

For the first one, the "Parent path not allowed" does repro on team city now: https://teamcity-artifacts.labkey.org/presignedTokenAuth/7e811e09-c288-4272-8dc6-09d79ae7ff5c/repository/download/LabKey_2511Release_External_Discvr_ExternalModulesTestPostgres/3771156:id/_serverLogs.tar.gz!/labkey-errors.log?__nodeId=primary