Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sure record/verify/properties actually affect test tasks #690

Merged
merged 6 commits into from
Apr 5, 2023

Conversation

TWiStErRob
Copy link
Contributor

@TWiStErRob TWiStErRob commented Jan 19, 2023

See #206 (comment)

Fixes #747

Copy link
Collaborator

@jrodbx jrodbx left a comment

Choose a reason for hiding this comment

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

thanks!

@TWiStErRob TWiStErRob changed the title Make sure executing record/verify actually affects test tasks Make sure record/verify/properties actually affect test tasks Jan 20, 2023
@TWiStErRob
Copy link
Contributor Author

Related Gradle feature: gradle/gradle#9092

@TWiStErRob
Copy link
Contributor Author

Is there anything missing here @jrodbx?

Copy link
Collaborator

@jrodbx jrodbx left a comment

Choose a reason for hiding this comment

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

Approved again with updated comments. Also, please rebase and squash. Thanks for fixing this!

Comment on lines 168 to 177
// Explicitly register these as inputs so that they are considered when determining up-to-date.
// The properties become resolvable after the last afterEvaluate runs.
test.inputs.property("paparazzi.test.record", isRecordRun)
test.inputs.property("paparazzi.test.verify", isVerifyRun)
Copy link
Collaborator

Choose a reason for hiding this comment

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

style nit: can we move this under the other "inputs" (just after "paparazzi.nativePlatform")? also, let's remove the comment, since this is standard Gradle knowledge.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I moved it together with the systemProperties, i.e. the first inputs, because they're an implementation detail of the missing inputs.property(name, provider) API.

@jrodbx jrodbx added this to the 1.3 milestone Mar 24, 2023
TWiStErRob and others added 2 commits March 30, 2023 17:00
…ify parameters are not playing in up to date checks and fix by registering inputs explicitly.

Co-authored-by: John Rodriguez <john.rodriguez@gmail.com>
… builds.

It's a standard HashMap not a DomainObjectCollection, so there won't be any further items inserted between filterKeys and doFirst.
@TWiStErRob
Copy link
Contributor Author

Addressed all the comments in separate commits, when merging select squash merge please.

@TWiStErRob
Copy link
Contributor Author

Extracted 44a7737 to #748

@jrodbx jrodbx merged commit bd1dd1a into cashapp:master Apr 5, 2023
13 checks passed
@TWiStErRob TWiStErRob deleted the rerunrecordverify branch May 11, 2023 10:35
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.

verify does not take in to account resource changes
2 participants