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

End-to-End studyview.spec.js is failing #7135

Closed
ecerami opened this issue Feb 9, 2020 · 2 comments · Fixed by cBioPortal/cbioportal-frontend#3049
Closed

End-to-End studyview.spec.js is failing #7135

ecerami opened this issue Feb 9, 2020 · 2 comments · Fixed by cBioPortal/cbioportal-frontend#3049
Assignees

Comments

@ecerami
Copy link
Contributor

ecerami commented Feb 9, 2020

According to the last few front-end PRs, studyview.spec.js is failing.

For details, see: https://circleci.com/gh/cBioPortal/cbioportal-frontend/61737?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

I think this is due to two (large) screenshots failing.

The screenshot tests within studyview.spec.js should also probably be moved out to a new studyview.screenshot.spec.js, so that it follows the convention.

I can try to fix this.

@inodb how do I find the screenshots that are generated by circle CI, so that I can check these in instead?

@ecerami ecerami self-assigned this Feb 9, 2020
@inodb
Copy link
Member

inodb commented Feb 9, 2020

@ecerami good catch! Looks like this is because of the backend binning fix for bar charts of integers on the study view (see also v3.2.2 release notes). The screenshot comparison tool can be found here:

https://61737-66571349-gh.circle-artifacts.com/0/imageCompare.html

You can get there by clicking on the "artifacts" tab of the circleci link you shared and clicking on imageCompare.html. At the bottom of the page there is a command that indicates how to update the screenshots. One needs to send in the screenshots through a pull request.

These tests aren't run on the backend which is why we didn't catch it earlier. We only run the localdb e2e tests on the backend as part of ci testing. If there are big backend changes in a release we currently run these frontend e2e tests manually after deploying to a test instance.

@ecerami
Copy link
Contributor Author

ecerami commented Feb 9, 2020

Thanks @inodb! I didn't see the artifact tab before, as I wasn't logged into circle CI.

I also wasn't sure if we wanted to break out the screenshot tests into its own file (that is part of #7134 discussion). But, I did follow the instructions on Circle CI and created a PR with updated screenshots.

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 a pull request may close this issue.

2 participants