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

dev/core#938 Stabalize Attachment API Test #15066

Merged
merged 1 commit into from
Aug 18, 2019

Conversation

seamuslee001
Copy link
Contributor

Overview

This aims to ensure that tests are more stable, by testing each stable part separately and only allow a deviation by 1 on the timestamp

Before

Test can be flaky

After

Test stable

ping @demeritcowboy @eileenmcnaughton @totten

@civibot
Copy link

civibot bot commented Aug 18, 2019

(Standard links)

@seamuslee001
Copy link
Contributor Author

Jenkins re test this please

@seamuslee001 seamuslee001 merged commit e8f9158 into civicrm:master Aug 18, 2019
@seamuslee001 seamuslee001 deleted the attachment_api_stablize branch August 18, 2019 07:31
@seamuslee001 seamuslee001 changed the title Stabalize Attachment API Test dev/core#938 Stabalize Attachment API Test Aug 18, 2019
@seamuslee001
Copy link
Contributor Author

@demeritcowboy
Copy link
Contributor

@seamuslee001 Thanks that seems like a good compromise to avoid touching the security fix code. But should the tolerance parameter be 2? That approxEquals function was new to me so I looked at it and the comparison is a strict less than, so the way I read it a tolerance of 1 actually means zero tolerance for integers?

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

Successfully merging this pull request may close these issues.

3 participants