yoga/gentest/Gemfile.lock

GEM
  remote: https://rubygems.org/
  specs:
    childprocess (4.1.0)
    mini_portile2 (2.8.0)
    nokogiri (1.13.8)
      mini_portile2 (~> 2.8.0)
      racc (~> 1.4)
    racc (1.6.0)
    regexp_parser (2.6.0)
    rexml (3.2.5)
    rubyzip (2.3.2)
    selenium-webdriver (4.5.0)
      childprocess (>= 0.5, < 5.0)
      rexml (~> 3.2, >= 3.2.5)
      rubyzip (>= 1.2.2, < 3.0)
      websocket (~> 1.0)
    watir (6.19.1)
      regexp_parser (>= 1.2, < 3)
      selenium-webdriver (>= 3.142.7)
    webdrivers (5.1.0)
      nokogiri (~> 1.6)
      rubyzip (>= 1.3.0)
      selenium-webdriver (~> 4.0)
    websocket (1.2.9)

PLATFORMS
  ruby

DEPENDENCIES
  watir (~> 6.19.0)
  webdrivers (~> 5.1.0)

BUNDLED WITH
   2.1.4
Fix Generation of Tests from Fixtures Summary: https://github.com/facebook/yoga/pull/1116 added a change to the test generator "gentests.rb" to support a newer version of chromedriver, along with a change to the enum generator (not touched in this diff) to produce code consistent with the current tests, which seem to have been manually edited since last generation. I had trouble running the test generator locally, because it relies on unversioned third-party dependencies, whose APIs change. Looking at source history, it seems like each time someone wants to run the script, they end up updating its syntax to match whatever versions they pull in. This change adds a Gemfile and lock so that that the version of "watir" is locked, and so that we will also automatically pull in a consistent "chomedriver" version via the "webdrivers" gem. It includes the updates from the PR to be consistent with already output tests, and I have also updated the copyright header generation to no longer create lint warnings on newly generated tests (some of the previous ones were fixed manually it looks like). The test generator would still produce bodies which would fail clang-format, and were manually edited (causing generation to emit new lint warnings), so I updated the generator to suppress clang-format in the body of the generated files. Three tests, around the interaction of minimum dimensions and flexible children produce different results in Chrome now compared to when the tests were added, so running `gentests.rb` creates tests which break UTs. This doesn't seem like any sort of rounding, or device specific difference, so I have disabled these tests for now. While digging around, it does look like Chrome periodically will fix bugs in its own layout implementation which cause differences, like https://bugs.chromium.org/p/chromium/issues/detail?id=927066 Reviewed By: rozele, Andrey-Mishanin Differential Revision: D39907416 fbshipit-source-id: f88714ff038b42f935901783452df25eabb6ebb1 2022-09-29 22:25:24 -07:00			`GEM`
			`remote: https://rubygems.org/`
			`specs:`
			`childprocess (4.1.0)`
			`mini_portile2 (2.8.0)`
			`nokogiri (1.13.8)`
			`mini_portile2 (~> 2.8.0)`
			`racc (~> 1.4)`
			`racc (1.6.0)`
			`regexp_parser (2.6.0)`
			`rexml (3.2.5)`
			`rubyzip (2.3.2)`
			`selenium-webdriver (4.5.0)`
			`childprocess (>= 0.5, < 5.0)`
			`rexml (~> 3.2, >= 3.2.5)`
			`rubyzip (>= 1.2.2, < 3.0)`
			`websocket (~> 1.0)`
			`watir (6.19.1)`
			`regexp_parser (>= 1.2, < 3)`
			`selenium-webdriver (>= 3.142.7)`
			`webdrivers (5.1.0)`
			`nokogiri (~> 1.6)`
			`rubyzip (>= 1.3.0)`
			`selenium-webdriver (~> 4.0)`
			`websocket (1.2.9)`

			`PLATFORMS`
			`ruby`

			`DEPENDENCIES`
			`watir (~> 6.19.0)`
			`webdrivers (~> 5.1.0)`

			`BUNDLED WITH`
			`2.1.4`