sourcegraph/client/browser/scripts/test-integration.js

const shelljs = require('shelljs')

const { decompressRecordings, deleteRecordings } = require('./utils')

// eslint-disable-next-line no-void
void (async () => {
  await decompressRecordings()
  shelljs.exec('POLLYJS_MODE=replay pnpm run-integration', async code => {
    await deleteRecordings()
    process.exit(code)
  })
})()
bext: refactor integration tests (#33598) 2022-04-13 08:03:08 +00:00			`const shelljs = require('shelljs')`

			`const { decompressRecordings, deleteRecordings } = require('./utils')`

			`// eslint-disable-next-line no-void`
			`void (async () => {`
			`await decompressRecordings()`
chore(ci): remove Percy visual tests (#63515) These are more frequently erroneous than helpful. See https://sourcegraph.slack.com/archives/C04MYFW01NV/p1719209633005499. This eliminates a source of frustration and flakiness in pull requests and removes a lot of code and Bazel complexity. If we want to revive them, we can revert this commit. Note that `client/web-sveltekit` does not use Percy, and if we want it to, we can always revert this commit or start over from scratch if that's easier. <!-- PR description tips: https://www.notion.so/sourcegraph/Write-a-good-pull-request-description-610a7fd3e613496eb76f450db5a49b6e --> ## Test plan CI Co-authored-by: Jean-Hadrien Chabran <jean-hadrien.chabran@sourcegraph.com> 2024-06-27 14:20:06 +00:00			`shelljs.exec('POLLYJS_MODE=replay pnpm run-integration', async code => {`
bext: refactor integration tests (#33598) 2022-04-13 08:03:08 +00:00			`await deleteRecordings()`
			`process.exit(code)`
			`})`
			`})()`