pragmatic-objects / oo-atom

A Java polyfill for better code design
MIT License
23 stars 2 forks source link

RtChainTest.java:32-32: Improve test coverage and mutation... #39

Closed 0pdd closed 6 years ago

0pdd commented 7 years ago

The puzzle 8-fc507248 (from #8) in atom-codegen/src/test/java/oo/atom/r/RtChainTest.java (lines 32-32) has to be resolved: "Improve test coverage and mutation coverage for {@link RtChain}"

The puzzle was created by Sergey Kapralov on 10-Sep-17.

Estimate: 15 minutes, role: IMP.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

0pdd commented 7 years ago

@skapral please pay attention to this new issue.

skapral commented 6 years ago

@0crat in

0crat commented 6 years ago

@0crat in (here)

@skapral Job #39 is now in scope, role is DEV

0crat commented 6 years ago

@skapral/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

0crat commented 6 years ago

@skapral/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

0crat commented 6 years ago

@skapral/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

0crat commented 6 years ago

@skapral/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 commented 6 years ago

@skapral/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 commented 6 years ago

@skapral/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 commented 6 years ago

@skapral/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 commented 6 years ago

@skapral/z everybody who has role DEV are banned at #39; 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 commented 6 years ago

@skapral/z everybody who has role DEV is banned at #39; 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 commented 6 years ago

@skapral/z everybody who has role DEV is banned at #39; 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)