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

Assertion.java:74-77: Assertion relies on the operation... #53

Closed
0pdd opened this issue Dec 8, 2018 · 15 comments
Closed

Assertion.java:74-77: Assertion relies on the operation... #53

0pdd opened this issue Dec 8, 2018 · 15 comments
Labels
bug Something isn't working pdd scope
Milestone

Comments

@0pdd
Copy link
Collaborator

0pdd commented Dec 8, 2018

The puzzle 18-a9679abd from #18 has to be resolved:

* @todo #18:30min Assertion relies on the operation under test to be idempotent
* in order to match "error matchers" such as `Throws` as expected. This may
* not be the case for all operations and could be a problem. Investigate if
* there's a way around/through this.

The puzzle was created by George Aristy on 08-Dec-18.

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.

@0crat
Copy link
Collaborator

0crat commented Dec 8, 2018

@llorllale/z please, pay attention to this issue

@0crat
Copy link
Collaborator

0crat commented Dec 8, 2018

Job #53 is now in scope, role is DEV

@dgroup
Copy link
Contributor

dgroup commented Dec 20, 2018

@llorllale, the description of this task isn't clear.

This may not be the case for all operations and could be a problem.

Could you please give an example?

@llorllale
Copy link
Owner

@dgroup it refers to operations that may not throw the same exception on the second call.

Assertion currently executes the operation under test twice in order to test the error. What this puzzle is saying is that the operation under test may not throw the same error on the second call, thereby potentially failing the match inside the catch clause.

@llorllale llorllale added this to the 1.0.0 milestone Dec 20, 2018
@0crat
Copy link
Collaborator

0crat commented Jan 3, 2019

The job #53 assigned to @dgroup/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

@dgroup
Copy link
Contributor

dgroup commented Jan 3, 2019

@0crat wait as #71 was raised.

@0crat
Copy link
Collaborator

0crat commented Jan 3, 2019

@0crat wait as #71 was raised. (here)

@dgroup The impediment for #53 was registered successfully by @dgroup/z

dgroup added a commit to dgroup/cactoos-matchers that referenced this issue Jan 5, 2019
dgroup added a commit to dgroup/cactoos-matchers that referenced this issue Jan 15, 2019
dgroup added a commit to dgroup/cactoos-matchers that referenced this issue Jan 21, 2019
@0pdd
Copy link
Collaborator Author

0pdd commented Jan 22, 2019

The puzzle 18-a9679abd has disappeared from the source code, that's why I closed this issue.

@0pdd
Copy link
Collaborator Author

0pdd commented Jan 22, 2019

@0pdd the puzzle #88 is still not solved.

@0crat
Copy link
Collaborator

0crat commented Jan 22, 2019

The job #53 is now out of scope

@0crat
Copy link
Collaborator

0crat commented Jan 22, 2019

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

@0pdd
Copy link
Collaborator Author

0pdd commented Apr 21, 2019

@0pdd the puzzle #110 is still not solved; solved: #88.

@0pdd
Copy link
Collaborator Author

0pdd commented Apr 24, 2019

@0pdd the puzzle #113 is still not solved; solved: #110, #88.

@0pdd
Copy link
Collaborator Author

0pdd commented Apr 26, 2019

@0pdd the puzzle #116 is still not solved; solved: #110, #113, #88.

@0pdd
Copy link
Collaborator Author

0pdd commented Apr 26, 2019

@0pdd all 4 puzzles are solved here: #110, #113, #116, #88.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working pdd scope
Projects
None yet
Development

No branches or pull requests

4 participants