@enact/ui-test-utils 1.0.10 → 2.0.0-alpha.1

package/.travis.yml

@@ -1,7 +1,7 @@
 dist: jammy
 language: node_js
 node_js:
-    - node
+    - 21
 before_install:
     - sudo apt-get update
     - sudo apt-get install build-essential libcairo2-dev libpango1.0-dev libjpeg-dev libgif-dev librsvg2-dev

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Change Log
 
+## [2.0.0-alpha.1] (February 26, 2025)
+
+* Updated `eslint` to v9 and adopted flat config.
+* Added `--no-animation` option for screenshot test.
+
 ## [1.0.10] (October 31, 2024)
 
 * Updated dependencies.

package/README.md

@@ -35,7 +35,7 @@ and must be configured as a `devDependency` of the UI library.
    }
 ```
 
-6. Optionally configure different ESLint and git configuration rules using `.eslintrc.js` and
+6. Optionally configure different ESLint and git configuration rules using `eslint.config.js` and
    `.gitignore` files, respectively
 
 ## Creating tests
@@ -218,6 +218,15 @@ For example, filtering for the component 'Input'.
 npm run test-ui -- --visible --spec /Input
 ```
 
+### Running without animation effects
+
+The `--no-animation` option is used to pack Enact without animation.
+You can use this option to test the apps without animation effects.
+
+```bash
+npm run test-ss -- --no-animation
+```
+
 ### Loading sample apps in a browser
 
  This requires that a server be running on port 3000. If you have globally installed the `serve`

package/config/wdio.conf.js

@@ -47,7 +47,7 @@ module.exports.configure = (options) => {
 					process.env.CHROME_DRIVER = chromeDriverVersion;
 				}
 			} catch (error) {
-				console.log('ERROR: Cannnot find Chrome driver from Chrome ' + chromeVersionMajorNumber);
+				console.log('ERROR: Cannot find Chrome driver from Chrome ' + chromeVersionMajorNumber);
 				process.env.CHROME_DRIVER = 2.44;
 			}
 		}
@@ -95,7 +95,7 @@ module.exports.configure = (options) => {
 			// First, you can define how many instances should be started at the same time. Let's
 			// say you have 3 different capabilities (Chrome, Firefox, and Safari) and you have
 			// set maxInstances to 1; wdio will spawn 3 processes. Therefore, if you have 10 spec
-			// files and you set maxInstances to 10, all spec files will get tested at the same time
+			// files, and you set maxInstances to 10, all spec files will get tested at the same time
 			// and 30 processes will get spawned. The property handles how many capabilities
 			// from the same test should run tests.
 			//
@@ -224,8 +224,6 @@ module.exports.configure = (options) => {
 			/**
 			 * Gets executed before test execution begins. At this point you can access to all global
 			 * variables like `browser`. It is the perfect place to define custom commands.
-			 * @param {Array.<Object>} capabilities list of capabilities details
-			 * @param {Array.<String>} specs List of spec file paths that are to be run
 			 */
 			before: function () {
 				require('expect-webdriverio');

package/eslint.config.js

@@ -0,0 +1,34 @@
+const enactStrict = require('eslint-config-enact/strict');
+const globals = require('globals');
+
+const customGlobals = {
+	'browser': true,
+	'expect': true,
+	'$': true,
+	'$$': true
+};
+
+module.exports = [
+	...enactStrict,
+	{
+		languageOptions: {
+			ecmaVersion: 'latest',
+			sourceType: 'module',
+			globals: {
+				...globals.node,
+				...globals.mocha,
+				...customGlobals
+			},
+			parserOptions: {
+				ecmaFeatures: {
+					jsx: true
+				}
+			}
+		},
+		rules: {
+			'max-nested-callbacks': 'off',
+			'no-console': 'off',
+			'react/forbid-foreign-prop-types': 'off' // proptypes not removed in storybook config
+		}
+	}
+];