brew/Library/Homebrew/test/support/fixtures/cask/Casks/with-two-apps-subdir.rb

cask 'with-two-apps-subdir' do
  version '1.2.3'
  sha256 'd687c22a21c02bd8f07da9302c8292b93a04df9a929e3f04d09aea6c76f75c65'

  url "file://#{TEST_FIXTURE_DIR}/cask/caffeines-subdir.zip"
  homepage 'https://brew.sh'

  app 'Caffeines/Caffeine Mini.app'
  app 'Caffeines/Caffeine Pro.app'
end
Remove `TestCask` class. 2017-02-03 21:52:51 +01:00			`cask 'with-two-apps-subdir' do`
init 2016-08-18 22:11:42 +03:00			`version '1.2.3'`
Dummy Caffeine app. 2016-08-20 05:08:16 +02:00			`sha256 'd687c22a21c02bd8f07da9302c8292b93a04df9a929e3f04d09aea6c76f75c65'`
init 2016-08-18 22:11:42 +03:00
Move cask fixtures to `test/fixtures/cask`. 2016-10-22 00:48:30 +02:00			`url "file://#{TEST_FIXTURE_DIR}/cask/caffeines-subdir.zip"`
Use Homebrew-controlled domain for Cask dummy URLs In a number of Cask specs, the value of the `homepage` stanza is currently set to https://example.com. As of 2018-11-28, the TLS certificate served by example.com seems to be expired, possibly due to an oversight on ICANN’s side. While the certificate is certainly going to be renewed soon, it would be desirable for Homebrew’s test result to be less dependent on ICANN’s actions. This commit changes the homepages of all test Casks to http://brew.sh, whose domain and TLS certificate are both controlled by Homebrew. 2018-11-28 20:51:55 +01:00			`homepage 'https://brew.sh'`
init 2016-08-18 22:11:42 +03:00
Dummy Caffeine app. 2016-08-20 05:08:16 +02:00			`app 'Caffeines/Caffeine Mini.app'`
			`app 'Caffeines/Caffeine Pro.app'`
init 2016-08-18 22:11:42 +03:00			`end`