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) [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

3) [webkit] › 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) [webkit] › 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.innerText: Error: strict mode violation: getByTestId('selected-rolling-stock-info') resolved to 2 elements: 1) <span class="rollingstock-info-end" data-testid="selec…>rollingstock_1500_25000_test_e2e</span> aka getByTestId('rollingstock-rollingstock_1500_25000_test_e2e').locator('div').filter({ hasText: 'rollingstock_1500_25000_test_e2eID30' }).first() 2) <span class="rollingstock-info-end" data-testid="selec…>rollingstock_1500_25000_test_e2e</span> aka getByTestId('rollingstock-selector') Call log: - waiting for getByTestId('selected-rolling-stock-info') at pages/operational-studies-page-model.ts:400 398 | await electricRollingstockCard.click(); 399 | await electricRollingstockCard.locator('button').click(); > 400 | expect(await rollingStockSelector.getSelectedRollingStockName.innerText()).toEqual( | ^ 401 | rollingStockName 402 | ); 403 | } at OperationalStudiesPage.selectRollingStock (/app/tests/pages/operational-studies-page-model.ts:400:67) at /app/tests/010-op-route-tab.spec.ts:123:5

5) [webkit] › 011-op-times-and-stops-tab.spec.ts:75:7 › Times and Stops Tab Verification › should correctly set and display times and stops tables Error: locator.innerText: Error: strict mode violation: getByTestId('selected-rolling-stock-info') resolved to 2 elements: 1) <span class="rollingstock-info-end" data-testid="selec…>dual-mode_rollingstock_test_e2e</span> aka getByTestId('rollingstock-dual-mode_rollingstock_test_e2e').locator('div').filter({ hasText: 'dual-modedual-modedual-' }).first() 2) <span class="rollingstock-info-end" data-testid="selec…>dual-mode_rollingstock_test_e2e</span> aka getByTestId('rollingstock-selector') Call log: - waiting for getByTestId('selected-rolling-stock-info') at pages/operational-studies-page-model.ts:400 398 | await electricRollingstockCard.click(); 399 | await electricRollingstockCard.locator('button').click(); > 400 | expect(await rollingStockSelector.getSelectedRollingStockName.innerText()).toEqual( | ^ 401 | rollingStockName 402 | ); 403 | } at OperationalStudiesPage.selectRollingStock (/app/tests/pages/operational-studies-page-model.ts:400:67) at /app/tests/011-op-times-and-stops-tab.spec.ts:97:5

6) [webkit] › 011-op-times-and-stops-tab.spec.ts:166:7 › Times and Stops Tab Verification › should correctly update and clear input table row Error: locator.innerText: Error: strict mode violation: getByTestId('selected-rolling-stock-info') resolved to 2 elements: 1) <span class="rollingstock-info-end" data-testid="selec…>dual-mode_rollingstock_test_e2e</span> aka getByTestId('rollingstock-dual-mode_rollingstock_test_e2e').locator('div').filter({ hasText: 'dual-modedual-modedual-' }).first() 2) <span class="rollingstock-info-end" data-testid="selec…>dual-mode_rollingstock_test_e2e</span> aka getByTestId('rollingstock-selector') Call log: - waiting for getByTestId('selected-rolling-stock-info') at pages/operational-studies-page-model.ts:400 398 | await electricRollingstockCard.click(); 399 | await electricRollingstockCard.locator('button').click(); > 400 | expect(await rollingStockSelector.getSelectedRollingStockName.innerText()).toEqual( | ^ 401 | rollingStockName 402 | ); 403 | } at OperationalStudiesPage.selectRollingStock (/app/tests/pages/operational-studies-page-model.ts:400:67) at /app/tests/011-op-times-and-stops-tab.spec.ts:180: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: 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: 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/