balena-supervisor/test/integration/.mocharc.js

module.exports = {
	bail: true, // Exit test script on first error
	exit: true, // Force Mocha to exit after tests complete
	recursive: true, // Look for tests in subdirectories
	require: [
		// Files to execute before running suites
		'ts-node/register/transpile-only',
		'tsconfig-paths/register',
		'test/lib/chai.ts',
		'mocha-pod/skip-setup',
	],
	spec: ['test/integration/**/*.spec.ts'],
	timeout: '30000',
};
Create `test/unit` and `test/integration` folders This sets up the new `test/unit` and `test/integration` folders and starts classification of some of the test files. Note that unit tests include, `fs-utils` and `system-info` tests. While these tests interact with the filesystem, the implementation of these modules is simple enough, and the tests are fast enough to allow these tests to fall under the `unit` test category (according to test/README) Change-type: patch 2022-08-18 22:50:13 +00:00			`module.exports = {`
			`bail: true, // Exit test script on first error`
			`exit: true, // Force Mocha to exit after tests complete`
			`recursive: true, // Look for tests in subdirectories`
			`require: [`
			`// Files to execute before running suites`
			`'ts-node/register/transpile-only',`
			`'tsconfig-paths/register',`
			`'test/lib/chai.ts',`
Setup docker-compose.test This allows to run integration tests during development and on CI with the right dependencies. There are several changes that this involves, but the gist of it is that a test environment is setup using `docker-compose.test.yml`. This file is loaded by `resin-ci` during the build, and ensures that integration tests are ran after setting up all requirements. This commit also defines a test environment command that can be setup using `npm run test:env` in order to run tests in a local development machine. 2022-08-22 23:54:21 +00:00			`'mocha-pod/skip-setup',`
Create `test/unit` and `test/integration` folders This sets up the new `test/unit` and `test/integration` folders and starts classification of some of the test files. Note that unit tests include, `fs-utils` and `system-info` tests. While these tests interact with the filesystem, the implementation of these modules is simple enough, and the tests are fast enough to allow these tests to fall under the `unit` test category (according to test/README) Change-type: patch 2022-08-18 22:50:13 +00:00			`],`
			`spec: ['test/integration/*/.spec.ts'],`
			`timeout: '30000',`
			`};`