don't require method JavaDoc for tests

[yegor256]

I believe method JavaDoc blocks are redundant. Instead, we should use reasons for assertThat(). See https://github.com/yegor256/cactoos/blob/master/src/test/java/org/cactoos/io/InputAsBytesTest.java

[0crat]

@krzyk please, pay attention to this issue

[nqafield]

And then you've got to wonder if the test method names are also redundant. (Or the reasons.) :)

[krzyk]

@0crat in

[0crat]

@0crat in (here)

@krzyk Job #848 is now in scope, role is DEV

[0crat]

Bug was reported, see §29: +15 point(s) just awarded to @yegor256/z

[0crat]

@krzyk/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV are banned at #848; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV are banned at #848; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV is banned at #848; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV is banned at #848; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV is banned at #848; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@krzyk/z everybody who has role DEV is banned at #848; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[krzyk]

@0crat assign me

[0crat]

@0crat assign me (here)

@krzyk The job #848 assigned to @krzyk/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

[0crat]

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @krzyk/z

[krzyk]

@yegor256 please close this issue, it has been merged to master in #947 (and should be released on 0.18.3)

[krzyk]

@0crat waiting for review from issue author

[0crat]

@0crat waiting for review from issue author (here)

@krzyk The impediment for #848 was registered successfully by @krzyk/z

[krzyk]

@yegor256 ping, it has been released on 0.18.4

[yegor256]

@krzyk thanks!

[0crat]

The job #848 is now out of scope

[0crat]

Order was finished: +30 point(s) just awarded to @krzyk/z