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

Refactor test fixtures #113

Merged
merged 1 commit into from
Feb 5, 2019
Merged

Refactor test fixtures #113

merged 1 commit into from
Feb 5, 2019

Conversation

mourner
Copy link
Member

@mourner mourner commented Feb 5, 2019

  • Moved expected number of triangles and deviation thresholds to a separate expected.json file.
  • Set the default deviation to 0 and added non-0 deviations explicitly so that there's a clear list of tests that aren't expected to triangulate perfectly.

This will potentially allow us to keep the tests between earcut and earcut-cpp in sync easier. cc @mrgreywater

@mrgreywater
Copy link
Collaborator

This will help quite a bit keeping the fixtures in sync, I like it!

@mourner mourner merged commit 52b3674 into master Feb 5, 2019
@mourner mourner deleted the cleaner-tests branch February 5, 2019 13:19
mourner added a commit that referenced this pull request Aug 19, 2019
* master: (32 commits)
  fix incorrect equality case in intersection test (#114)
  refactor test fixtures (#113)
  fix test for #111
  update readme for 2.1.5
  2.1.5
  fix a race condition with coincident chain of holes (#112)
  upgrade deps
  update readme
  2.1.4
  fix a race condition that could lead to a hang
  Reuse fixture files in benchmarks (#100)
  Replace vertice with vertex in documentation (#97)
  upgrade deps, update scripts
  2.1.3
  Search with equal priority in both z-order directions
  update changelog
  2.1.2
  fix a few race conditions (port from C++) (#90)
  Support export default (#88)
  upgrade deps
  ...
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