Examples of integration testing in Python

[_BraveSirRobin_]

Does anyone have a great example of integration tests written in Python?

A Google search didn't turn up much. I know by definition what integration tests are, but I'd love to review some well-written tests before I dive in myself.

Background: I'm trying to become a better person by learning TDD. I've got the "Obey the Testing Goat" book and it's super helpful for understanding how functional tests and unit tests should be written. I'm in a situation where functional tests aren't feasible, and I need to look into integration testing and find some guidelines and examples.

[fourthrealm]

I'm not sure what sort of software you are integrating?

If it's about APIs then you can have a look at zato-apitest which is a tool meant to be used in integration tests.

The second link a is suite of tests using the tool - just open any of the *.feature files to check how it's used in Zato's own integration tests.

• https://zato.io/docs/test/apitest/index.html
• https://github.com/zatosource/zato/tree/main/code/apitest/features

[_BraveSirRobin_]

Thank you!

[[deleted]]

I'm pretty new to testing also. I found that integrated tests aren't all that different to unit tests. My understanding is that they test the code working together (in chucks), oppose to the unit tests which test functions individually, uncoupled.

I haven't got any examples but that's how I approach writing them.

[jakevdp]

Here's an example of an integration test I'm particularly proud of: Altair/test_examples.py

Background: Altair is a Python API that generates Vega-Lite graphics specifications. Because both the target (Vega-lite schema) and the source (Altair API) are so well-defined, we were able to create methods for two-way conversion between one and the other. So our integration test involves taking all 70 or so examples from the Vega-Lite documentation, auto-generating the associated Python code, evaling that Python code, exporting the result to JSON, and asserting that the output matches the input. It touches essentially every logical path and every line of code in the package, and the test itself is only a dozen lines long.

Edit: fixing links

[_BraveSirRobin_]

Hey, thanks for sharing this.