1) [chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario TypeError: Cannot read properties of undefined (reading 'id') at utils/scenario.ts:27 25 | // Create a new scenario with a unique name 26 | const scenario = await postApiRequest( > 27 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`, | ^ 28 | { 29 | ...scenarioData, 30 | name: `${scenarioData.name} ${uuidv4()}`, at setupScenario (/app/tests/utils/scenario.ts:27:50) at /app/tests/004-scenario-management.spec.ts:17:35

2) [chromium] › 010-op-route-tab.spec.ts:67:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study Error: Timed out 10000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('dropped-via-info').nth(1).getByTestId('via-dropped-name') Expected string: "Mid_East_station" Received string: "" Call log: - expect.toHaveText with timeout 10000ms - waiting for getByTestId('dropped-via-info').nth(1).getByTestId('via-dropped-name') at pages/operational-studies-page-model.ts:304 302 | expectedUic: string 303 | ) { > 304 | await expect(OperationalStudiesPage.getWaypointDroppedNameLocator(droppedWaypoint)).toHaveText( | ^ 305 | expectedName 306 | ); 307 | await expect(OperationalStudiesPage.getWaypointDroppedChLocator(droppedWaypoint)).toHaveText( at Function.validateAddedWaypoint (/app/tests/pages/operational-studies-page-model.ts:304:89) at OperationalStudiesPage.addNewWaypoints (/app/tests/pages/operational-studies-page-model.ts:351:36) at /app/tests/010-op-route-tab.spec.ts:89:5

3) [firefox] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario TypeError: Cannot read properties of undefined (reading 'id') at utils/scenario.ts:27 25 | // Create a new scenario with a unique name 26 | const scenario = await postApiRequest( > 27 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`, | ^ 28 | { 29 | ...scenarioData, 30 | name: `${scenarioData.name} ${uuidv4()}`, at setupScenario (/app/tests/utils/scenario.ts:27:50) at /app/tests/004-scenario-management.spec.ts:17:35

4) [firefox] › 010-op-route-tab.spec.ts:67:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study Error: Timed out 10000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('dropped-via-info').nth(1).getByTestId('via-dropped-name') Expected string: "Mid_East_station" Received string: "" Call log: - expect.toHaveText with timeout 10000ms - waiting for getByTestId('dropped-via-info').nth(1).getByTestId('via-dropped-name') at pages/operational-studies-page-model.ts:304 302 | expectedUic: string 303 | ) { > 304 | await expect(OperationalStudiesPage.getWaypointDroppedNameLocator(droppedWaypoint)).toHaveText( | ^ 305 | expectedName 306 | ); 307 | await expect(OperationalStudiesPage.getWaypointDroppedChLocator(droppedWaypoint)).toHaveText( at Function.validateAddedWaypoint (/app/tests/pages/operational-studies-page-model.ts:304:89) at OperationalStudiesPage.addNewWaypoints (/app/tests/pages/operational-studies-page-model.ts:351:36) at /app/tests/010-op-route-tab.spec.ts:89:5

4) [firefox] › 010-op-route-tab.spec.ts:67:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 10000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('dropped-via-info').nth(1).getByTestId('via-dropped-name') Expected string: "Mid_East_station" Received string: "" Call log: - expect.toHaveText with timeout 10000ms - waiting for getByTestId('dropped-via-info').nth(1).getByTestId('via-dropped-name') at pages/operational-studies-page-model.ts:304 302 | expectedUic: string 303 | ) { > 304 | await expect(OperationalStudiesPage.getWaypointDroppedNameLocator(droppedWaypoint)).toHaveText( | ^ 305 | expectedName 306 | ); 307 | await expect(OperationalStudiesPage.getWaypointDroppedChLocator(droppedWaypoint)).toHaveText( at Function.validateAddedWaypoint (/app/tests/pages/operational-studies-page-model.ts:304:89) at OperationalStudiesPage.addNewWaypoints (/app/tests/pages/operational-studies-page-model.ts:351:36) at /app/tests/010-op-route-tab.spec.ts:89:5

4) [firefox] › 010-op-route-tab.spec.ts:67:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 10000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('dropped-via-info').nth(1).getByTestId('via-dropped-name') Expected string: "Mid_East_station" Received string: "" Call log: - expect.toHaveText with timeout 10000ms - waiting for getByTestId('dropped-via-info').nth(1).getByTestId('via-dropped-name') at pages/operational-studies-page-model.ts:304 302 | expectedUic: string 303 | ) { > 304 | await expect(OperationalStudiesPage.getWaypointDroppedNameLocator(droppedWaypoint)).toHaveText( | ^ 305 | expectedName 306 | ); 307 | await expect(OperationalStudiesPage.getWaypointDroppedChLocator(droppedWaypoint)).toHaveText( at Function.validateAddedWaypoint (/app/tests/pages/operational-studies-page-model.ts:304:89) at OperationalStudiesPage.addNewWaypoints (/app/tests/pages/operational-studies-page-model.ts:351:36) at /app/tests/010-op-route-tab.spec.ts:89:5

5) [firefox] › 010-op-route-tab.spec.ts:111:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study Test timeout of 90000ms exceeded.

5) [firefox] › 010-op-route-tab.spec.ts:111:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study Error: locator.waitFor: Test timeout of 90000ms exceeded. Call log: - waiting for getByTestId('missing-params-info') to be visible at pages/operational-studies-page-model.ts:255 253 | '' 254 | ); > 255 | await this.missingParamMessage.waitFor(); | ^ 256 | const actualMessage = await this.missingParamMessage.innerText(); 257 | expect(actualMessage).toContain(expectedMessage); 258 | } at OperationalStudiesPage.clickOnDeleteOPButtons (/app/tests/pages/operational-studies-page-model.ts:255:36) at /app/tests/010-op-route-tab.spec.ts:141:5

The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

[webkit] › 006-stdcm-page.spec.ts took 15.1s