I think there needs to be a distinction between verbosity and clarity. For me code that is clear with precise wording of methods and functions is important, even if these need to be more verbose. Amount of boiler-plate code on the hand is undesired.
In terms of testing, I think defining the requirements inline with the tests that are meant to implement those requirements provides value, removes ambiguity and is easier for those coming to a new code base (or coming back to one).
In terms of testing, I think defining the requirements inline with the tests that are meant to implement those requirements provides value, removes ambiguity and is easier for those coming to a new code base (or coming back to one).