-
Notifications
You must be signed in to change notification settings - Fork 77
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
Tests for layer filter feature #424
Tests for layer filter feature #424
Conversation
I am running in to the following error for the tests I've commented out. I tried to run the tests without the hash using the test.html file using |
e7eb367
to
0a8a9b8
Compare
Can't seem to get it to work, unfortunately. :( What do you think @sagarpreet-chadha? Do you think we should check the filtering for every single layer or just that the filtering works? If its the latter we've already done that in layerMenu.spec.js:
|
I think it's fine to test the general functionality of the filter and not intertwine it with each individual layer. I appreciate your linking to the relevant Cypress test! Hashes are a little bit undersupported in general as a UI, so it's not super surprising. So, this should be good to go then? Thanks!! |
Yes let's not go deep into each layer file filtering. Great efforts 🙌 !!! |
Great! The general functionality for layer filtering has already been tested in the layersMenu spec. We could close this PR since it has already been done. The only difference is in the spec included in this PR I am not only checking the layer count but also the layers individually. |
These tests would fail because of the recent changes if we merge with master. I'll push the fix in case we decide to keep it. |
916f5df
to
f3a9839
Compare
f3a9839
to
2b0a083
Compare
Sorry about that. These tests will have errors only when PR #428 merged. I guess I am a bit disoriented seeing how much I confused myself over this. 😅 |
OK, awesome!!! |
Fixes #423 (<=== Add issue number here)
Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!
@publiclab/reviewers
for help, in a comment belowIf tests do fail, click on the red
X
to learn why by reading the logs.Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software
Thanks!