-
Notifications
You must be signed in to change notification settings - Fork 14.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
chore(applitools): making tests more static for consistent testing #28201
Conversation
@geido I never got around to doing more of this Applitools stabilization. Should we just merge this one, and eventually open more like it? |
@@ -593,19 +593,19 @@ const shoppingData: ShoppingData[] = [ | |||
{ | |||
key: 1, | |||
item: 'Floppy Disk 10 pack', | |||
orderDate: Date.now(), | |||
orderDate: new Date('2015-07-02T16:16:00Z').getTime(), |
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.
Is there something akin to freezegun for frontend code?
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.
Good question! I'll try to remember to look into it, but I'm not sure of one offhand. I just picked the timestamp of Superset's first commit since it's pretty arbitrary here. ¯\_(ツ)_/¯
@justinpark @michael-s-molina might as well merge this thing if you don't see any reason not to. It fixes up the appltools stability of just one test. I thought I'd go deeper and grow the PR, but just haven't had time to. |
SUMMARY
Applitools is throwing visual regression errors because of things like Date.now()... this branch will serve as a place to start locking these things down as static, so our tests will be more meaningful than ignoring these zones in countless places.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION