what can be the reason?

Please provide more information including your CI provider and run commands or no one will be able to help with the limited amount of details. In the meantime, I'd suggest reviewing the documentation for your CI provider below, you might stumble upon something yourself 🙂 https://docs.cypress.io/guides/continuous-integration/ci-provider-examples

@lively-balloon-98986 In addition to your CI Provider and

cypress run

command, providing your .yml is helpful as well, if you have one.

Is this Bitbucket? I have no experience with this provider but just looking at your config vs the documented implementation for Cypress with Bitbucket, I don't see any

parallel

attributes defined which could certainly explain why you aren't getting the results you want. Have you reviewed this? https://docs.cypress.io/guides/continuous-integration/bitbucket-pipelines

@enough-truck-68085 i added project json where i configured parallel to true

You typically need to define parallelization in the CI configuration file too. For example, with Gitlab you need to provide the

parallel: x

value in a job to define how many machines to use. For Bitbucket, the Cypress example has this which I don't see in your

.yml

file.

my cloudbuild.yaml is not compiled with this way

I'm not familiar enough with Bitbucket but my guess is that you are missing something on the CI provider side. All I can offer you right now is to review the documentation that Cypress has provided with a working solution and see if you can identify what you are missing. If you are doing something different than standard yaml structuring too that could also impact what you are seeing. Maybe @adventurous-dream-20049 can provide more guidance

Hi! hoping i can help as i have a very similar stack in a lot of ways. Can we see what your

npm run system_test_parallel

script does? Since you're using nx if its not in your default options and you aren't calling the right configuration that could potentially be your problem. The script you need to run in your pipeline is something along the lines of

nx run <project-name>:e2e:parallel

env-cmd -f ./apps/web-app/.env.testing ./start.sh nx e2e web-app-e2e:e2e:parallel this is the script the flags i send are: "parallel": { "watch":false, "devServerTarget": "web-app:serve:development", "key": "b6a9b56c-8675-4197-bc08-9a5fb10a6dfc", "baseUrl": "http://127.0.0.1:4200/read", "record": true, "parallel": true, "group": "QAAutomationLabs", "video": false },

For me when I run

nx <target> <project-name>

nx converts that to

nx run <project-name>:<target>

Can you try changing that to

nx e2e web-app-e2e:parallel

instead? I think you are already specifying the target when you say nx e2e so you don't need to declare it again with the colon.

NX Cannot find configuration for task web-app-e2e:parallel getting that error @straight-grass-43954