IMO this is a good example of a faulty design: using make recipes in the unit testing code. makefile are close to the user and used as a tool that collect CLI options for the upper-most level user. I would argue, base on POLA , that makefile can call pytest but not the other way around
well I would argue that it depends what you are testing. if testing the Makefile targets then it can be a good idea. but that is already an integration test.
What do these changes do?
IMO this is a good example of a faulty design: using
make
recipes in the unit testing code.makefile
are close to the user and used as a tool that collect CLI options for the upper-most level user. I would argue, base on POLA , thatmakefile
can callpytest
but not the other way aroundRelated issue/s
How to test
For internal developers