You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for specifying the UI testing screenshot behavior in a scheme test action (#942)
* Support for specifying UI testing snapshot behavior in scheme test action
* Add tests for new screenshot scheme options
* Update changelog
* Add new fields to Scheme.Test json encoding
* Only save values to JSON if they aren't the defaults
* Using new defaults constants
Copy file name to clipboardExpand all lines: Docs/ProjectSpec.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -814,6 +814,8 @@ A multiline script can be written using the various YAML multiline methods, for
814
814
- [ ] **coverageTargets**: **[String]** - a list of targets to gather code coverage. Each entry can either be a simple string, or a string using [Project Reference](#project-reference)
815
815
- [ ] **targets**: **[[Test Target](#test-target)]** - a list of targets to test. Each entry can either be a simple string, or a [Test Target](#test-target)
816
816
- [ ] **customLLDBInit**: **String** - the absolute path to the custom `.lldbinit` file
817
+
- [ ] **captureScreenshotsAutomatically**: **Bool** - indicates whether screenshots should be captured automatically while UI Testing. This defaults to true.
818
+
- [ ] **deleteScreenshotsWhenEachTestSucceeds**: **Bool** - whether successful UI tests should cause automatically-captured screenshots to be deleted. If `captureScreenshotsAutomatically` is false, this value is ignored. This defaults to true.
817
819
818
820
#### Test Target
819
821
- [x] **name**: **String** - The name of the target
0 commit comments