c51ff3bce1
* feat: add installExtension integration test This adds a new helper function called `runCodeServerCommand` along with a test for `--install-extension`. We can use this approach for writing integration tests (i.e. testing a real code-server build, CLI commands, etc). * refactor: s/ test:standalone with test:integration This replaces our integration approach to use Jest instead of a single bash script. By doing this, we will be able to easily maintain and add to our integration test suite. * refactor: filter unit tests Now that our integration tests also use Jest, we need to update our unit test script to ignore `test/integration`. * refactor: add SKIP_SUBMODULE_DEPS to postinstall * refactor: add SKIP_SUBMODULE_DEPS to postinstall * fixup!: skip submod deps * refactor: move runCodeServerCommand into sep. file When Jest runs a test, it loads all the files and imports for that test. This means you might be "requiring" code that's unrelated to your tests. This leads to unexpected errors depending on where the code runs. Moved this file to avoid GLIBC and other errors relaed to argon2 when running integration tests in CI. * fizup: formatting * fizup: increase timeout * refactor: use fixture in installExtension test Instead of relying on a network to install an extension, we use a fixture - vsix file in the repo. This is also faster. * feat: add integration test for listExtensions * chore: ignore integration fixtures * fixup: formatting * fixup: remove custom-hacks.css * fixup: formatting * Update test/integration/installExtension.test.ts Co-authored-by: Asher <ash@coder.com> * Update test/integration/listExtensions.test.ts Co-authored-by: Asher <ash@coder.com> * Update test/integration/installExtension.test.ts Co-authored-by: Asher <ash@coder.com> * Update test/integration/listExtensions.test.ts Co-authored-by: Asher <ash@coder.com> * fixup: contributing integration tests section * fixup: update ci/readme * fixup: use RELEASE_PATH in test-integration.sh * refactor: unzip vsix for listExtensions * refactor: use exec instead of spawn * Update docs/CONTRIBUTING.md Co-authored-by: Asher <ash@coder.com> * Update test/integration/listExtensions.test.ts Co-authored-by: Asher <ash@coder.com> * Update test/integration/listExtensions.test.ts Co-authored-by: Asher <ash@coder.com> * Update test/integration/listExtensions.test.ts Co-authored-by: Asher <ash@coder.com> * refactor: use different default binary path * fixup!: formatting Co-authored-by: Asher <ash@coder.com>
31 lines
1.3 KiB
TypeScript
31 lines
1.3 KiB
TypeScript
import { rename } from "fs/promises"
|
|
import path from "path"
|
|
import extract from "extract-zip"
|
|
import { clean, tmpdir } from "../utils/helpers"
|
|
import { runCodeServerCommand } from "../utils/runCodeServerCommand"
|
|
|
|
describe("--list-extensions", () => {
|
|
const testName = "listExtensions"
|
|
const extName = `wesbos.theme-cobalt2`
|
|
const extVersion = "2.1.6"
|
|
const vsixFileName = `${extName}-${extVersion}.vsix`
|
|
let tempDir: string
|
|
let setupFlags: string[]
|
|
|
|
beforeEach(async () => {
|
|
await clean(testName)
|
|
tempDir = await tmpdir(testName)
|
|
setupFlags = ["--extensions-dir", tempDir]
|
|
const extensionFixture = path.resolve(`./test/integration/fixtures/${vsixFileName}`)
|
|
// Make folder because this is where we'll move the extension
|
|
const pathToUnpackedExtension = path.join(tempDir, `${extName}-${extVersion}`)
|
|
const tempPathToUnpackedExtension = path.join(tempDir, `${extName}-temp`)
|
|
await extract(extensionFixture, { dir: tempPathToUnpackedExtension })
|
|
await rename(path.join(tempPathToUnpackedExtension, "extension", pathToUnpackedExtension))
|
|
})
|
|
it("should list installed extensions", async () => {
|
|
const { stdout } = await runCodeServerCommand([...setupFlags, "--list-extensions"])
|
|
expect(stdout).toMatch(extName)
|
|
}, 20000)
|
|
})
|