Testing: runner.invoke reuses 'app' object, causing cached properties to exist when they're not supposed to

[Dymstro]

First Check

• I added a very descriptive title to this issue.
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the Typer documentation, with the integrated search.
• I already searched in Google "How to X in Typer" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answer.
• I already checked if it is not related to Typer but to Click.

Commit to Help

• I commit to help with one of those options 👆

Example Code

from typer.testing import CliRunner from .main import app runner = CliRunner() def test_list_databases() -> None: # This command causes an internal 'databases' object to be cached. result = runner.invoke(app, ["databases", "list"] assert result.exit_code == 0 def test_create_database() -> None: # This command accesses some cached properties (using cached-property package). # Those objects aren't supposed to exist yet, but they were already created in previous tests. # This causes the command to use old data and crash. result = runner.invoke(app, ["databases", "create", "tests-db", "MariaDB"]) assert result.exit_code == 0

Description

CliRunner.invoke reuses 'app' causing different behavior than just running them outside tests.

My code uses some cached properties that get cached in earlier tests.
This causes some commands to use old data, which causes it to crash.
Normally this would never happen as the program exits after a single command.

Operating System

Linux

Operating System Details

No response

Typer Version

0.4.0

Python Version

3.7

Additional Context

No response

[DvdNss]

happening for me as well, some options get cached and re-used in the following tests, making the tests fail

[YuriiMotov]

This is not a Typer's issue..

You can solve this by re-importing the app on every test:

import helloworld.main ... def test_list_databases(): importlib.reload(helloworld.main) result = runner.invoke(helloworld.main.app, ...) ...

Working code example

helloworld/main.py

from functools import cached_property import typer class DatabaseManager: @cached_property def databases(self) -> list[str]: print(">> Creating databases list") return ["default-db"] def create(self, name: str) -> None: print(f">> Creating database {name}") self.databases.append(name) manager = DatabaseManager() app = typer.Typer() @app.command() def list_databases(): for db in manager.databases: typer.echo(db) @app.command() def create_database(name: str): manager.create(name) typer.echo(f"Database {name} created")

helloworld/test.py

import importlib from typer.testing import CliRunner import helloworld.main runner = CliRunner() def test_list_databases(): importlib.reload(helloworld.main) result = runner.invoke(helloworld.main.app, ["list-databases"]) assert result.exit_code == 0 assert ">> Creating databases list" in result.stdout def test_create_database(): importlib.reload(helloworld.main) result = runner.invoke(helloworld.main.app, ["create-database", "test-db"]) assert result.exit_code == 0 assert ">> Creating databases list" in result.stdout

[WilliamDEdwards]

This is not a Typer's issue..

I agree that with the current implementation, i.e. app being a singleton, this is expected behaviour.

However, seeing as how the lifecycle of a CLI app is usually short, and tests should be isolated from each other, I would argue this is more of an architectural gray area.