e2e Test läuft mit Fehlermeldung nicht

Issue #1079 wontfix
Routing Plus BKG Team created an issue

Hi zusammen,

ich weiß nicht, ob das ein Bug oder eine falsche Konfiguration ist, jedoch konnten wir die e2e Tests nicht erfolgreich durchführen. Eine entsprechende Readme oder ein laufendes Beispiel in der Bitbucket Pipeline konnten wir auch nicht finden, an dem wir uns orientieren konnten.

Wir haben das Ganze in der 2.x als auch vue_dev Branch ausprobiert.

Was muss getan werden, um den e2e Test erfolgreich durchzuführen (auch in der alpha Version) und fehlerfrei durchlaufen zu lassen?

Was wir erwarten:

Beim Ausführen einer der folgenden Möglichkeiten

  • browsertest
  • browsertestWithDevServer
  • browsertestOnExternalServer

sollte eigentlich der e2e Test ausgeführt werden.

Was wir konfiguriert haben:

1)

Um den Browsertest durchzuführen, haben wir zudem in der devtools/webpack.browsertest.js entsprechend den gewünschten Port und Host angepasst (und https in unserem Fall auf false gestellt).

Die Parameter http://<My-Secet_URL>:<My-Port>werden auch entsprechend übernommen.

2)

In dem vue_dev branch mussten wir zudem noch die fehlenden Pakete

"dotenv": "16.3.1",

"selenium-webdriver": "4.12.0",

hinzufügen, da diese im Vergleich zu 2.x gefehlt haben.

3)

In der test/end2end/TestRunner.js haben wir zudem

in der localBypassList die URL / IP von unserem Server eingetragen.

Testweise haben wir auch die process.env.browser (Zeile 21) auf dem System mit einer Systemvariable belegt, sodass nicht der default Wert genommen wird browser = process.env.browser || "firefox,chrome,edge",.

Was stattdessen passiert:

Bei allen 3 Testvarianten kommt immer dieselbe Fehlermeldung.

Ich glaube, dass die Hauptursache an folgender Meldung liegt, aber wir wissen nicht, was das genau bedeutet und wie dieser zu beheben ist.

Field 'browser' doesn't contain a valid alias configuration

Hier die komplette Fehlermeldung:

$ npm install
...
$ npm start browsertest

> masterportal@3.0.0-alpha1 start
> webpack-dev-server --config devtools/webpack.dev.js "browsertest"

NOTICE: /some_long_path/masterportal/addons/addonsConf.json not found. Skipping all addons.
 wds: Project is running at http://<My-Secet_URL>:<My-Port>/
 wds: webpack output is served from /build/
 wds: Content not from webpack is served from /some_long_path//masterportal
 wdm: 
ERROR in Entry module not found: Error: Can't resolve 'browsertest' in '/some_long_path/masterportal'
resolve 'browsertest' in '/some_long_path/masterportal'
  Parsed request is a module
  using description file: /some_long_path/masterportal/package.json (relative path: .)
    Field 'browser' doesn't contain a valid alias configuration
    resolve as module
      /some_long_path/node_modules doesn't exist or is not a directory
      /another_search_path/node_modules doesn't exist or is not a directory
      /yet_another_search_path/node_modules doesn't exist or is not a directory
      /yet_yet_another_search_path/node_modules doesn't exist or is not a directory
      /yet_yet_yet_another_search_path/node_modules doesn't exist or is not a directory
      /node_modules doesn't exist or is not a directory
      looking for modules in /some_long_path/masterportal/node_modules
        using description file: /some_long_path/masterportal/package.json (relative path: ./node_modules)
          Field 'browser' doesn't contain a valid alias configuration
          using description file: /some_long_path/masterportal/package.json (relative path: ./node_modules/browsertest)
            no extension
              Field 'browser' doesn't contain a valid alias configuration
              /some_long_path/masterportal/node_modules/browsertest doesn't exist
            .wasm
              Field 'browser' doesn't contain a valid alias configuration
              /some_long_path/masterportal/node_modules/browsertest.wasm doesn't exist
            .mjs
              Field 'browser' doesn't contain a valid alias configuration
              /some_long_path/masterportal/node_modules/browsertest.mjs doesn't exist
            .js
              Field 'browser' doesn't contain a valid alias configuration
              /some_long_path/masterportal/node_modules/browsertest.js doesn't exist
            .json
              Field 'browser' doesn't contain a valid alias configuration
              /some_long_path/masterportal/node_modules/browsertest.json doesn't exist
            as directory
              /some_long_path/masterportal/node_modules/browsertest doesn't exist

ERROR in multi (webpack)-dev-server/client?http://<My-Secet_URL>:<My-Port> browsertest
Module not found: Error: Can't resolve 'browsertest' in '/some_long_path/masterportal'
resolve 'browsertest' in '/some_long_path/masterportal'
  Parsed request is a module
  using description file: /some_long_path/masterportal/package.json (relative path: .)
    Field 'browser' doesn't contain a valid alias configuration
    resolve as module
      /some_long_path/node_modules doesn't exist or is not a directory
      /another_search_path/node_modules doesn't exist or is not a directory
      /yet_another_search_path/node_modules doesn't exist or is not a directory
      /yet_yet_another_search_path/node_modules doesn't exist or is not a directory
      /yet_yet_yet_another_search_path/node_modules doesn't exist or is not a directory
      /node_modules doesn't exist or is not a directory
      looking for modules in /some_long_path/masterportal/node_modules
        using description file: /some_long_path/masterportal/package.json (relative path: ./node_modules)
          Field 'browser' doesn't contain a valid alias configuration
          using description file: /some_long_path/masterportal/package.json (relative path: ./node_modules/browsertest)
            no extension
              Field 'browser' doesn't contain a valid alias configuration
              /some_long_path/masterportal/node_modules/browsertest doesn't exist
            .wasm
              Field 'browser' doesn't contain a valid alias configuration
              /some_long_path/masterportal/node_modules/browsertest.wasm doesn't exist
            .mjs
              Field 'browser' doesn't contain a valid alias configuration
              /some_long_path/masterportal/node_modules/browsertest.mjs doesn't exist
            .js
              Field 'browser' doesn't contain a valid alias configuration
              /some_long_path/masterportal/node_modules/browsertest.js doesn't exist
            .json
              Field 'browser' doesn't contain a valid alias configuration
              /some_long_path/masterportal/node_modules/browsertest.json doesn't exist
            as directory
              /some_long_path/masterportal/node_modules/browsertest doesn't exist
[/some_long_path/node_modules]
[another_search_path]
[/yet_another_search_path/]
[/yet_yet_another_search_path/]
[/yet_yet_yet_another_search_path/node_modules]
[/node_modules]
[/some_long_path/masterportal/node_modules/browsertest]
[/some_long_path/masterportal/node_modules/browsertest.wasm]
[/some_long_path/masterportal/node_modules/browsertest.mjs]
[/some_long_path/masterportal/node_modules/browsertest.js]
[/some_long_path/masterportal/node_modules/browsertest.json]

Vielen Dank schon mal vorab.

Grüße

Comments (2)

  1. Sven Junker-Beyel

    Moin, End2End Tests sind für die Masteportal 3.0.0 Verison erstmal nicht vorgesehen, da diese in der Version 2 sehr instabil waren.

  2. Log in to comment