Make integration test fully async

[slang25]

Attempt to kill almost all blocking code, this removes all the occurences in the test projects. There are only 2 places left now:

• Fluent API, this we are well aware of
• Thottled.cs, this one is tricky and could be hit under contention when at throttling limits, I have an idea on how to fix this in a non-breaking way. For another PR.

Something is going on with line-endings, I don't know if it's me, or if the code base needs all lines normalizing. I'll investigate.

[martincostello]

There’s been a few seemingly massive diffs in other PRs due to line endings too. I guess we’re in need of a .gitattributes fix to ensure we’re not at the mercy of people’s local settings?

[AnthonySteele]

Hm, we have a .editorconfig, but sometimes that's not enough and a compatible .gitattributes file is also needed.

[slang25]

Because we were hitting the fluent api code (that blocks) previously in the constructor, it was "harmless".

Now we are using async initialization, we deadlock the xunit SynchronizationContext.
There are lot's of hacky workarounds, I've opted here for disabling concurrent tests (which means xunit doesn't use it's special context). 🤠

[martincostello]

@slang25 I noticed you have an old fluent-refactor lying around here. Do you still need it?

[slang25]

I'd like to keep it for reference, I'll move it into my fork and delete it from this repo

[slang25]

Any progress on a JustBehave release?

[adammorr]

@slang25 https://www.nuget.org/packages/JustBehave/2.0.0-beta-62 will be a thing once NuGet updates

[slang25]

Thanks @adammorr !

[martincostello]

I’ll review this tomorrow 👍🏻

[slang25]

Thanks, it's pretty boring I'm afraid!

[martincostello]

Just some minor points but otherwise, great job!

[martincostello]

[slang25]

I'll look at the failure over lunch

[slang25]

I've put the tests back to running sequentially now, there are too many areas that require exclusivity. Ready now @martincostello

[martincostello]

Go go gadget tests!