Add support for running on CI when “build for testing” agent is different to testing agent about swift-snapshot-testing HOT 10 OPEN

Thanks for reporting the issue (and PR, which I'll look at shortly)! Re: your suggestions:

1. Allow to look in Bundle resources for the snapshot file
2. Allow a run-time file search to find the path of the snapshot

Either of these sound like viable solutions, though we wanna think over the ramifications a bit.

Why there is StaticString for file parameter in assertSnapshot instead of String?

I think this is an oversight that we can fix.

from swift-snapshot-testing.

It could be environment variables like IMAGE_DIFF_DIR and FB_REFERENCE_IMAGE_DIR in iOSSnapshotTestCase.

from swift-snapshot-testing.

And just one small related question. Why there is StaticString for file parameter in assertSnapshot instead of String? So there is no way to pass a run-time requested string even from the caller's side.

from swift-snapshot-testing.

@vox-humana Unfortunately file needs to be passed to XCTFail as a StaticString, so this interface can't be changed.

from swift-snapshot-testing.

@stephencelis Oh, I see, it is sad. Thank you.

from swift-snapshot-testing.

With the #file macro changing its output in a future release of Swift (perhaps 5.4?), what's the plan to address storage paths? Having a standard ENV variable would at least be helpful to prevent general chaos over the #file -> #filePath transition

from swift-snapshot-testing.

Good afternoon, any news one this ?

from swift-snapshot-testing.

Xcode Cloud also runs the tests on a different machine to the build machine, so this suggestion would help there too. I'm currently using the technique discussed in this thread (#553) to make the snapshots accessible to the tests, but having the library support this case natively would be a cool addition!

from swift-snapshot-testing.

Any news on this? @stephencelis

from swift-snapshot-testing.

Any news regarding this?

from swift-snapshot-testing.