-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
[test] Improve visual regression tests #19175
[test] Improve visual regression tests #19175
Conversation
75af979
to
7db3fed
Compare
Details of bundle changes.Comparing: 91168ef...c7c05d8
|
abfc009
to
4707968
Compare
4707968
to
c7c05d8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm missing why some tests where deleted outright. Did you just merge some tests into a single screenshot or actually removed some tests? If so why did you choose certain tests over others?
@eps1lon We used to write dedicated visual regression tests before including all the demos. |
The one change I was unsure of was regarding the removal of the system tests. I have assumed that it would be equivalent to testing the output of the style functions, as plain JavaScript objects. |
I had a chat with @gregberge, told me that the company we wrote Argos for runs it on a dedicated Heroku instance, with 1,000 screenshots/PR and 100 workers. So, It seems that it will be able to scale, it's more a matter of pouring a few $/month to support the server infrastructure. So, it seems that the main bottleneck for us will be how we generate these screenshots (serial generation) and these weird random timeouts (>30s). |
You have to uploads screenshot in two different batches: |
Thanks for the tip. |
We have had a bunch of test fails related to uploading the screenshots to argos-ci. I believe it's because of the endpoint on Heroku timeout after 30s. In this effort, I plan to /2 the number of screenshots we do.
We will benefit from a faster CI.
Edit: the test fails seems to be related to something else, it could be postgresql/network/fs related. The reduction in the test reduction comes from fewer screenshots and ignoring the material icons search.
Before
After