this post was submitted on 31 Dec 2024
15 points (100.0% liked)

Python

6496 readers
1 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

πŸ“… Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

🐍 Python project:
πŸ’“ Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 2 years ago
MODERATORS
jnovinger
erlingur
norambna
15
unittest recipes for temporary files and directories (adamj.eu)
submitted 6 days ago by norambna to c/python
5 comments fedilink hide all child comments
 

via https://fosstodon.org/@adamchainz/113741633201993444

top 5 comments
sorted by: hot top controversial new old
[–] logging_strict 1 points 4 days ago

why use unittest?

Besides showing off what a degenerate can accomplish.

I can run groupings or part of a grouping of unittest testcases in parallel. From a GUI. By typing ~6-10 keystrokes.

Just never got around to implementing this using pytest. And cuz of that, never published the GUI package.

Search algorithms matter

When humans read ^^ nothing registers in the brain. Could write it 1000x and would always fall on closed brains.

People would still go back to recommending their favorite File Managers (has no search algo) or managing their contacts within each social media platform. And infinite scroll new feeds.

Without thinking twice about it.

[–] logging_strict 1 points 4 days ago

Use both unittest and pytest. To get proficient in both.

Was initially thinking this article is going to turn out to be useless. Then it taught a useful trick that wasn't aware of.

Learning something new with unittest is unusual.

[–] [email protected] 3 points 6 days ago (1 children)

People still use unitest instead of pytest fixtures? https://docs.pytest.org/en/6.2.x/tmpdir.html

[–] monomon 1 points 6 days ago* (last edited 6 days ago) (1 children)

This. We kinda stumbled on this pattern, and use it to great effect. Simplified code:

@pytest.fixture
def tmpfiles():
    with NamedTemporaryFile(suffix=".html") as f:
        yield f

# or for paths, which are more suitable for certain tests
# touch them so they exist
@pytest.fixture
def othertmppaths() -> list[Path]:
    f1 = Path("...")
    f1.touch()
    f2 = Path("...")
    f2.touch()

    yield [f1, f2]
    # you could delete them here if needed
    f1.unlink()

def test_foo(othertmppaths list[Path]):
    result = upload_resource(othertmppaths[0]) 
    assert result.status == 200

The context manager one will properly clean up all files.

E: Pretty website btw

[–] logging_strict 1 points 4 days ago

Often using pytest to debug code. When using a tmp_path, would prefer not to delete the file tree in the end.

When the test fails, can run the code against the folder tree

  • cd into the tmp folder
  • activate the venv
  • run the code