Skip to content

Conversation

@daltonclaybrook
Copy link
Contributor

Resolves #941

@daltonclaybrook
Copy link
Contributor Author

I'm guessing that the Xcode 12 job was recently added? The failure looks unrelated to this PR.

@daltonclaybrook
Copy link
Contributor Author

@brentleyjones Is there any appetite for merging this change soon? My team in particular is definitely looking forward to it.

@brentleyjones
Copy link
Collaborator

I'm on paternity leave for a while.

@yonaskolb can you take a look?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seeing as though these 2 booleans end up as an enum, we could also just add a simple attachmentLifetime enum to the spec instead. Thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My thought was that the "attachment lifetime" is more of an implementation detail of the XCScheme rather than the Scheme in the project spec. From the user's perspective, the bools are a 1:1 mapping with these two checkboxes in the Xcode scheme editor. Happy to discuss this more, though.
Screen Shot 2020-09-06 at 12 07 11 PM

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yonaskolb any more thoughts on this? I'm happy to make this change if you think it's the right call.

@daltonclaybrook daltonclaybrook force-pushed the dalton/ui-testing-screenshots branch from d9dc697 to 8a29412 Compare September 7, 2020 15:55
@daltonclaybrook daltonclaybrook force-pushed the dalton/ui-testing-screenshots branch from 8a29412 to 27c985c Compare June 3, 2021 00:48
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you write these values below in toJSONValue if they differ from the default

@daltonclaybrook daltonclaybrook force-pushed the dalton/ui-testing-screenshots branch from 27c985c to 4d1f51a Compare June 21, 2021 16:04
"region": region,
"coverageTargets": coverageTargets.map { $0.reference },
"captureScreenshotsAutomatically": captureScreenshotsAutomatically,
"deleteScreenshotsWhenEachTestSucceeds": deleteScreenshotsWhenEachTestSucceeds,
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Sorry if it wasn't clear before, but these values should only be written to the dictionary if they are not their default value (true), like below. This is so generated specs only contain the required information

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, got it! This makes perfect sense. Will make the change right away.

Copy link
Owner

@yonaskolb yonaskolb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yonaskolb yonaskolb merged commit 66b1db4 into yonaskolb:master Jun 27, 2021
Copy link

@Hally21 Hally21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Scheme Test Action: Capture screenshots automatically

4 participants