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
feat(scan): implement scan functionality #43
Conversation
Code Climate has analyzed commit 0305650 and detected 3 issues on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 99.3% (50% is the threshold). This pull request will bring the total coverage in the repository to 97.9% (1.0% change). View more on Code Climate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are multiple bugs, please address them first, then I will proceed with the review.
In addition, pay attention to these comments as well:
- rename the
requests
folder tocommands
(we don't have such an entity) - remove the useless
enums
folder (the folder structure should reflect the domain) - for each bug that I mention you should write a dedicated test case
ed0a5e6
to
93b3a9c
Compare
@RomanReznichenko please resolve codeclimate issues first |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are still multiple issues and bugs:
- The file is not satisfied HAR spec 1.2, e.g.
postData
is expected to be an object, cookies are empty, etc - Wrong query params serialization
- Wrong default body serialization in the
HarEntryBuilder
- No error handling in the
Scans
- Scan stops even while getting 502 error
- etc
@RomanReznichenko leave everything as is, I will fix them soon
6d14f6d
to
b13452f
Compare
c36ac30
to
5eedcdc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please check expectation
/expectations
wording in package description
closes #42