Joshua Gleitze
Joshua Gleitze
I like the proposal! But I think that this part: > We could even check if equals is overriden and warn the user. is _essential_. Because with overridden `equals`, the...
I like the idea! With the following wording the message would be easier to understand for me: > Atrium detected that your expectation would have been met if you expected...
My issue with ‘used’ is that it is ambiguous _where_ `\r\n` should have been used. Although not both interpretations are equally likely, the sentence could be read as > if...
> if you had used `\r\n` instead of `\n` in the expected string :+1:
1. I think `all` is not a good name because we already have `Expect.all`. 2. What is your use case that makes you want to avoid fail-late behaviour?
> making the stacktrace point to a correct assertion is very useful. I agree with this. Not only for the shortened feature syntax, but in general. However, I think it...
> We could also get the line number by creating a stacktrace. How would you find out which stack trace entry to take? > Do you think such a feature...
> E.g. by creating an exception when creating the feature extraction. Yeah, I got that, but which of the stack trace’s entries is the one to show to the user,...
@StragaSevera would one of these solutions address your use case? Or would you still want to have a way to make lambda blocks fail-fast? If yes, why?
> it is not shown with Junit5 That’s a bummer. > if the default does not show it, then it is not a solution I’m not sure about this, since...