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

TkStart.java:60-61: Add unit tests to test... #954

Closed
karato opened this issue Jan 19, 2016 · 21 comments
Closed

TkStart.java:60-61: Add unit tests to test... #954

karato opened this issue Jan 19, 2016 · 21 comments

Comments

@karato
Copy link
Collaborator

karato commented Jan 19, 2016

Puzzle 750-65232fbb in netbout-web/src/main/java/com/netbout/rest/TkStart.java:60-61 has to be resolved: Add unit tests to test scenarios for requests with/without a token.... The puzzle was created by Prahlad Yeri on 18-Jan-2016.

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.


@karato
Copy link
Collaborator Author

karato commented Jan 19, 2016

@kitsook could you please pick this up? This article explains how we work. Any technical questions you may ask right here; The cost of this task is 30 mins (this is exactly how much will be paid, not less not more), when the task is done

@karato
Copy link
Collaborator Author

karato commented Jan 19, 2016

@dmzaytsev I added milestone 3.1 to this issue, let me know if there has to be something else

@karato karato added this to the 3.1 milestone Jan 19, 2016
@kitsook
Copy link
Contributor

kitsook commented Jan 20, 2016

@karato I am about to start this task and I just took a look at PR #921 . I see that even when token is specified and a cached Inbox is found, the logic still proceed to call inbox.start() to generate bout.

Opening the URL http://localhost:8080/start?post=hello&token=123 multiple times confirmed that new bouts are created.

Is my understand correct that the fix should prevent this?

kitsook added a commit to kitsook/netbout that referenced this issue Jan 20, 2016
@karato
Copy link
Collaborator Author

karato commented Jan 21, 2016

@karato I am about to start this task and I just took a look at PR #921 . I see that even when token is specified and a cached Inbox is found, the logic still proceed to call inbox.start() to generate bout.

Opening the URL http://localhost:8080/start?post=hello&token=123 multiple times confirmed that new bouts are created.

Is my understand correct that the fix should prevent this?

@kitsook you should address your technical comments to the project architect (@dmzaytsev)

@dmzaytsev
Copy link
Contributor

@kitsook take a look #750

  • if you open url http://localhost:8080/start?post=hello&token=123 two times or more
    only one bout should be created
  • if you open url http://localhost:8080/start?post=hello two times or more
    one bout should be created on each call

you have to create unit tests to check these two cases

@kitsook
Copy link
Contributor

kitsook commented Jan 21, 2016

@dmzaytsev so my understanding was correct.

as said, PR #921 did not implement correctly. TKStart.java calls inbox.start() even when a cached bot was found. This effectively creates a new bout no matter a matching token is found or not.

just tested the latest master branch, opening http://localhost:8080/start?post=hello&token=123 multiple times will create multiple bouts.

@karato i have done the test cases since my previous post. but i won't create PR as it will break the build

kitsook added a commit to kitsook/netbout that referenced this issue Jan 21, 2016
kitsook added a commit to kitsook/netbout that referenced this issue Jan 22, 2016
kitsook added a commit to kitsook/netbout that referenced this issue Jan 22, 2016
@dmzaytsev
Copy link
Contributor

@kitsook you can create PR for sure
just put @Ignore on broken tests
and create a puzzle to fix the tests for another developer

kitsook added a commit to kitsook/netbout that referenced this issue Jan 22, 2016
kitsook added a commit to kitsook/netbout that referenced this issue Jan 22, 2016
kitsook added a commit to kitsook/netbout that referenced this issue Jan 22, 2016
@kitsook
Copy link
Contributor

kitsook commented Jan 22, 2016

@karato please see PR #960

@karato
Copy link
Collaborator Author

karato commented Jan 22, 2016

@karato please see PR #960

@kitsook I will take a look, thanks

kitsook added a commit to kitsook/netbout that referenced this issue Jan 22, 2016
kitsook added a commit to kitsook/netbout that referenced this issue Jan 22, 2016
kitsook added a commit to kitsook/netbout that referenced this issue Jan 22, 2016
kitsook added a commit to kitsook/netbout that referenced this issue Jan 22, 2016
kitsook added a commit to kitsook/netbout that referenced this issue Jan 22, 2016
kitsook added a commit to kitsook/netbout that referenced this issue Jan 22, 2016
kitsook added a commit to kitsook/netbout that referenced this issue Jan 23, 2016
@karato
Copy link
Collaborator Author

karato commented Jan 24, 2016

@dmzaytsev the code made here contains a puzzle 954-b453159b/#973, which will be resolved soon

@kitsook
Copy link
Contributor

kitsook commented Jan 24, 2016

@karato PR #960 merged. please close this issue if it is considered to be resolved

@karato karato closed this as completed Jan 25, 2016
@karato
Copy link
Collaborator Author

karato commented Jan 25, 2016

@dmzaytsev We are done here, thanks all

@karato
Copy link
Collaborator Author

karato commented Jan 25, 2016

@elenavolokhova please, review this ticket for compliance with our QA rules

@karato
Copy link
Collaborator Author

karato commented Jan 25, 2016

@karato PR #960 merged. please close this issue if it is considered to be resolved

@kitsook OK

@kitsook
Copy link
Contributor

kitsook commented Jan 26, 2016

@karato may i know when will my payment and rating be updated?

@dmzaytsev
Copy link
Contributor

@kitsook after QA review

karato commented 14 hours ago
@elenavolokhova please, review this ticket for compliance with our QA rules

@elenavolokhova
Copy link

@karato Looks good!

@karato
Copy link
Collaborator Author

karato commented Jan 26, 2016

@karato Looks good!

@elenavolokhova many thanks

@karato
Copy link
Collaborator Author

karato commented Jan 26, 2016

@kitsook just added 10 mins to @elenavolokhova (for QA), payment ID is 75680321; thank you, added 30 mins to your acc, payment num is AP-4TV167733Y4303337, 116 hours and 42 mins spent in total to complete; added +30 to your rating, now it is equal to +30

@karato
Copy link
Collaborator Author

karato commented Jan 30, 2017

@dmzaytsev the last puzzle 954-b453159b/#973 solved

0pdd referenced this issue Dec 19, 2023
Bumps [com.h2database:h2](https://github.com/h2database/h2database) from 1.4.190 to 2.2.220.
- [Release notes](https://github.com/h2database/h2database/releases)
- [Commits](h2database/h2database@version-1.4.190...version-2.2.220)

---
updated-dependencies:
- dependency-name: com.h2database:h2
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@0pdd
Copy link
Collaborator

0pdd commented Jan 4, 2024

@karato the only puzzle #unknown is solved here.

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

No branches or pull requests

5 participants