add relay backend (#964)

* add relay backend

* update relay github workflow

* extract shared e2e test helpers to new shared folder and other refactorings and improvements

* try fix docker test and make relay tests run sequentially

* try fix docker test

* try fix docker test

Author: Logende

.GITIGNORE

@@ -2,4 +2,5 @@ node_modules
 dist
 .idea
 out
-auxil
+auxil
+/meta_configurator/public/test-fixtures/

.github/workflows/e2e.yml

@@ -60,4 +60,4 @@ jobs:
         uses: actions/upload-artifact@v4
         with:
           name: playwright-report
-          path: ${{ github.workspace }}/meta_configurator/playwright-report/
+          path: ${{ github.workspace }}/meta_configurator/playwright-report/

.github/workflows/relay-tests.yml

@@ -0,0 +1,90 @@
+name: Relay Tests
+
+on:
+  push:
+    paths:
+      - 'relay/**'
+      - 'meta_configurator/e2e/**'
+      - 'meta_configurator/src/**'
+      - 'meta_configurator/package.json'
+      - 'meta_configurator/package-lock.json'
+      - 'tests/shared/**'
+  workflow_dispatch:
+
+jobs:
+  relay-tests:
+    name: Relay tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+
+      - name: Install relay dependencies
+        working-directory: ./relay
+        run: pip install -r requirements.txt -r requirements-dev.txt
+
+      - name: Run relay Python tests
+        working-directory: ./relay
+        run: pytest tests/ -v
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v4
+
+      - name: Set up Docker Compose
+        uses: docker/setup-compose-action@v2
+
+      - name: Show Docker tool versions
+        run: |
+          docker version
+          docker buildx version
+          docker compose version
+
+      - name: Run relay Docker smoke tests
+        run: bash relay/tests/test_docker.sh
+
+      - uses: actions/setup-node@v3
+        with:
+          node-version: '18'
+
+      - name: Cache npm dependencies
+        uses: actions/cache@v3
+        with:
+          path: |
+            meta_configurator/node_modules
+          key: ${{ runner.os }}-node-${{ hashFiles('meta_configurator/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-node-
+
+      - name: Cache Playwright browsers
+        uses: actions/cache@v3
+        with:
+          path: ~/.cache/ms-playwright
+          key: ${{ runner.os }}-playwright-${{ hashFiles('meta_configurator/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-playwright-
+
+      - name: Install MetaConfigurator dependencies
+        working-directory: ./meta_configurator
+        run: npm ci
+
+      - name: Build MetaConfigurator
+        working-directory: ./meta_configurator
+        run: npm run build --if-present
+
+      - name: Install Playwright browsers
+        working-directory: ./meta_configurator
+        run: npx playwright install --with-deps
+
+      - name: Start dev server and run relay E2E tests
+        working-directory: ./meta_configurator
+        run: npx start-server-and-test dev http://localhost:5173 test:e2e:relay
+
+      - name: Upload relay Playwright HTML report
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: playwright-report-relay
+          path: ${{ github.workspace }}/meta_configurator/playwright-report/

documentation_developer/README.md

@@ -44,7 +44,7 @@ To avoid/fix merge conflicts due to the automated formatting, you can do either:
 
 ## Tests
 
-For detailed testing descriptions, see [the testing documentation](TESTING.md)
+For detailed testing descriptions, see [the testing documentation](../tests/README.md)
 
 In short, run unit tests and end-to-end tests the following way:
 

documentation_developer/TESTING.md

@@ -35,3 +35,29 @@ The individual panels are hidden and de-coupled from each other.
 We do not have to test the interaction between, for example, the `textEditor` and the `guiEditor` and any other specific combination of two panels.
 Instead, we can test each panel type in isolation, together with the internal state of MetaConfigurator. 
 To manipulate or access the internal state of MetaConfigurator, the `test` panel can be used, see [utilsTestPanel.ts](utilsTestPanel.ts) for more information.
+
+# Settings Fixtures
+
+The `openApp` helper (in `utils.ts`) accepts an optional settings fixture file name. When provided, MetaConfigurator loads and merges those settings before rendering, which lets a test pre-configure anything that would otherwise require manual UI interaction:
+
+- **Visible panels per mode** — the `panels` key controls which panel types are shown in each editor mode (`dataEditor`, `schemaEditor`, `settings`) and which are hidden from the selector (`hidden`).  
+  This is especially useful for enabling the `test` panel (hidden by default), which exposes internal state for reading and writing in tests.
+- **Any other setting** — toolbar title, data format, performance limits, etc.
+
+The fixture file only needs to include the keys you want to override; all other settings retain their defaults (the merge is deep for objects, replacing for arrays).
+
+Example (`test-fixtures/settings_testpanel.json`) enables the `test` panel in schema editor mode:
+
+```json
+{
+  "panels": {
+    "schemaEditor": [
+      { "panelType": "textEditor", "mode": "schemaEditor", "size": 50 },
+      { "panelType": "test",       "mode": "schemaEditor", "size": 50 }
+    ],
+    "hidden": ["debug"]
+  }
+}
+```
+
+Providing a `schema` fixture alongside the `settings` fixture also skips the initial schema-selection dialog, which is required for any test that needs to interact with the app immediately after loading.

meta_configurator/e2e/README.md

@@ -1,5 +1,5 @@
 import { test, expect } from '@playwright/test';
-import {forceEditorMode, getCurrentEditorMode, openApp} from "./utils";
+import {forceEditorMode, getCurrentEditorMode, openApp} from "../../tests/shared/utils";
 import {SessionMode} from "../src/store/sessionMode";
 
 

meta_configurator/e2e/changeMode.spec.ts

@@ -1,6 +1,6 @@
 import {test, expect} from '@playwright/test';
-import {openApp} from './utils';
-import {tpGetData} from './utilsTestPanel';
+import {openApp} from '../../tests/shared/utils';
+import {tpGetData} from '../../tests/shared/utilsTestPanel';
 import {
     expandImportOptions,
     openCsvImportDialog,
@@ -9,7 +9,7 @@ import {
     submitCsvImport,
     uploadCsvFile,
     uploadCsvFileAndCheckProgress,
-} from './utilsCsvImport';
+} from '../../tests/shared/utilsCsvImport';
 import {SessionMode} from '../src/store/sessionMode';
 
 test('Import CSV as standalone table with default paths', async ({page}) => {

meta_configurator/e2e/csvImport.spec.ts

@@ -5,9 +5,9 @@ import {
     getCurrentEditorMode,
     openApp,
     openAppWithMode
-} from "./utils";
+} from "../../tests/shared/utils";
 import {SessionMode} from "../src/store/sessionMode";
-import {tpGetData} from "./utilsTestPanel";
+import {tpGetData} from "../../tests/shared/utilsTestPanel";
 
 test('Open the app and check that the initial mode is Data Editor', async ({ page }) => {
     // Go to the app
@@ -69,4 +69,4 @@ test('Go through the initial schema selection dialog', async ({ page }) => {
 
     // Click the button with "Example Schema"
     await page.getByRole('button', { name: 'Example Schema' }).click()
-});
+});

meta_configurator/e2e/openApp.spec.ts

@@ -2,16 +2,16 @@ import { test, expect } from '@playwright/test';
 import {
     forceEditorMode,
     openApp, selectInitialSchemaFromExamples,
-} from "./utils";
+} from "../../tests/shared/utils";
 import {
     addArrayItem, checkPropertyExistence, checkPropertyRequired,
     checkPropertySchemaViolation,
     checkStringProperty, editBooleanProperty,
     editNumberOrIntProperty,
     editStringProperty, expandOrCollapseProperty
-} from "./utilsGuiEditor";
+} from "../../tests/shared/utilsGuiEditor";
 import {SessionMode} from "../src/store/sessionMode";
-import {tpForceCurrentSelectedElement, tpForceData, tpGetData} from "./utilsTestPanel";
+import {tpForceCurrentSelectedElement, tpForceData, tpGetData} from "../../tests/shared/utilsTestPanel";
 
 test('Edit the feature testing example schema using the GUI Editor, testing basic editing and schema violations', async ({ page }) => {
     // Go to the app, pre-loading the test settings