Skip to content

Addresses flaky test #458

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

Merged
merged 4 commits into from
Jul 8, 2017
Merged

Addresses flaky test #458

merged 4 commits into from
Jul 8, 2017

Conversation

flovilmart
Copy link
Contributor

No description provided.

@codecov
Copy link

codecov bot commented Jul 7, 2017

Codecov Report

Merging #458 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #458   +/-   ##
=======================================
  Coverage   85.39%   85.39%           
=======================================
  Files          46       46           
  Lines        3724     3724           
  Branches      854      854           
=======================================
  Hits         3180     3180           
  Misses        544      544

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 30cc5fc...ac3eb98. Read the comment docs.

@flovilmart flovilmart merged commit 13438fe into master Jul 8, 2017
@flovilmart flovilmart deleted the flaky-test branch July 8, 2017 16:39
@flovilmart
Copy link
Contributor Author

@dplewis you may wanna have a look on this flaky test, odd that it runs locally properly :)

@dplewis
Copy link
Member

dplewis commented Jul 8, 2017

@flovilmart Thanks for addressing this. I've been avoiding using .catch() and .fail() and only done.fail. Is REQUEST_ATTEMPT_LIMIT in parse server?

@flovilmart
Copy link
Contributor Author

No it’s in the JS SDK, it retired on errors, the skipped test works locally but not on the CI, or at least inconsistently.

@dplewis
Copy link
Member

dplewis commented Jul 8, 2017

I see you have fixed a lot of flaky tests on JS SDK and parse server. Have you seen a pattern with inconsistent test? This would help with future tests.

Does this.skip come from mocha?

I try to follow this javascript guide for ES6 conventions. Maybe include this or something similar in CONTRIBUTION.md
https://github.com/airbnb/javascript

@flovilmart
Copy link
Contributor Author

Skip comes from mocha yes, it let you keep a test in your suite explicitly skipping it. I don’t really understand why it sometimes fails,

flovilmart pushed a commit that referenced this pull request Aug 30, 2017
* Add Type Polygon to Schema and PolygonContains to query

* Corrects Guide Link in README.md (#457)

Just a small fix of `https` to `http` for the JS guide link, which is only available over `http`.

* Addresses flaky test (#458)

* Update ParseGeoPointTest.js

* Limit request attempts to 1

* explore

* Marks flaky test as pending

* Add methods `addAll`, `addAllUnique` and `removeAll` (#459)

* Add methods `addAll`, `addAllUnique` and `removeAll`

* Add methods `addAll`, `addAllUnique` and `removeAll`

* Add test for `addAll`, `addAllUnique` and `removeAll`

* Revert test case

* containsPoint

uses bounded box first then ray casting

* update parse-server to 2.6.0

* Add Type Polygon to Schema and PolygonContains to query

* containsPoint

uses bounded box first then ray casting

* update parse-server to 2.6.0
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.

2 participants