Developer sees unit test coverage for Littlepay V3 syncing

[ohrite]

As a developer making changes to the Littlepay v3 sync logic,
When I make a breaking behavior change,
I can run pytest and see a corresponding failure message

---

Notes:

• Follow the example of other Operator tests in the airflow/tests/operators/ path
• Do not test the inside of the space capsule https://speakerdeck.com/skmetz/magic-tricks-of-testing-railsconf
• The result artifact should be in a predictable location, and containing the same information, given the inputs
• If your test depends on fixture data, such as a file at a specific location, make sure it’s there in setup
• More integration is better than less integration