Versionen im Vergleich

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.
Auszug
hiddentrue

Nuclos integration tests: IntelliJ, Docker, Selenium, standalone-chrome, groovy, /etc/hosts, VM parameters, JUnit.

globe with meridians Language: Deutsch · English

hammer and wrench Running the integration tests with IntelliJ (and Docker)

Run integration tests in IntelliJ – server tests (Groovy) and web client tests with Selenium/Docker.

Status
colourPurple
titleHow-to
Status
colourBlue
titleDeveloper
Status
colourGreen
titleUpdated: Jul 2026
Status
colourGrey
titleapplies to Nuclos 4.2026.x

Panel
bgColor#F4F5F7

On this page

Inhalt
maxLevel2
minLevel2

Run server and web client integration tests in IntelliJ – the web client tests use a Selenium container via Docker.

Setup

  • Start the server in IntelliJ on localhost.
  • Import the test nuclet (via REST, no rich client needed).
  • Test code under nuclos-integrationstests/src/test/groovy/org/nuclos/test.

Server integration tests

Start a *.groovy file under server (or the whole directory) via Run/Debug and wait for the results.

Web client integration tests

Codeblock
languagebash
docker run -d -p 4444:4444 -p 5900:5900 selenium/standalone-chrome-debug

Add the required hosts to /etc/hosts (Windows: %windir%\system32\drivers\etc\hosts), start the web client and set the VM parameters in IntelliJ (Edit Configurations → JUnit → Edit configuration templates…).

Info
titleSelenium parameters

Without a set selenium.server, the tests start their own Docker container that is deleted afterwards. Optional parameters: nuclos.webclient.screenshots, nuclos.failing.videos.path.

Related pages

gear Web client tests


E2E.

Open →

gear Setting up Docker


Docker.

Open →