Ancestors

Toot

Written by daftwullie on 2024-08-15 at 12:28

A question to the #python people: Is there a good way to approach automated downstream testing of your code?

Let's say you are the maintainer of library "Lib_A" and you know, that "Important_Project_B" and "Important_Project_C" user your library a a dependency. How do you approach automated testing of "Important_Project_B" and "Important_Project_C" when changing your "Lib_A"?

Maybe @brianokken has an idea 😅

=> More informations about this toot | More toots from daftwullie@chaos.social

Descendants

Written by L3viathan on 2024-08-15 at 12:30

@daftwullie Seems ultimately futile, "just" have a clearly defined public interface and increment version numbers appropriately..

=> More informations about this toot | More toots from l3viathan@mastodon.social

Written by daftwullie on 2024-08-15 at 12:33

@l3viathan I completly understand you point. And my lib has this (as far as I am concerned). But I'd like to refactor some internals and want to make sure not to break anything downstream. Sometimes my own tests don't catch everything ;)

=> More informations about this toot | More toots from daftwullie@chaos.social

Written by gram on 2024-08-15 at 12:46

@daftwullie

I know mypy does exactly that, at large scale, for every PR:

https://github.com/hauntsaninja/mypy_primer

=> More informations about this toot | More toots from orsinium@fosstodon.org

Written by daftwullie on 2024-08-15 at 13:01

@orsinium Thanks a lot for this tip. I'll try to find out how they are doing it :)

=> More informations about this toot | More toots from daftwullie@chaos.social

Written by Brian Okken :python: on 2024-08-15 at 16:26

@daftwullie pytest itself has selected some plugins to try to avoid breaking and incorporating those into the test suite. See https://github.com/pytest-dev/pytest/tree/main/testing/plugins_integration

I think this is a cool idea.

=> More informations about this toot | More toots from brianokken@fosstodon.org

Written by daftwullie on 2024-08-15 at 16:28

@brianokken thanks for the tip. I‘ll take a deeper look and hopefully get some ideas how to proceed.

=> More informations about this toot | More toots from daftwullie@chaos.social