Support test screenshot configuration options

[sanghun0724]

Add configuration for scroll performance testing

Background

When measuring scroll performance using FPS in Xcode, the current test configuration options in Tuist don't provide accurate measurement environments. For example, without disabling certain settings, what should be 60 FPS is incorrectly measured as 30 FPS.

Tuist Configurable Options Checklist

Tips for creating performance tests:

• Create a separate test scheme for your Performance XCTest ✅
• Use Release Build Configuration and uncheck Debug executable ✅
• Switch off Automatic Screenshots and Code Coverage ❌
• Turn off all diagnostic options, checkers, sanitizers and memory management ✅

ref: https://developer.apple.com/videos/play/wwdc2020/10077/

Proposed Solution

I propose to add two test configuration options:

1. captureScreenshotsAutomatically: This will allow users to disable automatic screenshots during testing, which is crucial for accurate scroll performance measurements.

2. deleteScreenshotsWhenEachTestSucceeds: This option will work in conjunction with captureScreenshotsAutomatically to configure AttachmentLifeTime (currently not utilized in Tuist).

These additions will help developers obtain more accurate performance measurements and better manage test artifacts.

Impact

• Enables accurate FPS measurements for scroll performance testing
• Provides more granular control over test screenshot behavior
• Improves overall test environment configuration capabilities

Note

The following PR will be submitted to Tuist based on this work

[fortmarek]

Would you mind creating the counterpart PR in Tuist? We usually don't merge PRs in XcodeGraph until the counterpart PR in Tuist is approved.

[fortmarek]

This technically constitutes a breaking change which we are trying to avoid.

I'd consider adding the new options to TestingOptions instead.

[fortmarek]

I'd suggest to model these options more closer to how they are modeled in XcodeProj: https://github.com/tuist/XcodeProj/blob/9f26d78d72ef40dd2e35f624bbcde1e3b28762cf/Sources/XcodeProj/Scheme/XCScheme%2BTestAction.swift#L42

[sanghun0724]

I'd consider adding the new options to TestingOptions instead.

got it. Will make the change right away.

[sanghun0724]

I'd suggest to model these options more closer to how they are modeled in XcodeProj:
https://github.com/tuist/XcodeProj/blob/9f26d78d72ef40dd2e35f624bbcde1e3b28762cf/Sources/XcodeProj/Scheme/XCScheme%2BTestAction.swift#L42

What do you think about this comment? I believe that structuring variables closer to the xcodeproj model as you suggested might make it less user-friendly from an user perspective. (There are no such Boolean values for captureScreenshotsAutomatically and deleteScreenshotsWhenEachTestSucceeds)

[fortmarek]

captureScreenshotsAutomatically definitely should be an enum as you can select between screenshots and recordings. That wasn't the case when that comment was posted.

Also, XcodeGraph is not something Tuist users directly interact with and I think we benefit from keeping the way we structure things somewhat similar. So, I'd still be for aligning with XcodeProj.