Dependent breaking pytest's

Command Palette

Search for a command to run...

Dependent breaking pytest's

PublishedJanuary 21, 2025

•1 min read•View as Markdown

Danny Crasto

I am developer/code-reviewer/debugger/bug-fixer/architect/teacher/builder from dubai, uae

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

Get harsh feedback

with T.A.C.T

Aug 9, 2026·1 min read

Database Isolation levels

Isolation is part of a database's ACID guarantees. It ensures that concurrent transactions don't affect each other. The goal is to maintain the state of the data as if transactions are run serially. H

Aug 6, 2026·2 min read·21

8 Simple reminders

You Should Tell Yourself

Jul 22, 2026·1 min read·14

Design a url shortner

A URL shortener is a proxy service that provides a mapping between the short and full representation of a URL. The short URL has the advantage of being small. The service can also provide useful analy

Jul 19, 2026·2 min read·219

No regrets

Listening to the Mel Robbins's podcast on regrets was a 'ear'-opener. One can have reqrets of action or inaction. 4 types of reqrets foundation - should've done the work boldness - should've taken t

Jul 15, 2026·1 min read·23

Danny's blog

77 posts

I like computers

New unit-tests were added that were passing when run in isolation. They were breaking when run all together by the CI/CD pipeline. Previous tests were affecting ours. The question was which ones? We thought it could be a data issue with persistent data affecting tests. However we use @pytest.mark.django_db which

will set up the Django databases the first time a test needs them. Once setup, the database is cached to be used for all subsequent tests and rolls back transactions, to isolate tests from each other.

We could replicate the failure locally. Finding the breaking test case by the process of elimination, we ran test cases directories in order. Removing a directory each time while the error persisted.

The breaking test case didn't reconnect a post_save signal’s receiver. Our tests relied on receivers. Reverting this line, and muting the firing of the signal for other failing tests we got it to work.

Moral: leave things better than you found it or at the very least, the same.

References

Pytest’s database access
Django’s post_save signals

#pytest #unit-testing #python

14 views

Archive
Recommendations
Privacy
Terms

Sitemap RSS