Closed a3626a closed 1 year ago
Thanks for submitting your first pull request! You are awesome! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please make sure you followed the pull request template, as this will help us review your contribution more quickly.
You can meet the other Jovyans by joining our Discourse forum. There is also a intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
Ah, thanks for looking into this!
Can you rework this to use https://docs.pytest.org/en/7.1.x/how-to/assert.html#assertions-about-expected-exceptions instead? That's the expected way to test for expected exceptions in pytest I think.
Ah, thanks for looking into this!
Can you rework this to use https://docs.pytest.org/en/7.1.x/how-to/assert.html#assertions-about-expected-exceptions instead? That's the expected way to test for expected exceptions in pytest I think.
Of course, that is great. It is done.
Thanks @a3626a. Looks like the test failures may be related?
@yuvipanda
Thanks @a3626a. Looks like the test failures may be related?
It is really done!
Congrats on your first merged pull request in this project! :tada: Thank you for contributing, we are very proud of you! :heart:
Recently, I have ported a portion of nbgitpuller into Ruby On Rails compatible ruby version. Meanwhile, I have found that 'test_exception_branch_exists' doesn't test anything. Actually
puller.gp.branch_exists("wrong")
was not throwing any errors, andassert type(e) == ValueError
was not called at all.I refered
test_exception_resolve_default_branch
andtest_git_lock
, and introducedexception_raised
variable andpuller.gp.git_url = ""
assignment.