Conversation
|
@camilamaia your pull request is missing a changelog! |
|
@barbosa this is super weird, on my machine there tests that fail 🤷♀️ Do you have any idea? I tried to debug and when I leave this part of the code, it works: class TestConsoleReport:
def test_should_print(self, mocker, mocked_print):
console_reporter = Reporter(None, "console")
console_reporter.write(fake_responses) |
80becc6 to
07578ec
Compare
Codecov Report
@@ Coverage Diff @@
## master #175 +/- ##
==========================================
- Coverage 93.21% 92.02% -1.20%
==========================================
Files 14 14
Lines 516 514 -2
==========================================
- Hits 481 473 -8
- Misses 35 41 +6
Continue to review full report at Codecov.
|
226b91b to
f7878a3
Compare
07578ec to
1e7a39f
Compare
| ```bash | ||
| $ scanapi --help | ||
| Usage: scanapi [OPTIONS] | ||
| Usage: scanapi [OPTIONS] [SPEC_PATH] |
There was a problem hiding this comment.
Having SPEC_PATH before OPTIONS reinforces the idea that the former is required and the latter is optional, I think.
There was a problem hiding this comment.
Good idea. However, I looked for some documentation for this pattern and I didn't find it. Besides, I checked two terminal commands and the usage are in the same format we currently have:
gcc [OPTIONS] COMMANDdocker [OPTIONS] COMMAND
So IMHO there's no problem here to keep using this format :)
There was a problem hiding this comment.
Good examples. Although the idea of COMMAND (which is usually an imperative verb like: run, build, open, etc) is a bit different from SPEC_PATH (which sounds more like just another argument), I’m OK with both options.
There was a problem hiding this comment.
Good catch. I can see more clearly now. Thanks!
There was a problem hiding this comment.
Great discussion, I did not think about these points, thank you both! I agree that would be clearer to have [SPEC_PATH] before [OPTIONS], but I don't know how to do it actually 😂 This order ir generated by Click. I would need more investigation to figure out how to change it.
☝️ In special for this PR, that we have a breaking change (from option to argument). |
|
Weird that the tests are breaking in your machine. Have you tried removing all |
Indeed! Done ✅ |
@barbosa Yes, I did it and it keeps breaking 😞 |
|
@barbosa I deleted the repo, recloned it and the error is still happening 😢 |
cf12172 to
d3001d9
Compare
d3001d9 to
7674c82
Compare
|
@loop0 figure out the problem with the failing tests! The problem was with the We were mocking the builtin method When we were running the console test before, it was not mocking the open method, so this info was already available in memory. When we removed it, it crashed. |
Closes #174
Closes #171