pytest-gitconfig 0.9.0

Provide a Git config sandbox for testing

pytest-gitconfig

Provide a Git config sandbox for testing

Getting started

Install pytest-gitconfig:

# pip
pip install pytest-gitconfig
# pipenv
pipenv install pytest-gitconfig
# PDM
pdm add pytest-gitconfig

Then, the session-scoped default_gitconfig fixture will be automatically loaded for the session providing isolation from global user-defined values.

If you want to customize or depend on it:

from __future__ import annotations

from typing import TYPE_CHECKING

import pytest

if TYPE_CHECKING:
    from pytest_gitconfig import GitConfig


@pytest.fixture(scope="session")
def default_git_user_name() -> str:
  return "John Doe"


@pytest.fixture(scope="session", autouse=True)
def fixture_depending_on_default_gitconfig(default_gitconfig: GitConfig) -> Whatever:
    # You can set values, the following statements are equivalents
    default_gitconfig.set({"some": {"key": value}}) # nested dicts form
    default_gitconfig.set({"some.key": value})      # dict with dotted keys form
    # Or read them
    data = default_gitconfig.get("some.key")
    data = default_gitconfig.get("some.key", "fallback")
    # If you need the path to the Git config file
    assert str(default_gitconfig) == str(default_gitconfig.path)
    return whatever

Note that the default_gitconfig fixture is Session-scoped (avoiding the performance hit of creating a Git config file for each test), so set values are persistent for the whole session and should be defined once, preferably in your conftest.py. But if you need to temporarily override some value, you can use the override() context manager which accepts the same parameters as set().

This allows to override it directly during a test:

from __future__ import annotations

from typing import TYPE_CHECKING, Iterator

if TYPE_CHECKING:
    from pytest_gitconfig import GitConfig


def test_something(default_gitconfig: GitConfig):
    with gitconfig.override({"other.key": value}):
        # Do something depending on those overridden values

But to test some value in some specific tests, it's best to rely on the function-scoped gitconfig fixture providing the Git config:

from __future__ import annotations

from typing import TYPE_CHECKING

if TYPE_CHECKING:
    from pytest_gitconfig import GitConfig


def test_something(gitconfig: GitConfig):
    gitconfig.set({"other.key": value})  # Only valid for this test
    # Do something depending on those overridden values

A classical setup is:

• Default to using the session-scoped default_gitconfig to ensure isolation.
• Some specific test cases relying on some specific settings set on the function-scoped gitconfig fixture.

This has the following benefits:

• Session isolation is done only once.
• Tests having specific settings do not impact other tests.
• Tests having specific settings can be run in parallel.

Provided fixtures

Function-scoped

gitconfig -> pytest_gitconfig.GitConfig

This is the main fixture which creates a new and clean Git config file for the tested function.

It inherits from default_gitconfig (meaning that all values set on default_gitconfig will be set on gitconfig).

It works by monkeypatching the GIT_CONFIG_GLOBAL environment variable. So, if you rely on this in a context where os.environ is ignored, you should patch it yourself using this fixture.

git_user_name -> str | None

Provide the initial user.name setting for gitconfig. If None, user.name will inherit its value from default_config, so most probably from default_git_user_name if not overridden.

git_user_email -> str | None

Provide the initial user.email setting for gitconfig. If None, user.email will inherit its value from default_config, so most probably from default_git_user_email if not overridden.

git_init_default_branch -> str | None

Provide the initial init.defaultBranch setting for gitconfig. If None, init.defaultBranch will inherit its value from default_config, so most probably default_git_init_default_branch if not overridden.

set_gitconfig -> Mapping[str, str | UnsetType]

Set some git config settings for gitconfig.

Session-scoped

default_gitconfig -> pytest_gitconfig.GitConfig

This is the main fixture which creates a new and clean Git config file for the test session. It is loaded automatically if you have pytest-gitconfig installed.

By default, it will set 3 settings:

• user.name
• user.email
• init.defaultBranch

It works by monkeypatching the GIT_CONFIG_GLOBAL environment variable. So, if you rely on this in a context where os.environ is ignored, you should patch it yourself using this fixture.

default_git_user_name -> str | UnsetType

Provide the initial user.name setting. By default pytest_gitconfig.DEFAULT_GIT_USER_NAME (Pytest). Override to provide a different initial value.

default_git_user_email -> str | UnsetType

Provide the initial user.email setting. By default pytest_gitconfig.DEFAULT_GIT_USER_EMAIL ([e-mail]). Override to provide a different initial value.

default_git_init_default_branch -> str | UnsetType

Provide the initial init.defaultBranch setting. By default pytest_gitconfig.DEFAULT_GIT_BRANCH (main). Override to provide a different initial value.

set_default_gitconfig -> Mapping[str, str | UnsetType]

Set some git config settings for default_gitconfig.

sessionpatch -> pytest.MonkeyPatch

A pytest.MonkeyPatch session instance.

API

pytest_gitconfig.GitConfig

An object materializing a given Git config file.

set(self, data: Mapping[str, Any])

Write some Git config settings. It accepts a dict of parsed data sections as (nested) dicts or dotted-key-values.

get(self, key: str, default: Any = UNSET) -> str

Get a setting given its dotted key. Get a user-provided default value if the setting does not exist. Raise KeyError if setting does not exists and default is not provided.

override(self, data: Mapping[str, Any]) -> Iterator[pytest_gitconfig.GitConfig]

A context manager that overrides Git config settings and restores them on exit. Accepts the same format as the set() method.