Gáspár Nagy
Gáspár Nagy
> I'm betting anyone who runs CI in Azure Devops pipelines will have this issue. How many others is that? I think the vast majority of the users just run...
> Whatever you do to fix the issue: Just keep it as before I don't think that aggressive communication helps the situation. Please keep in mind that you are using...
Thx @regnalebnala and @StarWars999123 for the comments. I agree that the fact that the parameters vary by changes of other scenarios in the file is not good. We will need...
> What's the idea of such example dupllications as in MyScenario? We would have considered it at least to be a bad test design habit, but I would expect it...
Yes, this is an NUnit issue. @tbaliukynas You can try to run the tests as `dotnet test --logger "console;verbosity=detailed"`
I have also tried in the meantime, but I haven't found any way to provide an output even in a simple (non-Reqnroll) NUnit project... So we can't do much. You...
Released with v3.3.0 today: https://github.com/reqnroll/Reqnroll/releases/tag/v3.3.0
I also attach the full log. From there is is visible that the whole task was running in 36s and the timeout happened after 18 seconds after the previous message,...
@mpkorstanje these changes are "technically" breaking changes, but in practice they will not break any code, because we still have the support for ".NET Standard 2.0" which anyway covers all...