Visual service and appium-windows-driver are not working together for iOS
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 25/100
- Tipo di issue
- Bug
- Chiarezza
- Da chiarire
- Stato di attività
- Ferma
- Stack tecnologico
- javascript, node.js
- Ambito
- mobile-dev, testing-qa
Direzione di ricerca
La riproduzione è collegata dall’issue e la configurazione che fallisce è wdio.conf.winappdriver.js; inizia eseguendo quell’esempio con le versioni di Node.js e dei pacchetti elencate. Traccia il fallimento attraverso ConfigParser.js di @wdio/config e stabilisci un comportamento atteso riproducibile per Visual service con la configurazione Windows/Appium; l’issue non definisce un esito positivo.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Environment (please complete the following information):
- Node.js version: v18.16.0
- NPM version: 9.5.1
- Browser name and version: we use winAppDriver
- Platform name and version: Windows 10
- WebdriverIO version: [e.g. 5.1.0]
@wdio/visual-serviceversion: [e.g. 1.0.0]
"devDependencies": {
"@types/jasmine": "^3.4.1",
"@types/node": "^12.20.55",
"@wdio/appium-service": "^5.12.1",
"@wdio/cli": "^5.10.1",
"@wdio/dot-reporter": "5.13.2",
"@wdio/jasmine-framework": "^5.12.1",
"@wdio/junit-reporter": "^5.12.1",
"@wdio/local-runner": "^5.10.1",
"@wdio/visual-service": "^3.0.2",
"appium": "1.15.0",
"canvas": "^2.11.2",
"prettier": "^1.18.2",
"rimraf": "3.0.0",
"ts-node": "^8.4.1",
"tsconfig-paths": "^3.8.0",
Config of WebdriverIO + @wdio/visual-service
An example of how you configured the @wdio/visual-service
const { join } = require('path');
exports.config = {
// ...
// =====
// Setup
// =====
services: [
['visual', {
// Some options, see the docs for more
baselineFolder: join(process.cwd(), 'tests', 'baseline'),
formatImageName: '{tag}-{logName}-{width}x{height}',
screenshotPath: join(process.cwd(), 'tmp'),
savePerInstance: true,
autoSaveBaseline: true,
blockOutStatusBar: true,
blockOutToolBar: true,
// NOTE: When you are testing a hybrid app please use this setting
isHybridApp: false,
// Options for the tabbing image
tabbableOptions: {
circle: {
size: 18,
fontSize: 18,
// ...
},
line: {
color: "#ff221a", // hex-code or for example words like red|black|green
width: 3,
},
},
// ... more options
}]
],
Describe the bug
An error is thrown when running the tests
To Reproduce
Steps to reproduce the behavior:
[Include code or an example repository that can easily be set up]
Expected behavior
A clear and concise description of what you expected to happen.
Log
2024-02-19T16:39:10.502Z ERROR @wdio/config:ConfigParser: Failed loading configuration file: C:\Users\dubli\OneDrive\Des
ktop\1\JavaScript\packages\webdriverio\wdio.conf.winappdriver.js: require() of ES Module C:\Users\dubli\OneDrive\Desktop
\1\JavaScript\packages\webdriverio\wdio.conf.winappdriver.js from C:\Users\dubli\OneDrive\Desktop\1\JavaScript\node_modu
les@wdio\config\build\lib\ConfigParser.js not supported.
wdio.conf.winappdriver.js is treated as an ES module file as it is a .js file whose nearest parent package.json contains
"type": "module" which declares all .js files in that package scope as ES modules.
Instead rename wdio.conf.winappdriver.js to end in .cjs, change the requiring code to use dynamic import() which is avai
lable in all CommonJS modules, or change "type": "module" to "type": "commonjs" in C:\Users\dubli\OneDrive\Desktop\1\Jav
aScript\packages\webdriverio\package.json to treat all .js files as CommonJS (using .mjs for all ES modules instead).
C:\Users\dubli\OneDrive\Desktop\1\JavaScript\node_modules@wdio\config\build\lib\ConfigParser.js:43
var fileConfig = (0, _deepmerge.default)(require(filePath).config, {}, MERGE_OPTIONS);
^
Error [ERR_REQUIRE_ESM]: require() of ES Module C:\Users\dubli\OneDrive\Desktop\1\JavaScript\packages\webdriverio\wdio.c
onf.winappdriver.js from C:\Users\dubli\OneDrive\Desktop\1\JavaScript\node_modules@wdio\config\build\lib\ConfigParser.j
s not supported.
wdio.conf.winappdriver.js is treated as an ES module file as it is a .js file whose nearest parent package.json contains
"type": "module" which declares all .js files in that package scope as ES modules.
Instead rename wdio.conf.winappdriver.js to end in .cjs, change the requiring code to use dynamic import() which is avai
lable in all CommonJS modules, or change "type": "module" to "type": "commonjs" in C:\Users\dubli\OneDrive\Desktop\1\Jav
aScript\packages\webdriverio\package.json to treat all .js files as CommonJS (using .mjs for all ES modules instead).
at ConfigParser.addConfigFile (C:\Users\dubli\OneDrive\Desktop\1\JavaScript\node_modules\@wdio\config\build\lib\Conf
igParser.js:43:48)
at new Launcher (C:\Users\dubli\OneDrive\Desktop\1\JavaScript\node_modules@wdio\cli\build\launcher.js:33:23)
at launch (C:\Users\dubli\OneDrive\Desktop\1\JavaScript\node_modules@wdio\cli\build\run.js:63:20)
at run (C:\Users\dubli\OneDrive\Desktop\1\JavaScript\node_modules@wdio\cli\build\run.js:45:12)
at Object.run (C:\Users\dubli\OneDrive\Desktop\1\JavaScript\node_modules@wdio\cli\build\index.js:36:20)
at Object. (C:\Users\dubli\OneDrive\Desktop\1\JavaScript\node_modules@wdio\cli\bin\wdio.js:11:21) {
code: 'ERR_REQUIRE_ESM'
}
Node.js v18.16.0
npm ERR! Lifecycle script test failed with error:
Additional context
Add any other context about the problem here.
- Lingua principale
- TypeScript
- Stelle
- 153
- Fork
- 59
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di webdriverio/visual-testing
-
bug third party bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
webdriverio/visual-testing#1127 · 1 commento ·
-
help wanted
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
webdriverio/visual-testing#985 · 1 commento ·
-
bug enhancement
webdriverio/visual-testing#783 · 5 commenti · 1 assegnatario ·
-
Wait for Screenshot to Match Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
webdriverio/visual-testing#690 ·
-
enhancement
webdriverio/visual-testing#515 · 1 commento · 1 assegnatario ·
Tutte le issue di webdriverio/visual-testing
Issue simili
-
blocklist removal
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
pastelsky/bundlephobia#1122 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100