Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

run-multiple reporting of failed steps not working #4254

Open
AramSol opened this issue Mar 15, 2024 · 7 comments
Open

run-multiple reporting of failed steps not working #4254

AramSol opened this issue Mar 15, 2024 · 7 comments

Comments

@AramSol
Copy link

AramSol commented Mar 15, 2024

What are you trying to achieve?

We aim to obtain reports on failing scenario steps when using "run-multiple --all".

What do you get instead?

there is no report of the failing scenario steps
image

Details

  • CodeceptJS version:3.5.14
  • NodeJS Version: 21.6.1
  • Operating System: windows
  • webdriverio
  • Configuration file:
    image

there was also a fix that was related to this issue that only fix the reporting of the scenario steps on scenario level wen we use run instead of run-multiple
#4020

related issue #3283

@AramSol AramSol changed the title reporting of failed tests in the scenario not working run-multiple reporting of failed steps not working Apr 4, 2024
@C5278607
Copy link

C5278607 commented Apr 5, 2024

I have the same problem.

@bko17
Copy link

bko17 commented Apr 5, 2024

We found to have the same issue. It makes identifying the exact problem super cumbersome. Some support would be greatly appreciated .

@AramSol
Copy link
Author

AramSol commented May 6, 2024

@kobenguyent any suggestions here?

@kobenguyent
Copy link
Collaborator

AFAIK, run-multiple command is kinda obsolete and there would be not really active maintenance. It is encouraged to use run-workers command.

@AramSol
Copy link
Author

AramSol commented May 23, 2024

@kobenguyent Thanks for the suggestion! I changed our run-test command to run-workers, which significantly reduced the running time of our test workflows. Unfortunately, the issue with reporting is still there.

Copy link

This issue is stale because it has been open for 90 days with no activity.

@github-actions github-actions bot added the stale label Aug 22, 2024
@AramSol
Copy link
Author

AramSol commented Aug 27, 2024

any update here?

@github-actions github-actions bot removed the stale label Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants