Skip to content

Parallel Execution With SpecFlow/Extent Report - With Report Scenarios Getting Logged Under The Lastly Executed Thread #72

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

Open
ramgkn opened this issue Nov 5, 2019 · 4 comments
Labels
bug Something isn't working
Milestone

Comments

@ramgkn
Copy link

ramgkn commented Nov 5, 2019

Hi Team,

I am in the process of enabling Parallel Execution for One of My Project; however ended up in a situation where I am able to execute test cases parallelly but the ExtentReport is generating wearied report - all the Test Steps are logged under the last scenario that got executed; where as i

have executed 3 separate feature files.

Solution that i am working on along with sample report attached. Tired to workout on couple of solution suggested in google with no luck . Can somebody give me direction on this.

ExtentReport_Local.zip

ParallelExecution.zip

@ramgkn
Copy link
Author

ramgkn commented Nov 5, 2019

@anshooarora - tired the solution from this repository location for Parallel Execution but not able to figure out where my solution is going wrong.. - just thought of adding this comment up

@ramgkn ramgkn changed the title Parallel Execution With SpecFlow - With Report Scenarios Getting Logged Under The Lastly Executed Thread Parallel Execution With SpecFlow/Extent Report - With Report Scenarios Getting Logged Under The Lastly Executed Thread Nov 7, 2019
@anshooarora
Copy link
Member

Will look into this.

@anshooarora anshooarora added the question Further information is requested label Jan 27, 2020
@Vardhan18
Copy link

Hi @anshooarora,

Facing the same issue while running in parallel. Scenarios are getting updated (sometimes) under random features but when running in sequential order steps are updated properly.
Attached the html report in txt format.

Any updates on the fixes ?
index .txt

@anshooarora anshooarora added bug Something isn't working and removed question Further information is requested labels Apr 21, 2020
@anshooarora anshooarora removed the api label Aug 6, 2020
@anshooarora anshooarora added this to the v5.0.x milestone Aug 6, 2020
@gnaneswarreddy
Copy link

Same happening for me as well @anshooarora is there any possibility to look in to this early?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants