FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Tests need to be implemented for tests/unit/test_projects.py · Issue #1708 · python-gitlab/python-gitlab · GitHub

Repository navigation

Tests need to be implemented for tests/unit/test_projects.py #1708

Description

Currently we have a lot of unimplemented tests in tests/unit/test_projects.py.

Adding these tests would be a good first issue for someone to work on.

Comment below if you would like to work on this issue.

Activity

  1. vishalpandeynits commented on Nov 30, 2021

    I would like to work on this @JohnVillalovos .

  2. nejch commented on Nov 30, 2021

    Member

    That's amazing @vishalpandeyvip. I've assigned this to you for now, feel free to reach out if you have any issues/questions.

    As we add new resources, we sometimes split modules to keep them a sane size, so it's possible some of those tests will eventually belong in a separate module, but up to you.

  3. vishalpandeynits commented on Nov 30, 2021

    Thanks for assigning this to me @nejch . I am new to the project so once going through documentation and codebase. I will try to create a PR very soon.

  4. rnoberger commented on May 7, 2022

    Contributor

    Hello, I tried to implement some tests for the easy list functions in projects. Can you take a quick look into and give me some feedback? I pushed it to a forked Repository: rnoberger/python-gitlab

    The fixtures are getting quickly big. Do you prefere to use the assert_all_requests_are_fired=False flag?

  5. nejch commented on May 7, 2022

    Member

    That looks good @rnoberger, thanks for taking a look at this! It's best to open a draft pull request so we can discuss it there :)

    It looks mature enough for a PR already IMO. I think we can reduce the size of fixtures by using lazy=True in the initial project get() call (or even using a project fixture, I'll give you a suggestion), so we only need to mock the final request.

    @vishalpandeyvip are you still interested in covering some of the other missing tests or should I unassign you from here?

  6. rnoberger commented on May 8, 2022

    Contributor

    I opened a PR. Would be nice if you @nejch could make the suggestion how to stomp the fixtures.

  7. nejch commented on May 31, 2022

    Member

    Unassigning this as we had some initial contributions already but this issue still could use quite a bit of help for any readers here :)

    If you're new and reading this, feel free to get in touch or open a PR, you can take a look at #2012 for an example.

  8. antoineauger commented on Jun 14, 2022

    Contributor

    @nejch I would like to help here, I'll have a look to #2012 😉

  9. nejch commented on Jun 14, 2022

    Member

    That's awesome @antoineauger, thanks! Maybe one day we get to that magical 100% then 😁

  10. locked as resolved and limited conversation to collaborators on Jul 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL