Webdriverio: wdio.conf.ejs no creado

Creado en 29 jul. 2017  ·  4Comentarios  ·  Fuente: webdriverio/webdriverio

El problema

Experimenté exactamente el mismo problema que el # 1568 que se cerró en ese entonces pero aztack lo informó nuevamente.

Cuando trato de configurar Webdriver IO después de instalarlo, aparece un error justo después de pasar por la interfaz de preguntas:

=========================
WDIO Configuration Helper
=========================

? Where do you want to execute your tests? On my local machine
? Which framework do you want to use? mocha
? Shall I install the framework adapter for you? Yes
? Where are your test specs located? ./test/*.js
? Which reporter do you want to use?  spec - https://github.com/webdriverio/wdio-spec-reporter
? Shall I install the reporter library for you? Yes
? Do you want to add a service to your test setup?  selenium-standalone - https://github.com/webdriverio/wdio-selenium-standalone
-service
? Shall I install the services for you? Yes
? Level of logging verbosity command
? In which directory should screenshots gets saved if a command fails? ./errorShots/
? What is the base url? http://localhost

Installing wdio packages:

Packages installed successfully, creating configuration file...
fs.js:651
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open '/Users/sarahdayan/Projets/communitytalk.com/node_modules/webdriverio/build/lib/helpers/wdio.conf.ejs'
    at Object.fs.openSync (fs.js:651:18)
    at Object.fs.readFileSync (fs.js:553:33)
    at renderConfigurationFile (/Users/sarahdayan/Projets/communitytalk.com/node_modules/webdriverio/build/lib/cli.js:292:28)
    at /Users/sarahdayan/Projets/communitytalk.com/node_modules/webdriverio/build/lib/cli.js:282:17
    at /Users/sarahdayan/Projets/communitytalk.com/node_modules/npm-install-package/index.js:31:5
    at ChildProcess.exithandler (child_process.js:262:7)
    at emitTwo (events.js:125:13)
    at ChildProcess.emit (events.js:213:7)
    at maybeClose (internal/child_process.js:897:16)
    at Socket.stream.socket.on (internal/child_process.js:340:11)
npm ERR! Test failed.  See above for more details.

Ambiente

Detalle

Me las arreglé para resolver el problema diciendo que no a la instalación del marco y omitiendo la selección de un reportero y agregando un servicio a mi configuración de prueba:

? Shall I install the framework adapter for you? No
? Which reporter do you want to use?
? Do you want to add a service to your test setup?

Luego los instalé y edité el wdio.conf.js manualmente, pero eso no es lo ideal.

¡Gracias por adelantado!

Comentario más útil

Me encontré con el mismo problema: el nodo 8.2.1 + hilo no funciona v0.27.5, el nodo 8.2.1 + npm 5.3.0 funciona, el nodo 7.10.1 + hilo funciona. ¿Alguna idea de dónde puede estar el problema?

=========================
WDIO Configuration Helper
=========================

? Where do you want to execute your tests? On my local machine
? Which framework do you want to use? cucumber
? Shall I install the framework adapter for you? Yes
? Where are your feature files located? ./features/**/*.feature
? Where are your step definitions located? ./features/step-definitions
? Which reporter do you want to use?  spec - https://github.com/webdriverio/wdio-spec-reporter
? Shall I install the reporter library for you? Yes
? Do you want to add a service to your test setup?  selenium-standalone - https://github.com/webdriverio/wdio-selenium-standalone-service,  phantomjs - https://github.com/cognitom/wdio-phantomjs-serv
ice
? Shall I install the services for you? Yes
? Level of logging verbosity silent
? In which directory should screenshots gets saved if a command fails? ./errorShots/
? What is the base url? http://localhost

el error es el mismo

Todos 4 comentarios

¿Puedes probar con Node v7.x?

@christian-bromann Acabo de probar con varias versiones de Node (v6.11.1, v7.0.0, v8.1.3, v8.2.1) y curiosamente, todas pasaron 😶 Tal vez algo estaba mal con mi copia local de Node cuando lo probé por primera vez hora.

Supongo que cualquier persona con el mismo problema solo necesitaría reinstalar o actualizar Node y eso debería ser suficiente.

Tengo el mismo problema: uso el nodo v8.1.2

Me encontré con el mismo problema: el nodo 8.2.1 + hilo no funciona v0.27.5, el nodo 8.2.1 + npm 5.3.0 funciona, el nodo 7.10.1 + hilo funciona. ¿Alguna idea de dónde puede estar el problema?

=========================
WDIO Configuration Helper
=========================

? Where do you want to execute your tests? On my local machine
? Which framework do you want to use? cucumber
? Shall I install the framework adapter for you? Yes
? Where are your feature files located? ./features/**/*.feature
? Where are your step definitions located? ./features/step-definitions
? Which reporter do you want to use?  spec - https://github.com/webdriverio/wdio-spec-reporter
? Shall I install the reporter library for you? Yes
? Do you want to add a service to your test setup?  selenium-standalone - https://github.com/webdriverio/wdio-selenium-standalone-service,  phantomjs - https://github.com/cognitom/wdio-phantomjs-serv
ice
? Shall I install the services for you? Yes
? Level of logging verbosity silent
? In which directory should screenshots gets saved if a command fails? ./errorShots/
? What is the base url? http://localhost

el error es el mismo

¿Fue útil esta página
0 / 5 - 0 calificaciones

Temas relacionados

Amrkamel1 picture Amrkamel1  ·  39Comentarios

jedwards1211 picture jedwards1211  ·  33Comentarios

christian-bromann picture christian-bromann  ·  58Comentarios

sullenor picture sullenor  ·  33Comentarios

syzer picture syzer  ·  44Comentarios