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

chore(applitools): making tests more static for consistent testing #28201

Merged
merged 1 commit into from
Jun 20, 2024

Conversation

rusackas
Copy link
Member

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

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@rusackas rusackas requested a review from geido April 24, 2024 16:59
@rusackas rusackas marked this pull request as ready for review May 8, 2024 07:07
@rusackas
Copy link
Member Author

rusackas commented May 8, 2024

@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(),
Copy link
Member

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?

Copy link
Member Author

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. ¯\_(ツ)_/¯

@rusackas
Copy link
Member Author

rusackas commented Jun 7, 2024

@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.

@rusackas rusackas merged commit 03143bf into master Jun 20, 2024
51 of 52 checks passed
@rusackas rusackas deleted the stabilizing-applitools branch June 20, 2024 16:42
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 4.1.0 labels Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/XS 🚢 4.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants