Zoltán Tóth

Take a look at the code of TestThreadExecutionEventPublisher. You have to add the listener manually. So you have to resolve an ITestThreadExecutionEventPublisher from the thread container and call ...

If I understand well: it seems that the tests are executed based on the old feature file content, while LivingDoc is generated from the new feature file content. Is it possible that the pipeline in...

This is typically only the last line of the error output. Please check the previous lines of the output for additional information. You can also open a support ticket with the additional details.

What do you see in the SpecFlow+LivingDoc menu? Are there any errors in the browser console? The output indicates that the "Upload was successful", so theoretically the data should be available in ...

For the 2nd question - using the "Rerun failed tests" option - there is the following solution:  In the LivingDoc Plugin please configure the ProcessId and ThreadId placeholders in the filepath.Yo...

Nashrin Banu Syed Mohamed thanks for the update, great that it works! thathi I think the issue is not related to the stopAfterFailures but probably to the retryCount. The stopAfterFailures feature ...

I still don't think that this is related to Linux. If you use the command line you have to specify the runsettings explicitly on all platforms. Only Visual Studio has an "autodetect" feature. See t...

Some more thoughts: if you don't use runsettings then the default file name that is picked up is "Default.srprofile" with capital "D". the .srprofile has to be next to the test assembly. Make sure...

Hi, could you please run "dotnet test -v:d" and check the output? The "Using default config"  is printed by the SpecFlow framework telling that it uses the default SpecFlow configuration (there was...