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

moving engine teardown logic #1391

Conversation

MohabMohie
Copy link
Contributor

  • teardown logic was implemented inside the launcherSessionClosed action of JUNit's LauncherSessionListener. This caused several activities to happen multiple times in case of executing several classes.
  • moved it to testPlanExecutionFinished trigger in the TestExecutionListener implementation to ensure it runs only once.

- teardown logic was implemented inside the launcherSessionClosed action of JUNit's LauncherSessionListener. This caused several activities to happen multiple times in case of executing several classes.
- moved it to testPlanExecutionFinished trigger in the TestExecutionListener implementation to ensure it runs only once.

Signed-off-by: Mohab Mohie <Mohab.MohieElDeen@outlook.com>
@MohabMohie MohabMohie linked an issue Dec 6, 2023 that may be closed by this pull request
@MohabMohie MohabMohie marked this pull request as ready for review December 6, 2023 21:37
@MohabMohie MohabMohie merged commit a1dc27e into main Dec 6, 2023
2 of 19 checks passed
@MohabMohie MohabMohie deleted the 1280-bug-summary-reports-are-generated-3-times-on-ci-junit-tests branch December 6, 2023 21:37
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

Successfully merging this pull request may close these issues.

[Bug]: Summary reports are generated 3 times on ci (Junit tests)
1 participant