nextcloud/__tests__/setup-testing-library.js

/**
 * SPDX-FileCopyrightText: 2024 Nextcloud GmbH and Nextcloud contributors
 * SPDX-License-Identifier: CC0-1.0
 */

import '@testing-library/jest-dom/vitest'
import 'core-js/stable/index.js'
chore: Move from Jest to vitest There are some benefits, like faster tests and thus saving CI time, but the main reason for me is: Jest still does not properly support ESM packages, this casues a lot of breaking stuff. Sometimes you need to adjust imports for mocking, and somethimes other random stuff break. Instead of wasting valuable developer lifetime we can use vitest which works perfectly with ESM. Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de> 2024-08-24 10:51:18 -04:00			`/**`
			`* SPDX-FileCopyrightText: 2024 Nextcloud GmbH and Nextcloud contributors`
			`* SPDX-License-Identifier: CC0-1.0`
			`*/`
refactor(test): migrate cypress component tests to vitest Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de> 2025-10-13 20:25:34 -04:00
chore: Move from Jest to vitest There are some benefits, like faster tests and thus saving CI time, but the main reason for me is: Jest still does not properly support ESM packages, this casues a lot of breaking stuff. Sometimes you need to adjust imports for mocking, and somethimes other random stuff break. Instead of wasting valuable developer lifetime we can use vitest which works perfectly with ESM. Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de> 2024-08-24 10:51:18 -04:00			`import '@testing-library/jest-dom/vitest'`
refactor(federatedfilesharing): Replace deprecated functions * Replace deprecated OC dialogs methods * Replace deprecated global jQuery with axios * Replace deprecated jQuery event with event bus * Add component + unit tests for new dialog Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de> 2024-10-15 19:03:40 -04:00			`import 'core-js/stable/index.js'`