Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(#1222) Fixed test methods sharing issue #1225

Merged
merged 3 commits into from
Nov 6, 2019
Merged

Conversation

fanifieiev
Copy link
Contributor

This pull request is for issue 1222

According to the article https://www.yegor256.com/2016/05/03/test-methods-must-share-nothing.html
the test methods must not share any methods or data.

@codecov-io
Copy link

codecov-io commented Nov 4, 2019

Codecov Report

Merging #1225 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff             @@
##             master   #1225      +/-   ##
===========================================
- Coverage     89.22%   89.2%   -0.03%     
+ Complexity     1660    1659       -1     
===========================================
  Files           279     279              
  Lines          3992    3992              
  Branches        213     213              
===========================================
- Hits           3562    3561       -1     
  Misses          396     396              
- Partials         34      35       +1
Impacted Files Coverage Δ Complexity Δ
src/main/java/org/cactoos/scalar/Solid.java 90% <0%> (-10%) 3% <0%> (-1%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5e0da30...efc0ee3. Read the comment docs.

@0crat 0crat added the scope label Nov 4, 2019
@0crat
Copy link
Collaborator

0crat commented Nov 4, 2019

Job #1225 is now in scope, role is REV

@0crat
Copy link
Collaborator

0crat commented Nov 4, 2019

This pull request #1225 is assigned to @victornoel/z, here is why; the budget is 15 minutes, see §4; please, read §27 and when you decide to accept the changes, inform @paulodamaso/z (the architect) right in this ticket; if you decide that this PR should not be accepted ever, also inform the architect; this blog post will help you understand what is expected from a code reviewer; there will be no monetary reward for this job

Copy link
Collaborator

@victornoel victornoel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fanifieiev see my comments, I think it would be better to simply write things more procedurally in the tests to be sure you are only testing IteratorOf and not other things.

@@ -60,7 +62,12 @@ public void emptyIteratorThrowsException() {

@Test
public void nonEmptyIteratorDoesNotHaveNext() {
final IteratorOf<Integer> iterator = this.iteratorWithFetchedElements();
final Iterator<Integer> iterator = new Skipped<>(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fanifieiev please do not rely on Skipped here, it's too far away from the tested class to make the test robust

@@ -70,9 +77,15 @@ public void nonEmptyIteratorDoesNotHaveNext() {

@Test
public void nonEmptyIteratorThrowsException() {
final Iterator<Character> iterator = new Skipped<>(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fanifieiev please do not rely on Skipped here, it's too far away from the tested class to make the test robust

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@victornoel Agree, made the fix

@fanifieiev
Copy link
Contributor Author

@0crat status

@0crat
Copy link
Collaborator

0crat commented Nov 6, 2019

@0crat status (here)

@fanifieiev This is what I know about this job in C63314D6Z, as in §32:

@victornoel
Copy link
Collaborator

@paulodamaso it's good to merge

@paulodamaso
Copy link
Contributor

@victornoel Thanks

@paulodamaso
Copy link
Contributor

@rultor merge

@rultor
Copy link
Collaborator

rultor commented Nov 6, 2019

@rultor merge

@paulodamaso OK, I'll try to merge now. You can check the progress of the merge here

@rultor rultor merged commit 4ee17e7 into yegor256:master Nov 6, 2019
@rultor
Copy link
Collaborator

rultor commented Nov 6, 2019

@rultor merge

@paulodamaso Done! FYI, the full log is here (took me 12min)

@0crat 0crat removed the scope label Nov 6, 2019
@0crat
Copy link
Collaborator

0crat commented Nov 6, 2019

The job #1225 is now out of scope

@0crat
Copy link
Collaborator

0crat commented Nov 6, 2019

@sereshqua/z please review this job completed by @victornoel/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

@0crat
Copy link
Collaborator

0crat commented Nov 6, 2019

Payment to ARC for a closed pull request, as in §28: +10 point(s) just awarded to @paulodamaso/z

@fanifieiev fanifieiev deleted the 1222 branch November 6, 2019 21:00
@sereshqua
Copy link

@victornoel please make sure you will try to find at least 3 issues during next CR, thanks

@victornoel
Copy link
Collaborator

@sereshqua yes

@sereshqua
Copy link

@0crat quality acceptable

@0crat
Copy link
Collaborator

0crat commented Nov 7, 2019

Quality review completed: +4 point(s) just awarded to @sereshqua/z

@0crat
Copy link
Collaborator

0crat commented Nov 7, 2019

Order was finished, quality is "acceptable": +15 point(s) just awarded to @victornoel/z

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants