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

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,18 @@
 # Change Log
 
+## [2.0.0-alpha.2] (March 7, 2025)
+
+* Updated `webdriverio` and related dependencies to version 9.
+* Dropped support for Node.js 16. Required Node.js version >= 18.
+* Removed deprecated `@wdio/selenium-standalone-service` module and added `wdio-selenium-standalone-service` community package.
+* Removed `w3c: false` and replaced with `'wdio:enforceWebDriverClassic': true` when running tests on a remote debugger. w3c enforces the usage of JSON Wire Protocol which has been removed from `webdriverio` v9.
+* Replaced deprecated dependency `wdio-image-comparison-service` with `@wdio/visual-service`.
+
+## [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;
 			}
 		}
@@ -72,12 +72,18 @@ module.exports.configure = (options) => {
 			// Specify Test Files
 			// ==================
 			// Define which test specs should run. The pattern is relative to the directory
-			// from which `wdio` was called. Notice that, if you are calling `wdio` from an
-			// NPM script (see https://docs.npmjs.com/cli/run-script) then the current working
-			// directory is where your package.json resides, so `wdio` will be called from there.
+			// of the configuration file being run.
+			//
+			// The specs are defined as an array of spec files (optionally using wildcards
+			// that will be expanded). The test for each spec file will be run in a separate
+			// worker process. In order to have a group of spec files run in the same worker
+			// process enclose them in an array within the specs array.
+			//
+			// The path of the spec files will be resolved relative from the directory of
+			// the config file unless it's absolute.
 			//
 			specs: [
-				'./tests/' + base + '/specs/**/*-specs.js'
+				'../../tests/' + base + '/specs/**/*-specs.js'
 			],
 			// Patterns to exclude.
 			exclude: [
@@ -95,7 +101,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.
 			//
@@ -112,6 +118,11 @@ module.exports.configure = (options) => {
 				maxInstances,
 				//
 				browserName: 'chrome',
+				/* WebdriverIO v8.14 and above downloads and uses the latest Chrome version when running tests.
+				We need to specify a browser version that matches chromedriver version running in CI/CD environment to
+				ensure testing accuracy.
+				TODO: Update this version when chromedriver version in CI/CD is updated */
+				browserVersion: '120.0.6099.109',
 				'goog:chromeOptions': visibleBrowser ? {} : {
 					args: ['--headless', '--window-size=1920,1080']
 				}
@@ -175,24 +186,7 @@ module.exports.configure = (options) => {
 			// commands. Instead, they hook themselves up into the test process.
 			services: [
 				['selenium-standalone', {
-					skipSeleniumInstall: offline,
-					args: {
-						drivers : {
-							chrome : {
-								version : process.env.CHROME_DRIVER,
-								arch    : process.arch
-							}
-						}
-					},
-					installArgs: {
-						drivers : {
-							chrome : {
-								version : process.env.CHROME_DRIVER,
-								arch    : process.arch,
-								baseURL : process.env.CHROME_DRIVER > 114 ? 'https://storage.googleapis.com' : 'https://chromedriver.storage.googleapis.com'
-							}
-						}
-					}
+					skipSeleniumInstall: offline
 				}],
 				['static-server', {
 					folders: [
@@ -224,8 +218,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
+		}
+	}
+];