Gáspár Nagy
Gáspár Nagy
@markdoth Yes, this is a known limitation. As far as I know, this can be solved by emitting a wrapper method call that uses the feature file position as the...
Do you get the error when you use it from NuGet? https://www.nuget.org/packages/SpecFlow.xUnitAdapter/
@ChristopherHaws that makes sense. Could you add this `DefaultItemExcludes` to the targets file? @instecjason Could you please confirm the workaround?
@robertbird that's an interesting issue. Do you want to dig into the xUnit source code to figure out how these values are populated? (https://github.com/xunit/xunit)
> @gasparnagy should still work for Tricentis as a freelancer. That is unfortunately not true. They haven't renewed my contract (yet?). So @bollhals I suggest contacting them at [email protected].
@jonathansapp Thx! Could you please also add a line about this change to the bodi.cs header (change history)?
This makes sense. Let's come back to it when we have moved away from the single-file approach.
Hi @leotsarev! Yes, you are right, probably it should be made more clear that it is not thread safe. SpecFlow manages 4 level of contexts (and the related containers): global,...
@leotsarev @Greybird Thank you for your comments. Two clarifications: * running the scenario async is normally not a problem, because even though there will be multiple threads allocated, there will...
I haven't got further reports about server block for a while, so I close this issue, but please reopen if reqnroll.net or docs.reqnroll.net is not accessible from your company network.