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

Assert s2_test #3

Open
ppKrauss opened this issue Oct 22, 2018 · 1 comment
Open

Assert s2_test #3

ppKrauss opened this issue Oct 22, 2018 · 1 comment

Comments

@ppKrauss
Copy link

The assert validation is very commom in software package distributions... PostgreSQL have assert clause since v9.5, so a possible option is to change all s2_test.sql (example).

Other option, the easiest, is to add at git a s2_test.txt file with the s2_test.sql, that is,
psql _etc_ < s2_test.sql > s2_test.txt.
So, any one can assert by diff... or checking md5sum s2_test.txt, the my is 7d80522b55bd6e3270fb8ffde3a161cd.


My s2_test.txt:

 s2_cellid_from_latlng 
-----------------------
   1152921504606846977
(1 row)

 s2_cellid_from_latlng 
-----------------------
  -8689295774057980903
(1 row)

        s2_latlng_from_cellid         
--------------------------------------
 (40.4999999678024,-105.499999974886)
(1 row)

.....

 s2_token_edge_neighbors 
-------------------------
 87696d
 876969
 876941
 876915
(4 rows)

 s2_token_contains 
-------------------
 f
(1 row)

 s2_token_contains 
-------------------
 t
(1 row)

 s2_token_intersects 
---------------------
 t
(1 row)

 s2_token_intersects 
---------------------
 t
(1 row)
@ppKrauss
Copy link
Author

Hum... only now I see because README.md say nothing:

  • md5sum results/s2_test.out = b0cf2b212cc571173cbcb46b3258ec09
  • md5sum expected/s2_test.out = b0cf2b212cc571173cbcb46b3258ec09

So they are identical... (perhaps redundant).

... But is not same as my s2_test.txt: it is impossible to check because s2_test.out is a mixed file. ideal is to save at git only the output to be really checked by other users.

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

No branches or pull requests

1 participant